Compressing responses and its impact on performance

news scaling
Posted by Melissa

14 August 2014

We constantly monitor our system and look for ways to enhance performance for you, our customers. We recently started compressing all of our responses to reduce their size. For example, when downloading Mingle’s main javascript file, the uncompressed response would have required your browser to download 2MB of data. The same content gzipped only requires downloading 518KB. The effect of this size reduction is particularly helpful for geographic locations farther from our data centers in California, USA.

As you can see in the image below, gzipping response data reduced receiving time by 75% dropping it from 0.4 to 0.1 seconds:

Gzip optimization

An easy fix to help improve your experience. Hopefully you’ve noticed the difference! If you aren’t already, you may want to consider doing this for the products you’re building. It is easily enabled in most popular web servers (e.g. Apache’s mod_deflate) and application servers (in Mingle’s case, Tomcat).

comments powered by Disqus