Bug 1450898 - [Perf] Huge drop in metadata workload on smbv3 on *2
Summary: [Perf] Huge drop in metadata workload on smbv3 on *2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: samba
Version: rhgs-3.3
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: RHGS 3.3.0
Assignee: Michael Adam
QA Contact: Karan Sandha
URL:
Whiteboard:
Depends On:
Blocks: 1417151
TreeView+ depends on / blocked
 
Reported: 2017-05-15 11:16 UTC by Karan Sandha
Modified: 2017-09-21 04:43 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.8.4-28
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-21 04:43:23 UTC
Embargoed:

Attachments (Terms of Use)
3.2 profile (deleted)
2017-05-15 11:16 UTC, Karan Sandha 		no flags Details
3.3 volume profile (14.47 KB, application/x-gzip)
2017-05-15 11:17 UTC, Karan Sandha 		no flags Details
3.2 profile (13.29 KB, application/x-gzip)
2017-05-15 11:17 UTC, Karan Sandha 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2774 0 normal SHIPPED_LIVE glusterfs bug fix and enhancement update 2017-09-21 08:16:29 UTC

Description Karan Sandha 2017-05-15 11:16:25 UTC 
Description of problem:
Ranging from 
35% in stats 
30% in chmod 
11% in ls-l
9%  in readdir 
 drop in the all the meatdata workloads

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

How reproducible:
100%

Steps to Reproduce:
1. run all the metadata workloads on SMB v3 access protocol
2. compare the results with 3.2

Actual results:
regression observed on all the metadata workloads

Expected results:


Additional info:
Comment 2 Karan Sandha 2017-05-15 11:17:30 UTC 
Created attachment 1278918 [details]
3.3 volume profile
Comment 3 Karan Sandha 2017-05-15 11:17:52 UTC 
Created attachment 1278919 [details]
3.2 profile
Comment 12 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
Note You need to log in before you can comment on or make changes to this bug.