-
Notifications
You must be signed in to change notification settings - Fork 318
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
Minimum viable example - benchmark issues #3146
Conversation
Overall package sizeSelf size: 4.12 MB Dependency sizes
🤖 This report was automatically generated by heaviest-objects-in-the-universe |
Codecov Report
@@ Coverage Diff @@
## master #3146 +/- ##
==========================================
- Coverage 86.98% 86.97% -0.02%
==========================================
Files 322 327 +5
Lines 11763 11782 +19
Branches 33 33
==========================================
+ Hits 10232 10247 +15
- Misses 1531 1535 +4
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
994d094
to
16a1b6b
Compare
BenchmarksComparing candidate commit 8990942 in PR branch Found 0 performance improvements and 10 performance regressions! Performance is the same for 436 metrics, 26 unstable metrics. scenario:log-without-log-16
scenario:log-with-debug-16
scenario:log-skip-log-16
scenario:startup-with-tracer-16
scenario:log-without-log-18
scenario:log-with-error-18
scenario:log-with-debug-18
scenario:log-skip-log-18
scenario:startup-with-tracer-18
|
All we should need is for `dummy-module` to be loaded
68bb099
to
8990942
Compare
We're reasonably certain the benchmarks aren't representative. This is no longer needed. |
What does this PR do?
This reproduces the benchmark issues seen in #2941
This example does 2 things:
plugin_manager
'sconfigure
to perform a tiny operation at startup time.What's going on?
Looking at the benchmarks that are having trouble, we have 2 categories:
The startup issue is interesting, because we have 4 startup scenarios here, but only 1 fails.
Looking at the code (
benchmarks/sirun/startup/startup-test.js
):My theory: we have issues in this benchmark, and not in the one where we load the tracer and everything because:
EVERYTHING
, becauseEVERYTHING
goes over the threshold we're observing anyway