So comparing the key latency, ∆ (2,3), in the two cases:
iodepth=1: 171 us
iodepth=8: 1453 us (in the ballpark of 171*8=1368). That's not good! (I
wonder if that relation roughly holds up for other values of iodepth).
This data doesn't conclusively establish that the problem is in gluster.
You'd
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-06-09-d95aa04e
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman
I have not used valgrind before, so I may be wrong here.
I think the valgrind_stack_deregister should have been after GF_FREE_STACK.
That may explain the instance of invalid_write during stack_destroy calls
in after.log.
There seems to be numerous issues reported in before.log (I am assuming,
you
