Ganesha should be usually I/O bound rather than CPU bound. If it is
running with things from RAM only, then mutex contention might be
putting ganesha threads to sleep??? Another thing is network, you can
only push so much.
Regards, Malahal.
Swen Schillig [s...@vnet.ibm.com] wrote:
> Does anybody
On 02/23/2016 09:14 AM, Swen Schillig wrote:
> Does anybody know of some build-in limitation/configuration
> which would explain why the ganesha process
> is not going beyond 800% CPU usage ?
>
> Thanks
> Swen
Maybe not enough clients / parallel accesses? The default number of
workers is 16, whi
Does anybody know of some build-in limitation/configuration
which would explain why the ganesha process
is not going beyond 800% CPU usage ?
Thanks
Swen
--
Site24x7 APM Insight: Get Deep Visibility into Application Perf
