Compression
HTTP Compression, like caching, is a best practice that should be implemented in all Web Application deployments. Even with the fast links of today, there are performance benefits to be had, as compression can reduce size upwards of 70 percent. This size reduction in TCP terms means fewer packets and reduced round trip times.
Let's start by looking at what kind of content should and shouldn't be compressed:
- Content that should be compressed:
- Any response that is text based is a good candidate for compression. HTML, CSS, JS, and XML, which are all items that you find on most web pages, fall into this category
- MS Office documents
- Content that shouldn't be compressed:
- Any response that is already compressed should not be compressed; this only adds to the size of the response.
- Images and other binary data should not be compressed for the same reason. Most image formats on the web are already compressed.
The NetScaler's default compression behavior
Go to the Compression...
