[sr-dev] [kamailio/kamailio] Kamailio dispatcher module reports incorrect values with Call-Load based dispatching algorithm(No.10) (#2322)

Julien Chavanton jchavanton at gmail.com
Wed May 13 07:45:51 CEST 2020


I have little experience using this algorithm, I noticed looking at the
dispatcher latency stats there was some timeouts, not sure about  config
but I wonder it went Inactive probing at some point and came back.
It may be worth consider looking at something that could go wrong when it
goes active, inactive, active in such scenario.
Or reload the dispatcher before your test to have clean stats just to be
sure.

On Tue, May 12, 2020 at 10:14 PM hbilling <notifications at github.com> wrote:

> Thanks Daniel,
> I will await your response on the issue then, regarding using the lock or
> atomic integers. I presume the atomic integer usage must be faster than the
> locking approach.
> FWIW, a similar locking is being used in 'dp_init_relative_weights()' and
> 'ds_update_latency' APIs in dispatch.c also.
>
>> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/kamailio/kamailio/issues/2322#issuecomment-627750313>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABO7UZINCF24E6BMTEAK5HLRRIT7ZANCNFSM4M5V5VYA>
> .
> _______________________________________________
> Kamailio (SER) - Development Mailing List
> sr-dev at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20200512/c462d53b/attachment-0003.html>


More information about the sr-dev mailing list