In our case we did it (a lot of backend replicas inside a k8), but still “hiding” the problem. Improves? Yes. Fixes? Not at all
> On Dec 19, 2024, at 12:09 PM, Olle E. Johansson <[email protected]> wrote: > > > >> On 19 Dec 2024, at 17:49, Alex Balashov via sr-users >> <[email protected]> wrote: >> >> >> >>> 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://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 > > Well, you can set up a cluster of background workers and use the normal > http_client. That will speed up the process to read from the network as the > network client processes are freed up by you suspending the transaction and > continuing in a background process (which you need many of). This will make > life better in some cases, but not all. > > But in high volume, I would not _depend_ on any TCP-based external process, > regardless if it’s HTTP or databases. > > /O > __________________________________________________________ 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!
