Bug 1477786 - [GSS]More than 2 smbd processes on a gluster node make application performance dramatically slow down
Summary: [GSS]More than 2 smbd processes on a gluster node make application performanc...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: disperse
Version: rhgs-3.2
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: RHGS 3.5.0
Assignee: Ashish Pandey
QA Contact: Upasana
URL:
Whiteboard:
Depends On: 1703455
Blocks: 1696803
TreeView+ depends on / blocked
 
Reported: 2017-08-03 00:35 UTC by liuwei
Modified: 2020-12-14 09:20 UTC (History)
14 users (show)

Fixed In Version: glusterfs-6.0-2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-30 12:19:37 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3249 0 None None None 2019-10-30 12:20:11 UTC

Description liuwei 2017-08-03 00:35:31 UTC
Description of problem:

1. Poor performance is related to the number of the client, not the working thread.
   And the number of the client is related to the number of smbd process.
   Poor performance can be reproduce every time when there are more than 2 clients.

     1 node with 8 working threads,         no performance issue.          Number of smbd process is 1
     2 node with 1 working thread for each, Poor performance was observed. Number of smbd process is 2

2. Working thread on client will receive and compress data, and then copy the data to gluster EC volume. Each thread will copy data to an independence directory, 
   So there will not be two or more thread working on same directory, data will copy to separately directory by working thread.

3. Gluster server is running with RHGS 3.2 + samba(gluster_vfs) + CTDB(3 VIPs) on 3 nodes.
   volume is EC(4+2) on 3 nodes, with 2 bricks on each node.
   Client is windows server 2012.

4. Workload is to copy 500 image files, about 200 kb for each.

5. For the working thread method of the client, 

     a. Receive image data and compress it.
     b. Round-robin access the 3 VIPs for connection, 
     c. Copy the image data to an independence directory
     d. (Optional) Move data to another directory when the copy is finished.

   The performance of step c will drop when there are 2 or more clients.

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

RHGS 3.2


How reproducible:

100% reproduced 

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 24 Yaniv Kaul 2019-04-09 10:25:05 UTC
What's our status for this for 3.5?

Comment 52 errata-xmlrpc 2019-10-30 12:19:37 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/RHEA-2019:3249


Note You need to log in before you can comment on or make changes to this bug.