On 10/15/2018 9:16 PM, Jerry Malcolm wrote:
I have several webapps that do a significant amount of recursive loads
of snippits of HTML utilizing XHR/http/ajax requests. These apps are
all debugged and in production. The server has no problem whatsoever
in keeping up with the multiple concurrent requests. However, the
open-connection limits on the browsers that block more than 6
concurrent connections to a server is killing me in performance.
I know pretty much nothing about the things you asked about after this
paragraph. But I do know about one thing that might help you --
HTTP/2. It can execute many HTTP requests simultaneously over a single
TCP connection.
Here's a demo:
https://http2.akamai.com/demo
I really have no idea how to enable HTTP/2 in Tomcat, but I know that it
can be done if you have a new enough version. Browsers with HTTP/2
support should automatically multiplex requests to the same server over
fewer connections.
Another possibility is to put your web services behind a load balancer
that supports HTTP/2 on the front end. Haproxy is one that I am aware
of with that support.
HTTP/2 promises to obsolete many of the development and software tricks
used in the past for improving web performance. Designing applications
for performance has typically involved combining code into fewer files
instead of aspiring to a highly modular application. With HTTP/2, you
can split things up without killing performance.
If anything I have said above is wrong, I would appreciate the community
informing me about my errors.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
