[Gluster-devel] GlusterFS v3.7.8 client leaks summary — part II
oleksandr at natalenko.name
Wed Feb 10 13:37:58 UTC 2016
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: 
statedump before drop_caches: 
slabtop before drop_caches: 
RAM usage after drop_caches: 
statedump after drop_caches: 
slabtop after drop_caches: 
Valgrind output: 
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.
More information about the Gluster-devel