[GH-ISSUE #767] Any way to reduce CPU usage of s3fs? #439

New issue

Closed

opened 2026-03-04 01:45:35 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:45:35 +03:00

Owner

Originally created by @atomrocktech on GitHub (May 24, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/767

Version of s3fs being used (s3fs --version)

V1.82

Version of fuse being used (pkg-config --modversion fuse)

V2.9.4

System information (uname -r)

4.4.0-1048-aws

Distro (cat /etc/issue)

Ubuntu16.04.3 LTS \n \l

s3fs command line used (if applicable)

s3fs bucket /opt/s3trunk -o passwd_file=/etc/passwd-s3fs -o endpoint=ap-northeast-1 -o allow_other

s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)

if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages
Get nothing when using "cat /var/log/syslog | grep s3fs"

Details about issue

Hello,
Im using EC2 with s3fs and mount S3 bucket as a file server,
but I found that CPU usage and I/O are pretty high, Is there any way to reduce them?

BR,
Johnny

Originally created by @atomrocktech on GitHub (May 24, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/767 #### Version of s3fs being used (s3fs --version) V1.82 #### Version of fuse being used (pkg-config --modversion fuse) V2.9.4 #### System information (uname -r) 4.4.0-1048-aws #### Distro (cat /etc/issue) Ubuntu16.04.3 LTS \n \l #### s3fs command line used (if applicable) s3fs bucket /opt/s3trunk -o passwd_file=/etc/passwd-s3fs -o endpoint=ap-northeast-1 -o allow_other #### s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ Get nothing when using "cat /var/log/syslog | grep s3fs" ### Details about issue Hello, Im using EC2 with s3fs and mount S3 bucket as a file server, but I found that CPU usage and I/O are pretty high, Is there any way to reduce them? ![image](https://user-images.githubusercontent.com/28853173/40467744-963d5602-5f5d-11e8-9a65-000320cc9b90.png) BR, Johnny

kerem closed this issue

2026-03-04 01:45:36 +03:00

kerem commented

2026-03-04 01:45:37 +03:00

Author

Owner

@gaul commented on GitHub (Jan 24, 2019):

This is unusually high. Could you attach a profiler to see where s3fs spends its time or maybe just check a few stack traces via gdb?

@gaul commented on GitHub (Jan 24, 2019): This is unusually high. Could you attach a profiler to see where s3fs spends its time or maybe just check a few stack traces via `gdb`?

kerem commented

2026-03-04 01:45:37 +03:00

Author

Owner

@gaul commented on GitHub (Jan 24, 2019):

Also updatedb running against the mountpoint can cause these symptoms:

https://stackoverflow.com/questions/52372095/tracking-down-s3-costs-s3fs

@gaul commented on GitHub (Jan 24, 2019): Also `updatedb` running against the mountpoint can cause these symptoms: https://stackoverflow.com/questions/52372095/tracking-down-s3-costs-s3fs

kerem commented

2026-03-04 01:45:37 +03:00

Author

Owner

@gaul commented on GitHub (Jun 25, 2019):

Closing due to inactivity.

@gaul commented on GitHub (Jun 25, 2019): Closing due to inactivity.