You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Masatake Iwasaki (Jira)" <ji...@apache.org> on 2022/07/12 10:41:00 UTC
[jira] [Updated] (HDFS-16403) Improve FUSE IO performance by supporting FUSE parameter max_background
[ https://issues.apache.org/jira/browse/HDFS-16403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Masatake Iwasaki updated HDFS-16403:
------------------------------------
Fix Version/s: 3.2.4
(was: 3.2.3)
> Improve FUSE IO performance by supporting FUSE parameter max_background
> -----------------------------------------------------------------------
>
> Key: HDFS-16403
> URL: https://issues.apache.org/jira/browse/HDFS-16403
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: fuse-dfs
> Affects Versions: 3.3.0, 3.3.1
> Reporter: daimin
> Assignee: daimin
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.4.0, 3.2.4, 3.3.9
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> When we examining the FUSE IO performance on HDFS, we found that the simultaneous IO requests number are limited to a fixed number, like 12. This limitation makes the IO performance on FUSE client quite unacceptable. We did some research on this and inspired by the article [Performance and Resource Utilization of FUSE User-Space File Systems|https://dl.acm.org/doi/fullHtml/10.1145/3310148], clearly the FUSE parameter '{{{}max_background{}}}' decides the simultaneous IO requests number, which is 12 by default.
> We add 'max_background' to fuse_dfs mount options, the FUSE kernel will take effect when an option value is given.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org