Hey Alex,
thanks for your prompt insights! This info will have saved me quite some
mistakes ;)
thx!
2014-10-26 20:28 GMT+01:00 Alex Balashov :
> If you want to rate-limit traffic below the throughout thresholds of the
> children, look at the pipelimit module. It would obviate the need for
> man
If you want to rate-limit traffic below the throughout thresholds of the
children, look at the pipelimit module. It would obviate the need for manual
htable statekeeping.
On 26 October 2014 15:23:27 GMT-04:00, Alex Balashov
wrote:
>Workers process SIP messages, which means both requests and
Workers process SIP messages, which means both requests and replies. So, you
can't use request-oriented tracking to make that decision.
The answers to your question are basically:
1. Keep your call processing as fast and light as possible.
2. Use async methods.
Async methods only help so mu
Gents,
assuming we don't use async methods (I know, it's against fashion),
eventually you'll end up in having some bottlenecks in your config...
Now thanks to a lot of children you can easily work around this, a maximum
of 32 children gives you already quite something, and if you use the
dispatch
