Thanks Alex and Kaufman,
As you said there is an element of db blocking for accounting, but I don't see the same impact when the INVITE goes through and sets the accounting flags.
I will look to disable accounting and see if it improves things. If not, I will have a look at benchmark to try and pin it down. It is not causing any noticeable delay in the clearing down of the call to the end users but I want to try and optimise the cleardown if possible.
Once I have tested this I will report back. Thanks for your assistance.
Lewis
You’re very welcome!
It may be that the DB operation for BYEs is different in nature and more latent than for INVITEs, as odd as that would seem.
If the inherent latency of the operation is unavoidable as a matter of technical design or insurmountable realities of server performance or whatever, there are various ways to make such operations asynchronous — that is, to send them to be performed by a separate pool of worker processes unrelated to the main SIP message worker processes.
— Alex
On Aug 26, 2022, at 10:20 AM, Lewis Hutchinson lewis.hutchinson@missionlabs.co.uk wrote:
Thanks Alex and Kaufman,
As you said there is an element of db blocking for accounting, but I don't see the same impact when the INVITE goes through and sets the accounting flags.
I will look to disable accounting and see if it improves things. If not, I will have a look at benchmark to try and pin it down. It is not causing any noticeable delay in the clearing down of the call to the end users but I want to try and optimise the cleardown if possible.
Once I have tested this I will report back. Thanks for your assistance.
Lewis
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Hello,
if the delay comes on some internal callback that is not due to a config function/action, the benchmark may not be much useful, but if it is about database, look at the core cookbook, there are latency related parameters for db operations and config actions, they might be more suitable to enable here than benchmark module.
Cheers, Daniel
On 26.08.22 16:20, Lewis Hutchinson wrote:
Thanks Alex and Kaufman,
As you said there is an element of db blocking for accounting, but I don't see the same impact when the INVITE goes through and sets the accounting flags.
I will look to disable accounting and see if it improves things. If not, I will have a look at benchmark to try and pin it down. It is not causing any noticeable delay in the clearing down of the call to the end users but I want to try and optimise the cleardown if possible.
Once I have tested this I will report back. Thanks for your assistance.
Lewis
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
-
Alex Balashov -
Daniel-Constantin Mierla -
Lewis Hutchinson