resmgr: block cache save during initial sync.#640
Merged
askervin merged 1 commit intocontainers:mainfrom Mar 10, 2026
Merged
Conversation
Collaborator
|
Looks good. New methods still need to be added to mock objects for the unit tests to work. (This is what golangci-lint complains, too.) |
klihub
force-pushed
the
fixes/block-cache-save
branch
from
9078cd7 to
3660d73
Compare
Collaborator
Author
Argh... always tend to forget. Fixed. |
klihub
force-pushed
the
fixes/block-cache-save
branch
from
3660d73 to
f546fbe
Compare
When doing a mass release followed by a mass allocation during initial sync, don't save the cache after each operation. Instead block cache saves and unblock them once the bulk/batch operation is complete, saving the cache once in the end. Signed-off-by: Krisztian Litkey <krisztian.litkey@intel.com>
klihub
force-pushed
the
fixes/block-cache-save
branch
from
f546fbe to
efc5001
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When doing a mass release followed by a mass allocation during initial sync, don't save the cache after each operation. Instead block cache saves and unblock them once the bulk/batch operation is complete, saving the cache once in the end.