+++ 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): ------------------------------------------------------------- RHGS 3.2.0 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 Rejy M Cyriac on 2017-07-12 07:49:52 EDT --- At the 'RHGS 3.3.0 - Release Blocker Bug Triage and Status Check' meeting on 12 July, it was decided to NOT ACCEPT this BZ for fix at the RHGS 3.3.0 release Need details around which RHHI release is being targeted, release time-lines, and clarity on the expected value for the parameter Bug may be re-proposed when clarity on required value(s) and the dependent RHHI release is known --- Additional comment from Red Hat Bugzilla Rules Engine on 2017-07-12 07:49:55 EDT --- This BZ having been considered, and subsequently not approved to be fixed at the RHGS 3.3.0 release, is being proposed for the next minor release of RHGS
https://review.gluster.org/#/c/18243/
Moving to ON_QA as dependent bug has moved state
This bug is fixed with the RHGS product, where the default shard size is updated to 64MB. Verified with the same with RHGS 3.3.1 interim build ( glusterfs-3.8.4-48.el7rhgs ) [root@ ~]# gluster volume get test shard-block-size Option Value ------ ----- features.shard-block-size 64MB