-
Notifications
You must be signed in to change notification settings - Fork 242
Performance testing/investigation #6140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Dependency Review✅ No vulnerabilities or OpenSSF Scorecard issues found.Scanned FilesNone |
/try |
Okay, starting a try! I'll update this comment once it's running...\n |
/try |
Okay, starting a try! I'll update this comment once it's running...\n |
/try |
Okay, starting a try! I'll update this comment once it's running...\n |
6ada745
to
fdb7911
Compare
/try |
Okay, starting a try! I'll update this comment once it's running...\n |
fdb7911
to
ada1005
Compare
/try |
Okay, starting a try! I'll update this comment once it's running...\n |
/try |
Okay, starting a try! I'll update this comment once it's running...\n |
3e93312
to
50087af
Compare
/try |
Okay, starting a try! I'll update this comment once it's running...\n |
… the UI `AttributeValue::update`, and `FuncRunner::run_attribute_value` appear to take substantial amounts of time. This adds additional instrumentation to try to help narrow down exactly where & why.
…value.prepare slowness
…nctions The intrinsic functions are never dispatched to Veritech to run, and the point of a "before function" is to set up the environment that Veritech/Cyclone will use to run the function so that it has access to whatever secrets/config it needs, which means that a before function will never be able to affect how an intrinsic is run.
There is several seconds of unaccounted for time in update_property_editor_value, so this is attempting to help narrow down where that time is being spent.
50087af
to
66f7fc4
Compare
No description provided.