-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
generate_index inserts ideal initial data #17247
generate_index inserts ideal initial data #17247
Conversation
98a30de
to
3d08c01
Compare
Codecov Report
@@ Coverage Diff @@
## master #17247 +/- ##
=======================================
Coverage 82.6% 82.7%
=======================================
Files 423 423
Lines 118053 118121 +68
=======================================
+ Hits 97626 97708 +82
+ Misses 20427 20413 -14 |
3d08c01
to
a2826ad
Compare
lemond colo machine, snapshot-77779424-AP7QKgrw31e5tBhtPqxejbJbYU8rs6LA97L1Qq7gqpdX.tar.zst |
a2826ad
to
d548e22
Compare
Is there test coverage that would catch a change to |
I think it's questionable that the performance improvement justifies the extra code complexity/risk. Does this build on a further change? The performance increase seems to be ~8%, is that right? |
this pr builds on the initial data change: |
I can rework this to make sure that is tested well. |
discussed with @carllin in context of other changes going on. |
5ea5beb
to
d6503cf
Compare
050712f
to
aa62281
Compare
aa62281
to
e5314c8
Compare
94c875f
to
f75aea3
Compare
updated results:
|
f75aea3
to
bc37314
Compare
@carllin fyi. reworked this extensively with stephen. |
Problem
Validator startup time is commonly experienced. Generating the index is a large part of that time.
Summary of Changes
When inserting new items, calculate the actual btreemap 'value' for initial insertion instead of blank values. Then, skip calling 'update' if the pubkey did not exist and we inserted the correct initial data.
Fixes #