Compression is enabled on a lab Virtual Service, but initial tests are not indicating that the traffic is being compressed. What is the most likely reason for this issue?
Avi HTTP compression behavior is influenced by network latency and compression policy settings. Broadcom's Avi documentation explains that when round-trip time is less than 10 ms, no compression is applied; when RTT is between 10 ms and 200 ms, normal compression is used; and when RTT is above 200 ms, aggressive compression may be used. This is especially relevant in a lab environment, where client-to-Service-Engine latency is often extremely low. In that situation, compression can be correctly enabled, but Avi may choose not to compress responses because the RTT is below the threshold where compression is considered beneficial. Therefore, the most likely reason initial tests do not show compression is that the default behavior excludes traffic with RTT below 10 ms.
Currently there are no comments in this discussion, be the first to comment!