Hi, we are working on Performance issues, after upgrading to Kinetic, one item we noticed is Kinetic is being served on HTTP1.1 instead of HTTP2. Is this a default for Epicor? Can we change it and what may be the expected issues?
@josecgomez Sorry for putting you on the spot, what do you think about this?
HTTP2 adoption overall is sitting at about 35%.
So they are not necessarily alone or behind. Just food for thought.
Yeah,
Does that mean everyone on Kinetic is on HTTP1?
I can’t answer that.
The underlying protocol shouldn’t matter—that’s way down in the weeds. As long as both the server and client support HTTP/2, you should be fine (though I haven’t tried it myself). @JeffLeBert might have a strong opinion on this though.
That said, I very much doubt HTTP/1.1 vs HTTP/2 is the root cause of your performance issues. While the performance improvements with HTTP/2 are notable, the actual overhead difference is tiny compared to everything else the system is doing.
Think of it like trying to patch a tiny hole in a sail when the boat is already filled with water. Sure, it helps a little, but the bigger issues need to be addressed first to keep things afloat.
What version of Kinetic are you running? Knowing that might help narrow down the actual source of the problem.
What @josecgomez said. We also have to know what client you are using. WinForms (classic UI) uses older tech (.NET FW 4.8) so may be what you are seeing. For the browser UI, I think it depends on your browser. I would assume that would be more up to date.
We are on Kinetic 2023.2.21
Anything else anyone has implemented to increase performance?
Check this thread and make sure RPC compression is setup there was an issue with it in 2023
Thanks @josecgomez 