mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[PR #769] [MERGED] Revert "enable FUSE read_sync by default" #1635
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#1635
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/769
Author: @orozery
Created: 5/28/2018
Status: ✅ Merged
Merged: 5/28/2018
Merged by: @ggtakec
Base:
master← Head:revert_to_async_read📝 Commits (1)
d4e86a1Revert "enable FUSE read_sync by default"📊 Changes
1 file changed (+0 additions, -16 deletions)
View changed files
📝
src/s3fs.cpp(+0 -16)📄 Description
This reverts commit
86b0921ac4.Details
I just found out that my recent commit causes single-file reading to be sometimes slower than before.
In commit
86b0921ac40ad0a34cd4202901efc2f4f774777b, I added by default the-o sync_read, to get better performance when reading multiple files at once.Since it got merged, I tested some more, and found out that single-file reading performance has gotten worst.
I therefore think we should revert this commit.
The performance of reading multiple files at-once can be better if
-o max_backgroundis increased instead.@ggtakec My apologies for this issue. Will greatly appreciate your prompt review & merge.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.