Dear Gluster developers,
This is Hyunseung Park at Gluesys, South Korea.
We are trying to replicate the test in https://github.com/gluster/glusterfs/issues/2771 but to no avail.
In our experiments, Gluster version 10 unfortunately did not perform noticably better than version 9.
The result above is from the test that deployed 32 threads on each of the 4 clients.
Some results were better than others, but it is not good enough when compared to the result in the aforementioned link.
We are wondering what we can do to get the full potential of the new version.
We have been running tests with varying file sizes, number of threads, different volume topology, etc. but we were not able to see data conclusive enough.
We were also not able to find meaningful output from running tests using other benchmark tools such as bonnie++ and FIO.
To find the potential cause we tried to look into the program by calling malloc_stats() and using perf.
However, we also could not find something noteworthy from the result.
Here is the data recorded during one set of smallfile test (from create to cleanup): https://drive.google.com/drive/folders/1NMXNjgOZ7svDd4-YvKCU4UAp43tm15dC?usp=sharing
Below is our test environment:
Basic HW info: VM (vSphere), 2 core CPU, 4G RAM. 4 servers and 4 clients.
OS: Centos 7
kernel version: 3.10.0-1160
Gluster version: built from git, checked out from branch 'release-9' and 'release-10' respectively (commits 7094da and a804f8)
build option: default setting except "./configure --disable-linux-io_uring" (kernel does not support io_uring)
Configuration result (case of version 10):
GlusterFS configure summary
===========================
FUSE client : yes
epoll IO multiplex : yes
fusermount : yes
readline : no
georeplication : yes
Linux-AIO : yes
Linux io_uring : no
Use liburing : no
Enable Debug : no
Run with Valgrind : no
Sanitizer enabled : none
XML output : yes
Unit Tests : no
Track priv ports : yes
POSIX ACLs : yes
SELinux features : yes
firewalld-config : no
Events : yes
EC dynamic support : x64 sse avx
Use memory pools : no
Nanosecond m/atimes : yes
Server components : yes
Legacy gNFS server : no
IPV6 default : no
Use TIRPC : yes
With Python : 3.6
Cloudsync : yes
Metadata dispersal : no
Link with TCMALLOC : yes
Enable Brick Mux : no
Building with LTO : no
------- Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
