19 Dec
2024
19 Dec
'24
4:55 p.m.
Hi all!
Well, i wasn't expecting to generate such debate on this matter! :)
Thanks to all for the provided feedback.
The async_http_client seems an interesting test to do, even though it
doesn't solve the issue, "per se".
I will try that tomorrow, 1st thing in the morning.
@Ben Kaufman <bkaufman(a)bcmone.com> The math exercise you explained
makes sense. I was already doing some math and very close to the same
results! Thanks mate!
Atenciosamente / Kind Regards / Cordialement / Un saludo,
*Sérgio Charrua*
On Thu, Dec 19, 2024 at 8:11 PM Henning Westerholt via sr-users <
sr-users(a)lists.kamailio.org> wrote:
Hello,
according to this discussion:
https://kamailio.org/mailman3/hyperkitty/list/sr-users@lists.kamailio.org/t…
and the linked PR in it, HTTP/2 should be available. Its probably
something to tested, as certain features (e.g. HTTP/2 multiplexing) are
deactivated in the http_async_client for example.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
-----Original Message-----
From: Alex Balashov via sr-users <sr-users(a)lists.kamailio.org>
Sent: Donnerstag, 19. Dezember 2024 20:16
To: sr-users(a)lists.kamailio.org
Cc: Alex Balashov <abalashov(a)evaristesys.com>
Subject: [SR-Users] Re: Kamailio not receiving packets on high CPS
BTW: Not sure what the state of HTTP/2 support is in http_async_client.
If existent, and the server is HTTP/2, you can make multiple sequential
and
parallel requests over the same connection. Given
Kamailio's concurrency
and
isolation model, this would probably mean
sequential requests over
multiple
persistent connections attached to each process.
While HTTP backends are still characteristically sluggish from the
perspective of
the tight timing tolerances of traditional
real-time communications,
this would
be a real game-changer and probably vacate much
of what I'm saying, and
the
basis of my opposition to HTTP as an integration
path out of Kamailio.
HTTP/1.1 is for these kinds of systems, though. If high throughput is
your
goal, I'd go a different route. Whatever you
do to squeeze a few hundred
requests/sec out of it will most likely amount to a Pyrrhic victory.
-- Alex
redirect
On Dec 19, 2024, at 2:06 pm, Alex Balashov
<abalashov(a)evaristesys.com>
wrote:
> On Dec 19, 2024, at 1:54 pm, Ben Kaufman <bkaufman(a)bcmone.com>
wrote:
>>
>> Alex,
>>
>> I read the OP's requirements like this. They want to implement a server that will:
>> • Receive a SIP INVITE
>> • Make a single http request that has a RTT of 200ms
>> • Copy a header from the HTTP reply to a SIP 300 reply
>> • Handle the ACK for the reply
>>
>> Is it your opinion this cannot be implemented reliably with Kamailio
on
a
4vCPUs and 4GB RAM host at a rate of 750 INVITE
requests per second?
>
> I have no idea. That's an empirical question. In my experience, that's
an
ambitious ask given the stochastic variation in
HTTP API response time
(i.e. it's
not exactly and literally 200 ms), but it's
probably possible with enough
processes.
at
My only argument--from first principles-- is that you'll get a lot more
throughput if you ditch HTTP, and I joined the conversation at the point which Alexis Fidalgo expressed that async
isn't a cure-all. I wanted to
sign onto
this sentiment.
the
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- sr-
users(a)lists.kamailio.org
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to sender!
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions --
sr-users(a)lists.kamailio.org
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to
the sender!