[Gluster-users] maxing out cpu

Dave Hall dave.hall at skwashd.com
Thu Jan 7 14:15:47 PST 2010


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
> 




More information about the Gluster-users mailing list