[SR-Users] evapi_async_relay() and workers

Daniel-Constantin Mierla miconda at gmail.com
Wed Sep 14 14:32:42 CEST 2022


I think there are two types of processes: "evapi dispatcher" (1 process
always) and "evapi worker" (can be many controlled by workers mod param)
and the resume of the transaction should happen in the later. The former
gets the data from sip workers and writes to evapi tcp connections, then
reads data from them (i/o event loop) and pushes to evapi workers. (iirc
:-) )


On 14.09.22 13:58, Alex Balashov wrote:
> Hi,
> When a transaction suspended by evapi_async_relay() is resumed, in which child processes is it resumed? Is it in the dedicated “EVAPI RELAY” workers defined by the ‘workers’ modparam to ‘evapi’?
> If this is so, just trying to work out the concurrency implications and the optimal size for the worker pool for maximal throughput. It sounds, at first glance, like it should be roughly similar to the sizing considerations for listener children. Thoughts welcome!
> Cheers,
> — Alex
> -- 
> 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:
>   * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda

More information about the sr-users mailing list