Description: There is a performance drop for large files if opened with a delay.
REVIEW: https://review.gluster.org/17377 (performance/open-behind: open early for large files) posted (#5) for review on master by Milind Changire (mchangir)
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
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
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/