On 01/02/2016 10:11 PM, Raghavendra Talur wrote:
On Jan 2, 2016 8:18 PM, "Atin Mukherjee" > wrote:
>
> -Atin
> Sent from one plus one
> On Jan 2, 2016 4:41 PM, "Raghavendra Talur" >
hi,
I have been thinking of coming up with a utility similar to strace
for gluster. I am sending this mail to find out if anyone else is also
thinking about it and how they are solving this problem to see if we can
come up with a concrete solution that we can implement.
These are my
- Original Message -
> From: "Emmanuel Dreyfus"
> To: "Raghavendra Gowdappa"
> Cc: "Raghavendra Talur" , "Gluster Devel"
>
> Sent: Thursday, December 31, 2015 6:32:22 PM
> Subject: Re: [Gluster-devel]
On 01/04/2016 11:04 AM, Prashanth Pai wrote:
Hi,
FYI, ltrace is very helpful for libgfapi clients.
[root@hummingbird gfapi]# ltrace -c -ff -p 28906
^C% time seconds usecs/call calls function
-- --- --- -
43.275.952481
Hi,
FYI, ltrace is very helpful for libgfapi clients.
[root@hummingbird gfapi]# ltrace -c -ff -p 28906
^C% time seconds usecs/call calls function
-- --- --- -
43.275.952481 59524 100 glfs_rename
21.392.942866
On 01/04/2016 11:16 AM, Pranith Kumar Karampuri wrote:
Nice, I didn't know about this. What I am looking for with this tool
is even more granularity. i.e. per xlator information. It shouldn't be
so difficult to find information like time spent in each xlator. What
fop from fuse lead to what
Giving one more try in the new year :)
http://review.gluster.org/#/c/12709/
http://review.gluster.org/#/c/12963/
http://review.gluster.org/#/c/13002/
Happy New year 2016!
Thanks,
-Prasanna
- Original Message -
> On Wednesday, December 23, 2015 10:07:53 PM, Atin Mukherjee wrote:
> >
Another Valgrind run.
I did the following:
===
valgrind --leak-check=full --show-leak-kinds=all --log-
file="valgrind_fuse.log" /usr/bin/glusterfs -N --volfile-
server=some.server.com --volfile-id=somevolume /mnt/volume
===
then cd to /mnt/volume and find . -type f. After traversing some part
On 01/03/2016 09:23 AM, Oleksandr Natalenko wrote:
Another Valgrind run.
I did the following:
===
valgrind --leak-check=full --show-leak-kinds=all --log-
file="valgrind_fuse.log" /usr/bin/glusterfs -N --volfile-
server=some.server.com --volfile-id=somevolume /mnt/volume
===
then cd to
Here is another Valgrind log of similar scenario but with drop_caches before
umount:
https://gist.github.com/06997ecc8c7bce83aec1
Also, I've tried to drop caches on production VM with GluserFS volume mounted
and memleaking for several weeks with absolutely no effect:
===
root 945 0.1
10 matches
Mail list logo