[Gluster-users] GlusterFS v3.7.8 client leaks summary — part II

Oleksandr Natalenko oleksandr at natalenko.name
Wed Feb 10 13:37:58 UTC 2016

Hi, folks.

Here go new test results regarding client memory leak.

I use v3.7.8 with the following patches:

Soumya Koduri (2):
       inode: Retire the inodes from the lru list in inode_table_destroy
       gfapi: Use inode_forget in case of handle objects

Those are the only 2 not merged yet.

So far, I've performed only "find" test, and here are the results:

RAM usage before drop_caches: [1]
statedump before drop_caches: [2]
slabtop before drop_caches: [3]
RAM usage after drop_caches: [4]
statedump after drop_caches: [5]
slabtop after drop_caches: [6]
Valgrind output: [7]

No leaks either via statedump or via valgrind. However, statedump stats 
still suffer from integer overflow.

Next steps I'm going to take:

1) "rsync" test;
2) API test.

[1] https://gist.github.com/88d2fa95c28baeb2543f
[2] https://gist.github.com/4f3e93ff2db6e3cf4081
[3] https://gist.github.com/62791a2c4258041ba821
[4] https://gist.github.com/1d3ce95a493d054bbac2
[5] https://gist.github.com/fa855a2752d3691365a7
[6] https://gist.github.com/84e9e27d2a2e5ff5dc33
[7] https://gist.github.com/f35bd32a5159d3571d3a

More information about the Gluster-users mailing list