Re: [sr-dev] [kamailio/kamailio] After commit ce8d36f latency_limit_db requires us instead of ms (#1956)

That commit was done as a fix, because the previous solution didn't work in most of the cases. It relied on the internal track of time, but in case of blocking, the signal to update the value didn't happen, so my tests with latency for action (which used the same mechanism as for db) was most of the time 0, even I explicitly used sleep(few seconds). The unit ms -- not sure if previously was still expected to be micro-seconds or mili-seconds. The origin was somehow related to benchmark module which has micro-seconds accuracy (or nano-seconds if compiled with librt), but to make the measurements internally, not in config file, so I had in mind micro-seconds. If people consider it to be something breaking what they expected or they were used to (but again, it was not actually working), we can think of some option to add for time unit. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1956#issuecomment-493582670