On Dec 19, 2024, at 5:32 pm, Alexis Fidalgo alzrck@gmail.com wrote:
Certainly ill test the http/2 in the near future and run tests at least on my lab (luckily I have all the tests I run over and over again trying to improve my current scenario) will be helpful to compare.
It should help a lot. The basic reason why HTTP is terrible is that it has to initiate a new connection every time, although a close secondary reason is that the backend services responding to HTTP requests don't tend to be very performant (e.g. Node), since they're not built for the demands of telephony, nor with a view to honouring timing interoperability with a circuit-switched world. Still, addressing the first one should help a lot.
-- Alex