An experiment to see how delayed_write and read_ahead behave#4750
Closed
An experiment to see how delayed_write and read_ahead behave#4750
Conversation
Technically, this shouldn't violate safety as an fsync will still flush out the data synchronously. We used to have some versions of these previously done at the couch_file or couch_db_updater level. There was an 8KB read-ahead and a delayed commit option. These ones are a bit simpler and easier as they are using OTP provided functionality. Locally on MacOS I haven't see a huge perf difference (with fabric_bench) but perhaps this might help in case with a remote block devices where write IO calls are throttled or somehow behave better if they are in larger blocks.
nickva
force-pushed
the
experiment-file-io-opts
branch
from
6870a41 to
93b8786
Compare
Contributor
Author
|
Closing as there wasn't as much interest in this |
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
1 participant
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.
Technically, this shouldn't violate safety as an fsync will still flush out the data synchronously.
We used to have some versions of these previously done at the couch_file or couch_db_updater level. There was an 8KB read-ahead and a delayed commit option. These ones are a bit simpler and easier as they are using OTP provided functionality.
Locally on MacOS I haven't see a huge perf difference (with fabric_bench) but perhaps this might help in case with a remote block devices where write IO calls are throttled or somehow behave better if they are in larger blocks.