[Enhancement] Support remove immutable memtable for cloud native pindex (backport #54178) #54408
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.
Why I'm doing:
Cloud native persistent index memtable support multiple memtables include one mutable memtable and multiple immutable memtables. However, multiple memtables will use more memory and generate many small sst files which increase read cost. Apart from that, flushing the memtable is not the bottleneck of the apply process, so having a single memtable is more appropriate.
What I'm doing:
Support single memtable for cloud native persistent index.
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist: