[Bugs] [Bug 1349953] thread CPU saturation limiting throughput on write workloads

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1349953



--- Comment #14 from Xavier Hernandez <xhernandez at datalab.es> ---
Thanks Manoj for the testing. I was wrong. As Pranith says, writes need to be
serialized in EC causing the queued writes to be resumed inside the epoll
threads.

In this case I'm not sure why enabling client-io-threads improves performance
so much. Maybe it allows fuse to process requests faster, causing the
saturation of epoll-threads later...

In any case I think it would be interesting to move the execution of all these
operations to other threads. Maybe using a thread pool or synctasks.

Another parameter that I tweak that gives a small extra boost in my tests is
rpc.outstanding-rpc-limit. Default is 64. Using 128, 256 or 512 gives some more
performance (probably at the cost of more CPU usage)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=qmJFe1OYbq&a=cc_unsubscribe