mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #616] 50x slowdown compared to s3cmd #350
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#350
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?
Originally created by @tachim on GitHub (Jun 6, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/616
Additional Information
The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.
Amazon Simple Storage Service File System V1.79(commit:unknown) with GnuTLS(gcrypt)Version of fuse being used (pkg-config --modversion fuse)
ii fuse 2.9.4-1ubuntu3 amd64 Filesystem in UserspaceSystem information (uname -a)
Linux DL2 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/LinuxDistro (cat /etc/issue)
Ubuntu 16.04 LTSs3fs command line used (if applicable)
if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages
Details about issue
When we access a file in S3FS to do an operation like md5sum, the download speed observed with bmon is 50x slower than the speed we would get downloading the file with s3cmd (500KB/s vs 50MB/s). Any ideas if there's some configuration change that can match that perf?
@danielpflood commented on GitHub (Oct 5, 2017):
I would like to know also
@gaul commented on GitHub (Jan 24, 2019):
Could you test again against master? It includes some optimizations that may help.
@gaul commented on GitHub (Jun 25, 2019):
Closing due to inactivity.