[Bugs] [Bug 1319045] memory increase of glusterfsd

[bugzilla at redhat.com]

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

Pranith Kumar K <pkarampu at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



--- Comment #11 from Pranith Kumar K <pkarampu at redhat.com> ---
Evangelos, Olia,
  I went through the statedumps you provided briefly. So when we create all the
directory hierarchies, the inode-table is populated with all the
inodes/dentries that are created afresh (There is an lru-limit of 16834, so as
and when these inodes are forgotten we keep reclaiming the memory after the
limit):

pool-name=log-server:inode_t
hot-count=16383
cold-count=1
padded_sizeof=156
alloc-count=170764724
max-alloc=16384
pool-misses=36330120
cur-stdalloc=68509
max-stdalloc=68793

Once the directory hierarchy is deleted, the number of inodes come down:
pool-name=log-server:inode_t
hot-count=6
cold-count=16378
padded_sizeof=156
alloc-count=179709943
max-alloc=16384
pool-misses=39154019
cur-stdalloc=1
max-stdalloc=68793

As per statedump, it released the memory :-/. Wonder why it is not showing that
the memory is now reduced in RSS

Link below gives details about how to interpret statedump file, especially in
this case memory pools:
https://github.com/gluster/glusterfs/blob/master/doc/debugging/statedump.md#mempools

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=BBAN91nD9G&a=cc_unsubscribe