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
At the moment, performance tests are done with different values and the value is yet to finalized based on the perf tests
Additiona info: I have created a doc bug[1] to update the features.shard-block-size to 64MB with RHV-RHGS guide. [1] - https://bugzilla.redhat.com/show_bug.cgi?id=1489743
https://review.gluster.org/#/c/18243/
https://code.engineering.redhat.com/gerrit/118074
upstream mainline : https://review.gluster.org/#/c/18243/ upstream 3.12 : https://review.gluster.org/#/c/18305/ downstream : https://code.engineering.redhat.com/gerrit/118074
The original intent of the bug is to update the virt profile to have the shard-block-size as 64MB. But in actual, the default shard block size is now updated. Tested with RHGS 3.3.1 interim build ( glusterfs-3.8.4-48.el7rhgs ) The default shard size is 64MB [root@ ~]# gluster volume get test shard-block-size Option Value ------ ----- features.shard-block-size 64MB
Looks good to me, Pratik!
Changes in Doc Text to make it concise.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3276