Bug 1450841

Summary: [Perf] 17% drop in small file "delete-rename" on smbv3 on *2
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Karan Sandha <ksandha>
Component: sambaAssignee: Mohammed Rafi KC <rkavunga>
Status: CLOSED ERRATA QA Contact: Karan Sandha <ksandha>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.3CC: amukherj, asoman, ksandha, rhinduja, rhs-smb
Target Milestone: ---Keywords: Regression
Target Release: RHGS 3.3.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.8.4-28 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-21 04:43:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1417151    
Attachments:
Description Flags
3.3 volume profile
none
volume profile 3.2 none

Description Karan Sandha 2017-05-15 09:31:20 UTC
Created attachment 1278897 [details]
3.3 volume profile

Description of problem:
34% drop in smallfile delete-renames on SMB v3 from 3.2

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

How reproducible:
100%

Steps to Reproduce:
1. run a smallfiles using parameter "delete-renamed" using 4 clients and 4 server
2. compare the  throughput/files read with last two release 3.2 and 3.3


Actual results:
regression observed over the two releases 3.2 & 3.3

Expected results:
no regression should be observed or the drop should be between -5%

Additional info:

Comment 2 Karan Sandha 2017-05-15 09:32:34 UTC
Created attachment 1278898 [details]
volume profile 3.2

Comment 9 Atin Mukherjee 2017-06-05 12:45:19 UTC
upstream patch : https://review.gluster.org/17465

Comment 11 Atin Mukherjee 2017-06-13 07:51:50 UTC
downstream patch : https://code.engineering.redhat.com/gerrit/108901

Comment 15 errata-xmlrpc 2017-09-21 04:43:23 UTC
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:2774