Make fuse param max-write tunable #4500
Comments
chen1195585098
added a commit
to chen1195585098/glusterfs
that referenced
this issue
Mar 23, 2025
Since kernel 4.20, the FUSE driver introduced the max-pages feature. To enhance write performance, this patch exports a new mount option fuse-max-write to let users specify the maximum write bytes for FUSE. The max-pages parameter for fuse connection will be adjusted accordingly. Updates: gluster#4500 Signed-off-by: chenjinhao <1195585098@qq.com>
chen1195585098
added a commit
to chen1195585098/glusterfs
that referenced
this issue
Apr 15, 2025
Since kernel 4.20, the FUSE driver introduced the max-pages feature. To enhance write performance, this patch exports mount options fuse-max-write and fuse-max-read to let users specify the maximum write/read bytes for FUSE. The max-pages parameter for fuse connection will be adjusted accordingly. Updates: gluster#4500 Signed-off-by: chenjinhao <1195585098@qq.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The kernel FUSE driver introduced a new feature called
max-pagesstarting from kernel version 4.20. This feature allows an IO request to utilize up to256pages at most. However, in the case of GlusterFS, the maximum write request size is currently limited to128K, which corresponds to32pages. As a result, when handling a write request of 1M data, it will be split into8separate requests. This fragmentation can potentially lead to a FUSE IO bottleneck.Given this situation, it would be beneficial to investigate whether we can adjust the size of the write request in GlusterFS to better leverage the max-pages feature and thereby improve write performance.
The text was updated successfully, but these errors were encountered: