it seems that the file attached is not complete. callgrind_annotate does not show the call tree. Can you rerun glusterfs on valgrind and send the new callgrind output? You can check whether callgrind output is correct by using callgrind_annotate. On Fri, Jan 8, 2010 at 2:15 AM, Dave Hall <dave.hall at skwashd.com> wrote: > oops, try again > > On Thu, 2010-01-07 at 19:15 +0400, Raghavendra G wrote: > > Hi Dave, > > > > I think you forgot to add attachment :). > > > > regards, > > On Thu, Jan 7, 2010 at 10:54 AM, Dave Hall <dave.hall at skwashd.com> > > wrote: > > Hi again, > > > > > On Wed, 2010-01-06 at 14:38 +0530, Shehjar Tikoo wrote: > > > > > > > > > > You can do this by using the following command to start up > > the > > > > glusterfs client process: > > > > > > > > $ valgrind --tool=callgrind <path-to-glusterfs> -f > > > > <path-to-client-volfile> -L NONE --no-daemon > > <client-mount-point> > > > > > > Done. See attached. I must admit that I don't have much > > experience with > > valgrind. I let it run for a few hours while I did something > > else. > > When it was running the valgrind process was maxing a CPU and > > cd /path/to/mount and other operations hung. I started it > > with find > > -type f > /dev/null > > > > Cheers > > > > Dave > > > > _______________________________________________ > > Gluster-users mailing list > > Gluster-users at gluster.org > > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > > > > > > > > > > -- > > Raghavendra G > > > > > -- Raghavendra G
