Github user shinrich commented on the issue:
https://github.com/apache/trafficserver/pull/761
One benefit of the existing throttle approach is that there is a single
limit for both inbound and outbound connections. This allows you to create a
last ditch limit if the number of connections on the current box is overrunning
resources. It can be difficult to compute the max inbound and max outbound
constrained enough to protect the box from resource exhaustion without
overlimiting. That is, I may know that the box has enough memory to support
20K connections, but I don't know if that is 10K inbound and 10K outbound or
15K inbound and 5K outbound.
I think the LRU logic still works to some degree with HTTP/2. I did a bit
of testing there.
Moving forward with the LRU logic, we might want to look at eliminating
some connections from the LRU as well (at least from the closing active
connection phase).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
