Repository navigation
Add option write buffer size - #39
Merged
kasperisager merged 3 commits intoSep 12, 2026
Merged
Conversation
kasperisager
requested changes
Sep 11, 2026
Co-authored-by: Kasper Isager Dalsgarð <kasperisager@hey.com>
kasperisager
approved these changes
Sep 12, 2026
This was referenced Sep 14, 2026
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
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.
In order to reduce initial disk allocation cost when creating hundreds of instances of rocksdb;
I've added column family option
write_buffer_size.The default is 64mb which causes each rocksdb instance folder to occupy about 75mb on first write.
Lowering
write_buffer_sizereduces the initial allocation cost I'm using about 4mb per instance.I do not recommend using this optimization in production, am using it for diagnostics.