Alex,

In this case, the "moving food around on the plate" is moving the process 
blocking of the http request (which is just wait time) to increased memory 
usage by storing the request in memory.  The number of message able to be 
handled over a sustained period increases (full stop).   Of course there' still 
an upper bound based on memory and that should be considered.  It's not a 
"limitless fix", but buy creating a queue for the requests in memory the upper 
bound gets increased.




Kaufman
Senior Voice Engineer



E: [email protected]







SIP.US Client Support: 800.566.9810  |  SIPTRUNK Client Support: 800.250.6510  
|  Flowroute Client Support: 855.356.9768

[img]<https://www.sip.us/>
[img]<https://www.siptrunk.com/>
[img]<https://www.flowroute.com/>


________________________________
From: Alex Balashov via sr-users <[email protected]>
Sent: Thursday, December 19, 2024 10:49 AM
To: Kamailio (SER) - Users Mailing List <[email protected]>
Cc: Alexis Fidalgo <[email protected]>; Alex Balashov <[email protected]>
Subject: [SR-Users] Re: Kamailio not receiving packets on high CPS

CAUTION: This email originated from outside the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.


> On Dec 19, 2024, at 11:19 am, Alexis Fidalgo via sr-users 
> <[email protected]> wrote:
>
> Been there, done that :) async does not help in this scenario.
>
> Killer here, as you mentioned, is wait, async moves the problem to the side 
> only (learned by testing)
>
> :)

YES! You've just summarised the central thesis about async that I made in this 
blog post:

https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblog.evaristesys.com%2F2016%2F02%2F15%2Ftuning-kamailio-for-high-throughput-and-performance%2F&data=05%7C02%7Cbkaufman%40bcmone.com%7C0884262f911d4db3a87208dd204dc539%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638702240603473955%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=m0E3h%2FC7TebqkLxqxa73yVAy9RV2hu5dQIyDVGnTzHM%3D&reserved=0<https://blog.evaristesys.com/2016/02/15/tuning-kamailio-for-high-throughput-and-performance/>

TL;DR don't do HTTP queries from Kamailio. Just don't.

-- Alex

--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: 
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fevaristesys.com%2F&data=05%7C02%7Cbkaufman%40bcmone.com%7C0884262f911d4db3a87208dd204dc539%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638702240603493009%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2BSzYyh%2F%2FVBctW%2FUXGhA%2FFyPfFFgE4YOviKd4rAEYrgo%3D&reserved=0<https://evaristesys.com/>
Tel: +1-706-510-6800

__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- 
[email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- 
[email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the 
sender!

Reply via email to