One possible reason for this issue is the TCP Window Size. The Cacheflow negotiates the TCP Window Size during the initial TCP handshake and retains that window size throughout the session. It is found that some client and environment is capable of increasing the TCP Window Size 'on the fly' during transmission which would allow for more bytes in flight. This capability in now supported in Cacheflow version 22.214.171.124 onwards in the 3.2 branch and also 126.96.36.199 onwards in the 3.4 branch.
With the addition of "Adaptive Window Sizing Support", the TCP send and receive socket buffers will start with a small buffer and quickly grow in parallel with the TCP congestion window to match network conditions. Buffer sizes grow as needed to allow the congestion window to reach the optimal size given by the product of bandwidth and round-trip time (RTT). The “tcp-ip window-size” setting is no longer used, and any previous settings will have no effect on either the starting window size or the maximum window size achieved during the lifetime of the connection.
If you are using a version prior to the 188.8.131.52 or 3.4, a potential workaround is to manually increase the TCP Window Size to 128K or 256K as outlined below. The recommendation however is to upgrade to a version in which adaptive window sizing is supported
To manually increase the initial window size to 256K:
#(config)tcp-ip window-size 256000 ok
To revert the initial window size back to default:
#(config)tcp-ip window-size 65535 ok
Imported Document ID: 000027464
Subscribing will provide email updates when this Article is updated. Login is required.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
Subscribed to the Article.
Unable to subscribe
Thanks for your additional feedback !!!
Enterprise Support Virtual Agent
Rate Me :
Tell us more:
Welcome! My name is Sami, the Enterprise Support Virtual Agent answering technical support questions.