-
Notifications
You must be signed in to change notification settings - Fork 20
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
Chore Update Benchmark Standard #1843
Conversation
697d951
to
92f1432
Compare
⏳ Running benchmarks and calculating weights. DO NOT MERGE! A new commit will be added upon completion... |
✅ Finished running benchmarks. Updated weights have been committed to this PR branch in commit 2aba9c3. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1843 +/- ##
=======================================
Coverage 83.11% 83.11%
=======================================
Files 56 56
Lines 4525 4525
=======================================
Hits 3761 3761
Misses 764 764 ☔ View full report in Codecov by Sentry. |
2aba9c3
to
a134ad4
Compare
a134ad4
to
dc83205
Compare
⏳ Running benchmarks and calculating weights. DO NOT MERGE! A new commit will be added upon completion... |
✅ Finished running benchmarks. Updated weights have been committed to this PR branch in commit e697ce6. |
e697ce6
to
b392187
Compare
⏳ Running benchmarks and calculating weights. DO NOT MERGE! A new commit will be added upon completion... |
✅ Finished running benchmarks. Updated weights have been committed to this PR branch in commit 480c4e0. |
480c4e0
to
b392187
Compare
⏳ Running benchmarks and calculating weights. DO NOT MERGE! A new commit will be added upon completion... |
⏳ Running benchmarks and calculating weights. DO NOT MERGE! A new commit will be added upon completion... |
⏳ Running benchmarks and calculating weights. DO NOT MERGE! A new commit will be added upon completion... |
✅ Finished running benchmarks. Updated weights have been committed to this PR branch in commit f283580. |
f283580
to
d9b0eba
Compare
d9b0eba
to
ae5db44
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm, noted a few significant weight changes but nothing alarming.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good only 2 considerations:
- While it looks like that this should be using a new instance the comments on header suggests the same CPU "Intel(R) Xeon(R) Platinum 8375C CPU @ 2.90GHz"
- We might want to rerun the database benchmarks using the latest chain state to make sure our DB benchmarks are updated
// Minimum execution time: 32_236_000 picoseconds. | ||
Weight::from_parts(33_078_000, 6399) | ||
// Minimum execution time: 48_134_000 picoseconds. | ||
Weight::from_parts(48_875_000, 6399) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
interesting increase here
4dabc03
to
25e3ed9
Compare
It is still that CPU. The big change is that the memory was increased. |
Goal
The goal of this PR is to update the benchmarks using the new standard
Closes #1786