| Agents Administration - Tests |
|---|
|
Default Parameters for CtxGwCompressTest Compression reduces bandwidth requirements and can significantly improve server responsiveness in bandwidth-constrained setups. The compression policies are associated with services bound to the virtual server. The policies determine whether a response can be compressed and send compressible content to the target connector, which compresses it and sends it to the client. If you enable the Compression feature, the target connector intercepts requests from clients and determines whether the client can accept compressed content. After receiving the HTTP response from the server, the connector examines the content to determine whether it is compressible. If the content is compressible, the compresses it, modifies the response header to indicate the type of compression performed, and forwards the compressed content to the client. The real test of the effectiveness of the compression feature lies in how much data is compressed and how much bandwidth is saved in the process. Besides the compression algorithm employed, when compression occurs and what type of data is compressed also influence how compression is performed and how beneficial it really is. Moreover, errors encountered when decompressing data also serve as factors impacting user-perception on compression and its usefulness. Using the CtxGwCompressTest, administrators can accurately assess the effectiveness of the compression feature, keep a close watch on all factors influencing compression, and understand how these parameters can be fine-tuned to improve compression ratios and increase bandwidth savings. This page depicts the default parameters that need to be configured for the CtxGwCompressTest.
When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test. |