[Bugs] [Bug 1451843] New: gluster volume performance issue

bugzilla at redhat.com bugzilla at redhat.com
Wed May 17 15:40:59 UTC 2017


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

            Bug ID: 1451843
           Summary: gluster volume performance issue
           Product: GlusterFS
           Version: 3.8
         Component: replicate
          Assignee: bugs at gluster.org
          Reporter: 3242650 at naver.com
                CC: bugs at gluster.org



Description of problem:Glaster volume performance is measured poorly.
I create the gluster volume and then mount the volume as fuse in RHEV.
If I use gluster volume at VM creation and deployment on RHEV, the time is the
very slow.
So I made measurements using FIO benchmark tool. The measurement results are as
follows.
-----------------------------------------
volume : jbod replica
fio profile : 
filesize - 30G
number of files - 36
blocksize - 4K
measured value :
read iops - 7587
write iops - 3254
-----------------------------------------
volume : jbod disperse
fio profile : 
filesize - 30G
number of files - 1
blocksize - 4K
measured value :
read iops - 2498
write iops - 1070
-----------------------------------------
local(no use gluster volume) :
fio profile : 
filesize - 30G
number of files - 1
blocksize - 4K
read iops - 42044
write iops - 18020
-----------------------------------------


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


How reproducible:Always


Steps to Reproduce:
1.Configure the gluster volume
2.Mounting as fuse gluster volume in RHEV
3.Create the vm
4.Use benchmark tool FIO to measure performance at VM or server

Actual results:
VM creationtome is later than other storage methods (SAN Storage, local NFS)


Expected results:
Same as actual result

Additional info:
Configuration environment
os : RHVH4.1
gluster version : glsuterfs 3.8.4
node : 3
disk : 6(SSD 800G) per server(except os disk)
gluster volume : replica, disperse
Switch : RDMA
Additional environment : DMCache(using VNMe)

-- 
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