[Gluster-devel] Review request - #17105

[Raghavendra G]

program/GF-DUMP: Shield ping processing from traffic to Glusterfs Program

Since poller thread bears the brunt of execution till the request is handed
over to io-threads, poller thread experiencies lock contention(s) in the
control flow till io-threads, which slows it down. This delay invariably
affects reading ping requests from network and responding to them,
resulting in increased ping latencies, which sometimes results in a
ping-timer-expiry on client leading to disconnect of transport. So, this
patch aims to free up poller thread from executing code of Glusterfs
Program.

We do this by making
* Glusterfs Program registering itself asking rpcsvc to execute its actors
in its own threads.
* GF-DUMP Program registering itself asking rpcsvc to _NOT_ execute its
actors in its own threads. Otherwise program's ownthreads become bottleneck
in processing ping traffic. This means that poller thread reads a ping
packet, invokes its actor and hands the response msg to transport queue.

Change-Id: I526268c10bdd5ef93f322a4f95385137550a6a49
<https://review.gluster.org/#/q/I526268c10bdd5ef93f322a4f95385137550a6a49>
Signed-off-by: Raghavendra G <rgowdapp at redhat.com>
BUG: 1421938 <https://bugzilla.redhat.com/show_bug.cgi?id=1421938>

Patch: https://review.gluster.org/#/c/17105/

Note that there is only one thread per program. So, am wondering whether
this thread can become performance bottleneck for Glusterfs program. Your
comments are welcome.

regards,
-- 
Raghavendra G
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20170516/8b7b0795/attachment.html>