-
Notifications
You must be signed in to change notification settings - Fork 72
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 purges as Pri::LOW instead of HIGH #34
Comments
Unit tests passed. |
@erez-speedb this has been accidentally merged to main without running the performance tests. Please run them on commit |
#183 has been merged. @erez-speedb, please run the aforementioned test on and before commit |
@isaac-io we should also change the description here right? include/rocksdb/options.h |
Yes. Would you be able to open a PR to fix this? I don't think that this requires an accompanying issue. |
since purges are now set from the LOW pri pool, the bg job scheduled when background_purge_on_iterator_cleanup is true is scheduled in the compaction queue
since purges are now set from the LOW pri pool, the bg job scheduled when background_purge_on_iterator_cleanup is true is scheduled in the compaction queue
since purges are now set from the LOW pri pool, the bg job scheduled when background_purge_on_iterator_cleanup is true is scheduled in the compaction queue
since purges are now set from the LOW pri pool, the bg job scheduled when background_purge_on_iterator_cleanup is true is scheduled in the compaction queue
since purges are now set from the LOW pri pool, the bg job scheduled when background_purge_on_iterator_cleanup is true is scheduled in the compaction queue
since purges are now set from the LOW pri pool, the bg job scheduled when background_purge_on_iterator_cleanup is true is scheduled in the compaction queue
since purges are now set from the LOW pri pool, the bg job scheduled when background_purge_on_iterator_cleanup is true is scheduled in the compaction queue
since purges are now set from the LOW pri pool, the bg job scheduled when background_purge_on_iterator_cleanup is true is scheduled in the compaction queue
since purges are now set from the LOW pri pool, the bg job scheduled when background_purge_on_iterator_cleanup is true is scheduled in the compaction queue
since purges are now set from the LOW pri pool, the bg job scheduled when background_purge_on_iterator_cleanup is true is scheduled in the compaction queue
reason for the change:
purges are deletions of obsolete compaction files. by doing the cleanup of these files in the HIGH priority thread pool, the flushes are hindered. we’d like to avoid disturbing the flushes and instead do this cleaning job as a LOW priority.
other notes:
this change is also favored when using the SPDB-680 (delete a file in chunks) feature since with it, the deletion takes longer which would further stall the flushes.
also, consider changing priority here as well db/db_impl/db_impl_compaction_flush.cc:
The text was updated successfully, but these errors were encountered: