-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[wip] bench nodedb sync thresholds #17405
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
Open
AskAlexSharov
wants to merge
20
commits into
main
Choose a base branch
from
alex/nodedb_33
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
taratorio
pushed a commit
that referenced
this pull request
Oct 13, 2025
current benchmarks show that after 5mb speed doesn't grow - but benchmarks are very unreliable yet (don't know yet why). form another side - user reported best performance at 20mb. So, setting to 5mb for now - until getting more bench-driven evidence. ``` BenchmarkSyncPeriodDefault/20kb-16 1383 4112960 ns/op 20.00 ms_worst BenchmarkSyncPeriodDefault/200kb-16 7178 1106435 ns/op 15.00 ms_worst BenchmarkSyncPeriodDefault/1mb-16 18532 328017 ns/op 14.00 ms_worst BenchmarkSyncPeriodDefault/2mb-16 33478 193897 ns/op 12.00 ms_worst BenchmarkSyncPeriodDefault/5mb-16 72160 100291 ns/op 13.00 ms_worst BenchmarkSyncPeriodDefault/10mb-16 77170 99663 ns/op 12.00 ms_worst BenchmarkSyncPeriodDefault/20mb-16 67716 97053 ns/op 15.00 ms_worst BenchmarkSyncPeriodDefault/40mb-16 74607 97140 ns/op 13.00 ms_worst ``` for #14182 it also depends on: #17284 (because it fixing bug of wrong `WANNA_RECOVERY` assert - Erigon can't start without this fix). But unlikely we will port new mdbx to `3.2` (will see how it work in `main`). will continue work on benches in #17405
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
benchmarks are unreliable (each next run - degradating):
current results: