-
Notifications
You must be signed in to change notification settings - Fork 287
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
Trial combination of bouwe array-equal-fix and non-lazy-benchmarks #6349
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6349 +/- ##
=======================================
Coverage 89.79% 89.80%
=======================================
Files 90 90
Lines 23554 23576 +22
Branches 4391 4399 +8
=======================================
+ Hits 21150 21172 +22
Misses 1662 1662
Partials 742 742 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
⏱️ Performance Benchmark Report: 0327e4ePerformance shifts
Full benchmark results
Generated by GHA run |
Update after re-benchmark runthe #6337 speedups were about -20%..-30%, so roughly cancel out the slowdowns. All of this is pretty much just the same as what we saw before. |
Rebased from updated #6325 with added commit "@bouweandela And re-started benchmarks ... |
⏱️ Performance Benchmark Report: 84c20d0Performance shifts
Full benchmark results
Generated by GHA run |
⏱️ Performance Benchmark Report: 0d3239bPerformance shifts
Full benchmark results
Generated by GHA run |
⏱️ Performance Benchmark Report: 842be13Performance shifts
Full benchmark results
Generated by GHA run |
My manual merge of #6325 and #6339 just to see how performance is affected.
NB since I already merged #6337 the benefit from that has already been had.
So, if this benchmarks slower in the expected cases, we should reference to those improvements too, since they were intended to mitigate possible costs of #6325