Your contention that I was rebutting (emphasis mine) was: * "whether it's better to let slow HTTP requests block things or stack up in an async context, and the contention was that it doesn't much matter either way and that the difference won't be too big,"
The difference in performance is substantial. Your indication that the performance of the two modules as near equal is incorrect. Both in theory and in practice it is the better of the two options. (You might turn back to the "if one were to create a ridiculous number of processes", but since each module gets allocated memory per process, this is not a good idea). 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: Monday, December 23, 2024 1:01 PM To: [email protected] <[email protected]> Cc: 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 23, 2024, at 1:14 pm, Ben Kaufman <[email protected]> wrote: > > • the original controversy was about whether it's better to let slow HTTP > requests block things or stack up in an async context, and the contention was > that it doesn't much matter either way and that the difference won't be too > big. > TL;DR: The difference isn't only big, it's enough to make the OP's proposed > scenario work. I didn't say 750 CPS wouldn't work, and didn't make that claim when you originally asked. The danger with committing to specific numbers is that they harken back to the era of hardware and software in which you last did peak load tests. In the case of http_async_client, for me, that was probably the mid-2010s. Whatever I could say worked or didn't work then is surely different now. My contention was that HTTP queries, even with http_async_client, are a paradigm for which Kamailio isn't especially well-suited as compared to other approaches. That is to say, the other designs recommended here would work better, if properly implemented. I don't say that http_async_client can't be made to hit the OP's specific targets, and I commend you in your efforts to show that it can. -- 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%7C072332e9b04848b4e08f08dd23858ea9%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638705778748873953%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=XKvqxpyHiMbtH%2BGAE78aXg0GooUvywYe1D3ZgTGUUII%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!
