+++ This bug was initially created as a clone of Bug #1468969 +++ Description of problem: ----------------------- The better performance was observed with the shard-size of 128MB. Virt profile should have this attribute and so its set on the volume when the volume is optimized for virt-profile Version-Release number of selected component (if applicable): ------------------------------------------------------------- How reproducible: ----------------- NA Steps to Reproduce: ------------------- NA Actual results: --------------- Shard-size is set to 4MB Expected results: ----------------- shard-size should be set to 128MB so that perf improvement is observed --- Additional comment from SATHEESARAN on 2017-07-10 02:52:40 EDT --- At the moment, performance tests are done with different values and the value is yet to finalized based on the perf tests --- Additional comment from Atin Mukherjee on 2017-09-07 06:32:37 EDT --- When would the recommended shard-size can be provided so that the required changes can be done? --- Additional comment from SATHEESARAN on 2017-09-07 06:34:14 EDT --- (In reply to Atin Mukherjee from comment #4) > When would the recommended shard-size can be provided so that the required > changes can be done? The recommended value is 64MB
REVIEW: https://review.gluster.org/18243 (features/shard: Change default shard-block-size to 64MB) posted (#1) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: https://review.gluster.org/18243 (features/shard: Change default shard-block-size to 64MB) posted (#2) for review on master by Krutika Dhananjay (kdhananj)
REVIEW: https://review.gluster.org/18243 (features/shard: Change default shard-block-size to 64MB) posted (#3) for review on master by Krutika Dhananjay (kdhananj)
COMMIT: https://review.gluster.org/18243 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit e4a59b384f5bbaaeb937a53cef64f4e388f85153 Author: Krutika Dhananjay <kdhananj> Date: Fri Sep 8 18:04:50 2017 +0530 features/shard: Change default shard-block-size to 64MB Change-Id: I55fa87e07136cff10b0d725ee24dd3151016e64e BUG: 1489823 Signed-off-by: Krutika Dhananjay <kdhananj> Reviewed-on: https://review.gluster.org/18243 Reviewed-by: Pranith Kumar Karampuri <pkarampu> Smoke: Gluster Build System <jenkins.org> Tested-by: Sunil Kumar Acharya <sheggodu> CentOS-regression: Gluster Build System <jenkins.org>
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.13.0, please open a new bug report. glusterfs-3.13.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] http://lists.gluster.org/pipermail/announce/2017-December/000087.html [2] https://www.gluster.org/pipermail/gluster-users/