Today there is allowed only ONE TCP-Connection between a Proxy and a Main Server.
This leads to the situation that whereas there may exist a VPN Connection with a bandwith of 100 MBit/sec the proxy can only use a small part of it.
Such a situation we discovered in our company where during our test the Proxy only get's 10 MBit/sec per Main Server Connection.
The limit is a result of the connection's Latency, which give this result for that location.
For other locations with varying Network Latencies the Traffic performance might be better but can also more worse.
My request (idea) is: Allow multiple TCP connections from FSA to Main server to improve throughput
The Integrity Administrator should get the possiblity to define in which way a WAN Connection can be used, especially if there are more bandwith available than the Proxy can use.
Physical Limits should not slow down the Traffic Performance.
A little bit of History as a result of a case opened at PTC Support:
In the past there have been Enhancements submitted, but they were rejected with Reason: No Change Planned.
One of these Enhancements was like it follows: Allow multiple TCP connections from FSA to Main server to improve throughput:
- Can Integrity be configured to allow more than one TCP connection between FSA and main server?
- Using only single Integrity TCP connection between FSA and main server can result in saturated TCP connection
A second Defect was requesting: Integrity FSAs experience performance degradation in environments where single TCP connections are bandwith capped.
It was rejected with Reason: No Change Planned.
A third Enhancement was : Proxy Caches should automatically detect a huge increase in latency in operations and automatically sever/re-establish the proxy->server connection.
This Enhancement was never implemented.
