-
Notifications
You must be signed in to change notification settings - Fork 206
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
feat: expose more rocksdb options #1033
Merged
ShiKaiWi
merged 7 commits into
apache:main
from
zouxiang1993:expose-more-rocksdb-options
Jun 27, 2023
Merged
feat: expose more rocksdb options #1033
ShiKaiWi
merged 7 commits into
apache:main
from
zouxiang1993:expose-more-rocksdb-options
Jun 27, 2023
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
chunshao90
reviewed
Jun 26, 2023
ShiKaiWi
reviewed
Jun 26, 2023
zouxiang1993
changed the title
Expose more rocksdb options
feat: expose more rocksdb options
Jun 27, 2023
ShiKaiWi
reviewed
Jun 27, 2023
Co-authored-by: WEI Xikai <ShiKaiWi@users.noreply.github.com>
zouxiang1993
force-pushed
the
expose-more-rocksdb-options
branch
from
June 27, 2023 03:29
4839599
to
989b419
Compare
ShiKaiWi
approved these changes
Jun 27, 2023
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.
LGTM
dust1
pushed a commit
to dust1/ceresdb
that referenced
this pull request
Aug 9, 2023
## Rationale Now rocksdb as the wal, it is easy to become the bottleneck of write. ## Detailed Changes 1. expose more rocksdb options to avoid write stall 2. introduce rocksdb's FIFO compaction style, which makes rocksdb looks like a message queue. (FIFO is more suitable for time-series data, maybe it will become the default option in the future.) ## Test Plan I will test it in my test env. --------- Co-authored-by: WEI Xikai <ShiKaiWi@users.noreply.github.com>
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.
Rationale
Now rocksdb as the wal, it is easy to become the bottleneck of write.
Detailed Changes
(FIFO is more suitable for time-series data, maybe it will become the default option in the future?)
Test Plan
I will test it in my test env.