Yes they are, maybe unix sockets too (not tcp) but yes, there’s a point.
> On Dec 19, 2024, at 12:29 PM, Ben Kaufman <[email protected]> wrote: > > Playing devil's advocate here: > > Aren't DB queries generally over TCP? Of course one should OPTIMIZE their DB > queries, but in many cases they're necessary in many cases, right? > > Kaufman > Senior Voice Engineer > > > > E: [email protected] <mailto:[email protected]> > > > > > > SIP.US Client Support: 800.566.9810 | SIPTRUNK Client Support: 800.250.6510 > | Flowroute Client Support: 855.356.9768 > <https://www.sip.us/> > <https://www.siptrunk.com/> > <https://www.flowroute.com/> > > > > From: Olle E. Johansson via sr-users <[email protected] > <mailto:[email protected]>> > Sent: Thursday, December 19, 2024 11:09 AM > To: Kamailio (SER) - Users Mailing List <[email protected] > <mailto:[email protected]>> > Cc: Alexis Fidalgo <[email protected] <mailto:[email protected]>>; Olle E. > Johansson <[email protected] <mailto:[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 19 Dec 2024, at 17:49, Alex Balashov via sr-users > > <[email protected] <mailto:[email protected]>> wrote: > > > > > > > >> On Dec 19, 2024, at 11:19 am, Alexis Fidalgo via sr-users > >> <[email protected] <mailto:[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%7Cfbc39a2815df40e07b3308dd20509ae0%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638702252797649255%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=TCmI3hcZCjF9WP4iEyrPni5N890mPORv1zb5IH%2FXrds%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 > > 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] <mailto:[email protected]> > To unsubscribe send an email to [email protected] > <mailto:[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!
