[ResourceMngmt] Add new API CacheReservationManager::GetDummyEntrySize() #9072
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.
Note: it might conflict with another CRM related PR #9071 and so will merge after that's merged.
Context:
As
CacheReservationManager
being used by more memory users, it is convenient to retrieve the dummy entry size forCacheReservationManager
instead of hard-coding256 * 1024
in writing tests. Plus it allows more flexibility to change our implementation on dummy entry size.A follow-up PR is needed to replace those hard-coded dummy entry size value in
db_test2.cc
,db_write_buffer_manager_test.cc
,write_buffer_manager_test.cc
,table_test.cc
and the ones introduced in #9072 (comment).Summary:
kDummyEntrySize
through public staticCacheReservationManager::GetDummyEntrySize()
Test: