-------- Original Message --------
Subject: Re: 120k context switches on
GlsuterFS nodes
Local Time: May 18, 2017 8:43 PM
UTC Time: May 18, 2017 6:43 PM
I have a single Intel Xeon CPU E5-2620 v3 @ 2.40GHz in each
nodes and this one has 6 cores and 12 threads. I thought this
would be enough for GlusterFS. When I check my CPU graphs
everything is pretty much idle and there is hardly any peeks
at all on the CPU. During the very high context switch my CPU
graphs shows the following:
1 thread was 100% busy in CPU user
1 thread was 100% busy in CPU system
leaving actually 10 other threads out of the total of 12
threads unused...
Is there maybe any performance tuning parameters I need to
configure in order to make a better use of my CPU cores or
threads?
-------- Original Message --------
Subject: Re: 120k context switches on
GlsuterFS nodes
Local Time: May 18, 2017 7:03 AM
UTC Time: May 18, 2017 5:03 AM
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