-
Notifications
You must be signed in to change notification settings - Fork 74
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
Set initiate_wbm_flushes to the same default value used by the WBM (true) (#480) #510
Set initiate_wbm_flushes to the same default value used by the WBM (true) (#480) #510
Conversation
6e937f9
to
44468a5
Compare
ef9ec63
to
d522a58
Compare
@Yuval-Ariel Please review my latest commit. |
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
@Yuval-Ariel I have pushed the branch 480-set-initiate_wbm_flushes-to-true-in-tools after rebase and conflict resolution |
this PR is already closed and merged 😕 |
* Set initiate_wbm_flushes to the same default value used by the WBM (true) * Remove sanitizations of wbm flags in the db_bench, db_stress, and db_crashtest.py * Create a WBM unconditionally in db_bench / db_stress (using the applicable flags)
* Set initiate_wbm_flushes to the same default value used by the WBM (true) * Remove sanitizations of wbm flags in the db_bench, db_stress, and db_crashtest.py * Create a WBM unconditionally in db_bench / db_stress (using the applicable flags)
Please note that now the user of db_bench / db_stress must either override the default of initiate_wbm_flushes to false or leave it true, but set the db_write_buffer_size flag to a value > 0