[SR-Users] EVAPI workload allocation across processes
hw at gilawa.com
Tue Jan 11 16:09:38 CET 2022
not the author of this module - but I think you are right after having briefly looked to the code. The dispatcher process accept(..) the connections and then pass them to the worker processes for further processing.
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
From: sr-users <sr-users-bounces at lists.kamailio.org> On Behalf Of Alex Balashov
Sent: Sunday, January 2, 2022 3:54 AM
To: Kamailio (SER) - Users Mailing List <sr-users at lists.kamailio.org>
Subject: [SR-Users] EVAPI workload allocation across processes
Given several EVAPI worker processes:
modparam("evapi", "workers", 4)
# kamcmd -s /run/kamailio/kamailio_ctl ps | fgrep -i evapi
539257 EvAPI Dispatcher
539258 EvAPI Worker
539259 EvAPI Worker
539260 EvAPI Worker
539261 EvAPI Worker
How should one understand the way that the EVAPI workload is allocated among them?
My best guess is that the EvAPI dispatcher process is the sole accept()or of client connections and the place where all relaying to client connections is done, regardless of their number, and that the ‘workers’ represent an async pool of processes in which TM transactions can be resumed or other work can be done when an outside caller sends a message to the dispatcher.
However, the documentation is a little vague on the meaning of the ‘workers’ modparam:
"Number of worker processes to be started to handle incoming messages from remote applications.”
Or maybe it’s not. Just wanted to confirm that my understanding is correct.
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users at lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
More information about the sr-users