Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1455872

Summary: [Perf]: 25% regression on sequential reads on EC over SMB3
Product: [Community] GlusterFS Reporter: Milind Changire <mchangir>
Component: open-behindAssignee: Milind Changire <mchangir>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: mainlineCC: amukherj, aspandey, bturner, bugs, pgurusid, pkarampu, rcyriac, rgowdapp, rhinduja, rhs-bugs, storage-qa-internal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-5.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1419807 Environment:
Last Closed: 2018-10-23 15:06:00 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:
Bug Depends On:    
Bug Blocks: 1419807    

Comment 1 Milind Changire 2017-05-26 10:54:30 UTC
Description:
There is a performance drop for large files if opened with a delay.

Comment 2 Worker Ant 2017-05-26 10:57:15 UTC
REVIEW: https://review.gluster.org/17377 (performance/open-behind: open early for large files) posted (#5) for review on master by Milind Changire (mchangir)

Comment 3 Worker Ant 2018-07-14 13:02:14 UTC
REVIEW: https://review.gluster.org/20511 (performance/open-behind: don't use anonymous fds for reads by default) posted (#1) for review on master by Raghavendra G

Comment 4 Worker Ant 2018-08-03 00:59:20 UTC
COMMIT: https://review.gluster.org/20511 committed in master by "Raghavendra G" <rgowdapp> with a commit message- performance/open-behind: don't use anonymous fds for reads by default

anonymous fds interfere with working of read-ahead as read-ahead won't
be able to store its cache in fd. Also, as seen in bz 1455872,
anonymous fds also affect performance of large file sequential reads
as the cost of opening fd for each read on brick stack is
significant. So, have a proper fd which enables read-ahead to store
its cache and brick stack to reuse the fd during reads.

With this change test
tests/bugs/snapshot/bug-1167580-set-proper-uid-and-gid-during-nfs-access.t
fails consistently. The failure can also be seen with open-behind
off. bz 1611532 has been filed to track the issue with test. Thanks to
Rafi <rkavunga> for assistance provided in debugging test
failure.

Change-Id: Ifa52d8ff017f115e83247f3396b9d27f0295ce3f
Signed-off-by: Raghavendra G <rgowdapp>
Fixes: bz#1455872

Comment 5 Shyamsundar 2018-10-23 15:06:00 UTC
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-5.0, please open a new bug report.

glusterfs-5.0 has been announced on the Gluster mailinglists [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] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/