[Bugs] [Bug 1492026] New: set the shard-block-size to 64MB in virt profile

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1492026

            Bug ID: 1492026
           Summary: set the shard-block-size to  64MB in virt profile
           Product: GlusterFS
           Version: 3.12
         Component: sharding
          Keywords: Triaged
          Severity: urgent
          Assignee: bugs at gluster.org
          Reporter: kdhananj at redhat.com
        QA Contact: bugs at gluster.org
                CC: amukherj at redhat.com, bugs at gluster.org,
                    rcyriac at redhat.com, rhinduja at redhat.com,
                    rhs-bugs at redhat.com, sabose at redhat.com,
                    sasundar at redhat.com, storage-qa-internal at redhat.com
        Depends On: 1489823
            Blocks: 1468969



+++ This bug was initially created as a clone of Bug #1489823 +++

+++ 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

--- Additional comment from Worker Ant on 2017-09-08 08:35:56 EDT ---

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 at redhat.com)

--- Additional comment from Worker Ant on 2017-09-13 05:37:32 EDT ---

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 at redhat.com)

--- Additional comment from Worker Ant on 2017-09-13 08:46:42 EDT ---

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 at redhat.com)

--- Additional comment from Worker Ant on 2017-09-13 23:23:19 EDT ---

COMMIT: https://review.gluster.org/18243 committed in master by Pranith Kumar
Karampuri (pkarampu at redhat.com) 
------
commit e4a59b384f5bbaaeb937a53cef64f4e388f85153
Author: Krutika Dhananjay <kdhananj at redhat.com>
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 at redhat.com>
    Reviewed-on: https://review.gluster.org/18243
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Tested-by: Sunil Kumar Acharya <sheggodu at redhat.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1468969
[Bug 1468969] set the shard-block-size to  64MB in virt profile
https://bugzilla.redhat.com/show_bug.cgi?id=1489823
[Bug 1489823] set the shard-block-size to  64MB in virt profile
-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.