10 Mar
2009
10 Mar
'09
1:52 p.m.
On Tuesday 10 March 2009, Andrei Pelinescu-Onciul wrote:
On Mar 09, 2009 at 22:14, Ovidiu Sas
<osas(a)voipembedded.com> wrote:
Hi Andrei,
we used also the extra process timers, because the old k timers were not
really performant under high load conditions. But if you say the ones from
SER behave better in this regards they should be sufficient for our task, as
we only needed them for some internal modules.
Cheers,
Henning
Should I understand that in ser there are two
timer processes:
- fast timer
- slow timer
If this is correct, I would like to have the ability to register an
extra process for particular timer.
On a multicore platform, several timers can be processed in parallel.
Under heavy load, I experienced issues while using the standard timer
process for the ratelimit module and therefore I registered the
ratelimit timer with it's own process.
Could you describe what is the ratelimit timer doing and how
often is it called?
(there are huge differences between the timer in k and sr, the timer in
k is very inefficient and that's what you might have seen).