[Spce-user] [SEMS] Performance tuning, parameter USE_THREADPOOL

[Andrew Pogrebennyk]

Denys,
we have not measured the performance impact with threadpool _disabled_.
It is enabled in our SPCE builds. I think that it is not optimal to
create a new thread for every session, but probably with average cc
around 200 calls you won't notice any difference. Also we use SEMS
mainly for signaling with a few exceptions in our Sipwise appliance and
we do have better experience with threadpool stability-wise than without.

Regards,
Andrew

On 12/21/2018 05:11 PM, Denys Pozniak wrote:
> Hello!
> 
> Could you explain how parameter USE_THREADPOOL affect on performance?
> I use SEMS with sbc application with RTP relaying, average concurrent
> call is around 200.
> 
> I am about Makefile.defs:
> 
> # compile with session thread pool support?
> #      use this for very high concurrent call count
> #      applications (e.g. for signaling only)
> #      if compiled with thread pool, there will be a
> #      thread pool of configurable size processing the
> #      signaling and application logic of the calls.
> #      if compiled without thread pool support, every
> #      session will have its own thread.
> #
> #USE_THREADPOOL = yes
> 
> 
> -- 
> 
> BR,
> Denys Pozniak
> 
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>