Hi, We have been able to reproduce the OOM killer error consistently. NFS Ganesha memory consumption goes as high as 85-90 gigs (>60% of total memory). The test case is very simple, just keep creating files (with dd, bs=64k count=1).
The setup has 1 NFS Ganesha server and 8 clients which are continuously firing dds. After about 1M files, the memory reaches to 85 gigs. Which is like every inode consuming 85k of memory. I see that there are already a couple of issues opened on glusterfs, https://bugzilla.redhat.com/show_bug.cgi?id=1240172 https://bugzilla.redhat.com/show_bug.cgi?id=1337867 Is this a known issue for nfs-ganesha? Can we work around this problem with some inode cache configuration (cache size, entries hw, cache fds, etc)? Thanks, Sriram ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
