On the other hand, tracking that stat between versions with a known test sequence may be valuable for watching for performance issues or improvements.
On May 17, 2017 10:03:28 PM PDT, Ravishankar N <ravishankar@xxxxxxxxxx> wrote:
On 05/17/2017 11:07 PM, Pranith Kumar
Karampuri wrote:
+ gluster-devel
Okay, that could be due to the syscalls themselves or pre-emptive
multitasking in case there aren't enough cpu cores. I think the
spike in numbers is due to more users accessing the files at the
same time like you observed, translating into more syscalls. You
can try capturing the gluster volume profile info the next time it
occurs and co-relate with the cs count. If you don't see any
negative performance impact, I think you don't need to be bothered
much by the numbers.
HTH,
Ravi
--
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel