-
Notifications
You must be signed in to change notification settings - Fork 973
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
Apply load improvements #4539
base: master
Are you sure you want to change the base?
Apply load improvements #4539
Conversation
- Use the new function that doesn't access storage, but does emit events - Generate synthetic bucket list with configurable number of entries/ledgers - Tighten the resources estimation
Some additional changes the I didn't want to push to this PR just yet - dmkozh#1 |
mDataEntrySize); | ||
} | ||
|
||
for (uint32_t i = 0; i < cfg.APPLY_LOAD_BL_SIMULATED_LEDGERS; ++i) |
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.
Should we separate the command to populate the bucket list from apply-load
? The data entry count will need to be communicated between the two runs, but this would allow you to copy the bucket list files and rerun with different parameters instead of waiting for bucket list generation on each run.
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.
Yeah, I've considered that, but didn't have time for implementation. An alternative to an additional command would be to just only generate the BL if it doesn't contain an expected entry for the maximum id (this has a small footgun if we want to shrink the BL, but I don't think that's a significant issue). This way we won't need to add any additional commands.
Description
Checklist
clang-format
v8.0.0 (viamake format
or the Visual Studio extension)