[Gluster-users] NFS performance degradation in 3.3
samu60 at gmail.com
Wed Jul 18 16:44:45 UTC 2012
We're experiencing with a 4 nodes distributed-replicated environment
(replica 2). We were using gluster native client to access the volumes, but
we were asked to add NFS accessibility to the volume. We then started the
NFS daemon on the bricks. Everything went ok but we started experiencing
some performance degradation accessing the volume.
We debugged the problem and found out that quite often the NFS glusterfs
process (NOT the glusterfsd) eats up all the CPU and the server where the
NFS is being exported starts offering really bad performance.
Is there any issue with 3.3 and NFS performance? Are there any NFS
parameters to play with that can mitigate this degradation (standard R/W
values drops to a quarter of standard values)?
Thanks in advance for any help,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-users