[Gluster-devel] Profiling GlusterFS FUSE client with Valgrind's Massif tool

[Oleksandr Natalenko]

Hello.

While dancing around huge memory consumption by FUSE client [1], I was 
suggested by Pranith to use Massif tool to find out the reason of the 
leak.

Unfortunately, it does not work for me properly, and I believe I do 
something wrong.

Instead of generating report after unmounting volume or sigterming 
glusterfs process, Valgrind generates 2 reports (for 2 PIDs) just right 
after launch, and does not update them further, even on exit. I believe, 
that is because something is going on with forking, but I cannot figure 
out, what's going wrong.

The command I use to launch GlusterFS via Valgrind+Massif:

===
valgrind --tool=massif --trace-children=yes /usr/sbin/glusterfs -N 
--volfile-server=server.example.com --volfile-id=test 
/mnt/net/glusterfs/test
===

Any ideas or sample usecases for Massif+GlusterFS?

Thanks.

Regards,
   Oleksandr

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1369364