Bug 908277
| Summary: | Poor performance with gluster volume set command execution | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Pranith Kumar K <pkarampu> |
| Component: | glusterd | Assignee: | Pranith Kumar K <pkarampu> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | mainline | CC: | bugs, gluster-bugs |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.6.0beta1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-11-11 08:23:31 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
Pranith Kumar K
2013-02-06 10:21:43 UTC
The latency is due to O_SYNC and fsync in gluster-store, which are necessary. REVIEW: http://review.gluster.org/7370 (mgmt/gluster: Use fsync instead of O_SYNC) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu) Performance results with this new change:
Without this change:
[root@localhost ~]# for i in {1..3}; do time gluster volume set r2 performance.read-ahead off; done
volume set: success
real 0m1.897s
user 0m0.233s
sys 0m0.088s
volume set: success
real 0m2.241s
user 0m0.228s
sys 0m0.081s
volume set: success
real 0m2.544s
user 0m0.130s
sys 0m0.047s
With the change:
[root@localhost ~]# for i in {1..3}; do time gluster volume set r2 performance.read-ahead off; done
volume set: success
real 0m0.569s
user 0m0.132s
sys 0m0.038s
volume set: success
real 0m0.485s
user 0m0.130s
sys 0m0.034s
volume set: success
real 0m0.840s
user 0m0.125s
sys 0m0.031s
REVIEW: http://review.gluster.org/7370 (mgmt/gluster: Use fsync instead of O_SYNC) posted (#3) for review on master by Pranith Kumar Karampuri (pkarampu) COMMIT: http://review.gluster.org/7370 committed in master by Anand Avati (avati) ------ commit 3a35f975fceb89c5ae0e8e3e189545f6fceaf6e5 Author: Pranith Kumar K <pkarampu> Date: Thu May 1 10:29:54 2014 +0530 mgmt/gluster: Use fsync instead of O_SYNC Glusterd uses O_SYNC to write to temp file then performs renames to the actual file and performs fsync on parent directory. Until this rename happens syncing writes to the file can be deferred. In this patch O_SYNC open of temp file is removed and fsync of the fd before rename is done. Change-Id: Ie7da161b0daec845c7dcfab4154cc45c2f49d825 BUG: 908277 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/7370 Reviewed-by: Krishnan Parthasarathi <kparthas> Reviewed-by: Raghavendra Bhat <raghavendra> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati> A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/ This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users |