[Bugs] [Bug 1437330] New: Sharding: Fix a performance bug

[bugzilla at redhat.com]

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

            Bug ID: 1437330
           Summary: Sharding: Fix a performance bug
           Product: GlusterFS
           Version: 3.8
         Component: sharding
          Keywords: Triaged
          Assignee: bugs at gluster.org
          Reporter: kdhananj at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org
        Depends On: 1436739
            Blocks: 1437326



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

Description of problem:

As per Sanjay Rao's inputs, there was a performance drop in random reads fio
workload when run through vms hosted on sharded volumes.

Volume profile indicated a big difference between the number of lookups sent by
FUSE and number of lookups received by individual bricks.

Through code reading, it was found that there is a performance bug in shard
which was causing the translator to trigger unusually high number of lookups
for cache invalidation even when there was no modification to the file.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Worker Ant on 2017-03-28 10:23:33 EDT ---

REVIEW: https://review.gluster.org/16961 (features/shard: Pass the correct iatt
for cache invalidation) posted (#1) for review on master by Krutika Dhananjay
(kdhananj at redhat.com)

--- Additional comment from Worker Ant on 2017-03-30 01:48:38 EDT ---

REVIEW: https://review.gluster.org/16961 (features/shard: Pass the correct iatt
for cache invalidation) posted (#2) for review on master by Krutika Dhananjay
(kdhananj at redhat.com)


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1436739
[Bug 1436739] Sharding: Fix a performance bug
https://bugzilla.redhat.com/show_bug.cgi?id=1437326
[Bug 1437326] Sharding: Fix a performance bug
-- 
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.