-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Make a single call to run_pending_tasks
to evict as many entries as possible from the cache
#417
Merged
Conversation
This file contains 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
tatsuya6502
changed the title
Make
Make a single call to Apr 14, 2024
run_pending_tasks
to evict more entries from the cache at oncerun_pending_tasks
to evict as many entries as possible from the cache
A CI job for Kani verifier is failing with compile errors on We will address the Kani and |
- Disable the eviction batch size when the eviction listener is not set to the cache. - So single `run_pending_tasks` call should remove all entries that can be evicted from the cache. - Add a hard-coded maintenance task timeout duration. - When the eviction listener is set, `run_pending_tasks` should stop (return) after the maintenance task timeout is elapsed. - This is a safe-guard to prevent the maintenance task from running long time when the user wrote a slow eviction listener. - In older versions, the batch size was used to limit the time spent on the maintenance task. - Not that `run_pending_tasks` checks the timeout only after processing a batch of entries, so `run_pending_tasks` can run longer than the timeout duration. - Reduce the size of the read op and write op channels.
Apply the same change of `future::Cache` to `sync` caches.
possible from the cache Ensure the loop in the `do_run_pending_tasks` method is eventually stopped.
possible from the cache Tweak some unit tests.
tatsuya6502
force-pushed
the
evict-more-entries-at-once
branch
from
April 16, 2024 10:02
4d8de7c
to
dfbbe3f
Compare
tatsuya6502
commented
Apr 16, 2024
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.
Merging.
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.
Fixes #408.
Changes
This PR ensures that a single call to
run_pending_tasks
to evict as many entries as possible from the cache.run_pending_tasks
call should remove all the entries that can be evicted from the cache.run_pending_tasks
should stop (return) after the timeout duration is elapsed.run_pending_tasks
checks the timeout only after processing a batch of entries, sorun_pending_tasks
can run longer than the timeout duration.Tests
run_pending_tasks
to evict as many entries as possible.