Hi,
Similar issue was reported in nfs-ganesha github [1]. As mentioned in
the link, there is upcall thread (actively polling in a loop) spawned
for every export which might be consuming the CPU. There are few
optimizations needed here -
* Make this behavior optional by checking existing 'clu
(I don't have the message ID of the original so this will be a new thread.)
Original Message:
https://www.gluster.org/pipermail/gluster-users.old/2016-October/028892.html
I too am seeing ~10% CPU usage per Gluster export when using Ganesha
NFS. This occurs straight after the process starts and t
Hi,
I'm using Ganesha NFS in a LXC container and using Gluster FSAL as backend.
When I define a single export in ganesha, the CPU usage is 10%
constantly on core i5 (without or without client mounting and using the
server).
When I define 8 exports, the CPU usage is constantly at 45% for the
