[Bugs] [Bug 1558379] Huge memory usage of FUSE client

[bugzilla at redhat.com]

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



--- Comment #13 from Yannick Perret <yannick.perret at liris.cnrs.fr> ---
(In reply to Xavi Hernandez from comment #12)
> The malloc implementation in glibc (the one gluster uses) does return the
> memory to the system only if the released memory belongs to the top of the
> heap. This means that a single allocation on the top of the heap prevents
> all other released memory from being returned to the system.
> 
> Anyway, the memory is still free from the point of view of the application,
> so it can be reused when more memory is requested.
> 
I understand this. And, so far, it seems to be confirmed by the fact that I
need to perform *new additional* operations to make memory increased.

But when I remove all files from the FS − I still performed several 'rm -rf
MNT/*' − top of heap (which should have hold stuff about last files operations)
should be free, and this memory should returns to the system.
This is not the case so far: after a total cleanup of FS content the glusterfs
process stay at the same memory value.

In the context of few operations on the FS this is clearly not a problem.
Neither for temporary mounts (i.e. some of our backups that are automounted).
But at my office some of the volumes are users HOME, with about +300 people.
They are mounted using NFS export (so without a real failover).
Currently by just dealing with ~20 different subdirectories today (with various
archives) I reached VSZ/RSS of 1216364/754568, 
How high would it grows if I use it on a +300 directories activity on a
permanent mount?

Regards,
--
Y.

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