Bug 1054133
Summary: | Slow write speed when using small blocksize | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Johan Huysmans <johan.huysmans> |
Component: | fuse | Assignee: | bugs <bugs> |
Status: | CLOSED EOL | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.4.2 | CC: | bugs, gluster-bugs, jdarcy |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-07 13:49:43 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Johan Huysmans
2014-01-16 10:18:13 UTC
I don't mean to sound dismissive, but this is very much NOTABUG. It's an expected characteristic of single-threaded I/O on any distributed filesystem that tries to protect against data loss. Each write requires a network round trip. Even if the networking is local, that's a lot more overhead than local disk I/O. With 8KB writes, 47.1MB/s corresponds to 5887 IOPS, or an average round-trip latency of 0.17ms. You don't specify whether these tests were run on a single machine or a real network, but it's not clear why you'd expect better latency than that. If you want to get a better picture of what your GlusterFS installation can do, try testing with multiple threads - and ideally multiple clients. If you want to buffer writes locally then you can use the performance.write-behind-window-size volume option to buffer writes locally. This is set to a very conservative 1MB by default, because setting it larger increases vulnerability to data loss if a client fails. There are other performance-related options you can also try, but that seems like the key one you're looking for. GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5. This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "bugs". If there is no response by the end of the month, this bug will get automatically closed. GlusterFS 3.4.x has reached end-of-life. If this bug still exists in a later release please reopen this and change the version or open a new bug. GlusterFS 3.4.x has reached end-of-life.\ \ If this bug still exists in a later release please reopen this and change the version or open a new bug. |