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

[bugzilla at redhat.com]

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

Xavi Hernandez <jahernan at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jahernan at redhat.com



--- Comment #12 from Xavi Hernandez <jahernan at redhat.com> ---
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.

One way to test if this is really the case would be to repeat the same test you
did in comment #3 but before untaring to another directory, remove all previous
data. This should release a lot of cached data that should be reused by the
next untar, keeping memory usage (almost) constant.

For example:

mkdir /gluster/dir1
tar -C /gluster/dir1 -xf linux.tgz
# check memory usage
rm -rf /gluster/dir1 # or dropping caches
mkdir /gluster/dir2
tar -C /gluster/dir2 -xf linux.tgz
# check memory usage

There shouldn't be a significant increase in memory usage after the second
untar.

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