mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[PR #371] [MERGED] Always set stats cache for opened file #1484
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#1484
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/371
Author: @ggtakec
Created: 3/13/2016
Status: ✅ Merged
Merged: 3/13/2016
Merged by: @ggtakec
Base:
master← Head:master📝 Commits (1)
67efc11Always set stats cache for opened file📊 Changes
3 files changed (+63 additions, -11 deletions)
View changed files
📝
src/cache.cpp(+35 -3)📝
src/cache.h(+6 -2)📝
src/s3fs.cpp(+22 -6)📄 Description
Fixed https://github.com/s3fs-fuse/s3fs-fuse/issues/370.
When copying a file(object), FUSE will call continuously s3fs_write evey 4KB(depending on the OS).
At this time FUSE will confirm the xattr of security.capability, if it is deemed necessary.
As a result, s3fs_getxattr will also be called in 64KB units.
And the HEAD request is sent to the S3 by evey s3fs_getxattr call, when s3fs is gave max_stat_cache_size=0 option or s3fs cached out the stats data for the file.
This causes a decrease in performance.
For solving this problem, s3fs is changed that the stats information for the file is always cached while the file is open.
After closing the file, the cache life depends on the setting of the max_stat_cache_size and it will be cleared.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.