[Bugs] [Bug 1365463] New: [Perf] : Poor metadata performance on Ganesha v4 mounts

bugzilla at redhat.com bugzilla at redhat.com
Tue Aug 9 10:50:30 UTC 2016


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

            Bug ID: 1365463
           Summary: [Perf] : Poor metadata performance on Ganesha v4
                    mounts
           Product: GlusterFS
           Version: 3.8.1
         Component: ganesha-nfs
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: asoman at redhat.com
                CC: bugs at gluster.org



Description of problem:
-----------------------

Metadata performance on Ganesha v4 mounts is  poor when compared to GlusterNFS
:

*On Ganesha v4 mounts* :

stat : 959 files/sec
chmod : 820 files/sec
setxattr : 1318 files/sec
getxattr : 334 files/sec

*On Gluster NFS* :

stat : 1596 files/sec
chmod : 1477 files/sec
setxattr : 1750 files/sec
getxattr : 1535 files/sec


Both these results are with "Smallfile Perf enhancements" -
cluster.lookup-optimize is on and server.event-threads and client.event-threads
are 4 each.

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

glusterfs-server-3.8.1-0.4.git56fcf39.el7rhgs.x86_64
nfs-ganesha-gluster-2.4-0.dev.26.el7rhgs.x86_64
pacemaker-libs-1.1.13-10.el7.x86_64
pcs-0.9.143-15.el7.x86_64


How reproducible:
-----------------

100%

Steps to Reproduce:
------------------
My setup consists of 4 servers and 4 clients.Each client mounts from 1 server.

Run smallfile workload in a distributed-multithreaded way on  Ganehsa v4 and
Gluster NFS mounts :

python /small-files/smallfile/smallfile_cli.py --operation stat --threads 8 
--file-size 64 --files 10000 --top /gluster-mount --host-set "`echo $CLIENT |
tr ' ' ','`"

python /small-files/smallfile/smallfile_cli.py --operation chmod --threads 8 
--file-size 64 --files 10000 --top /gluster-mount --host-set "`echo $CLIENT |
tr ' ' ','`"

etc

Actual results:
--------------

Metadata perf is comparitively poor.

Expected results:
-----------------

Additional info:
----------------

Volume Name: testvol
Type: Distributed-Replicate
Volume ID: 3ee2c046-939b-4915-908b-859bfcad0840
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: gqas001.sbu.lab.eng.bos.redhat.com:/bricks/testvol_brick0
Brick2: gqas014.sbu.lab.eng.bos.redhat.com:/bricks/testvol_brick1
Brick3: gqas015.sbu.lab.eng.bos.redhat.com:/bricks/testvol_brick2
Brick4: gqas016.sbu.lab.eng.bos.redhat.com:/bricks/testvol_brick3
Options Reconfigured:
client.event-threads: 4
server.event-threads: 4
cluster.lookup-optimize: on
ganesha.enable: on
features.cache-invalidation: on
nfs.disable: on
performance.readdir-ahead: on
performance.stat-prefetch: off
server.allow-insecure: on
nfs-ganesha: enable
cluster.enable-shared-storage: enable

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list