You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current setup one proxy instance handles all incoming traffic type (TCP, HTTP, WebSocket). Thus a problem in of one those types (e.g. someone creating very many HTTP connections as seen recently) will affect all traffic types equally. Having separate instances for HTTP will limit the blast radius to HTTP only.
The effect will be depending on how much traffic is specific to HTTP in the region relative to the other traffic types.
We would create as many proxy instances dedicated to HTTP traffic as there are now, effectively duplicating the number of instances.
Another side effect is that we can better observe which of the traffic types consumes how much memory.
The text was updated successfully, but these errors were encountered:
In the current setup one proxy instance handles all incoming traffic type (TCP, HTTP, WebSocket). Thus a problem in of one those types (e.g. someone creating very many HTTP connections as seen recently) will affect all traffic types equally. Having separate instances for HTTP will limit the blast radius to HTTP only.
The effect will be depending on how much traffic is specific to HTTP in the region relative to the other traffic types.
We would create as many proxy instances dedicated to HTTP traffic as there are now, effectively duplicating the number of instances.
Another side effect is that we can better observe which of the traffic types consumes how much memory.
The text was updated successfully, but these errors were encountered: