3 ms·

A single core machine already overloaded is going to get even worse introducing the cpu overhead of gzipping response bodies (assuming it’s cpu bound and not IO

A single core machine already overloaded is going to get even worse introducing the cpu overhead of gzipping response bodies (assuming it’s cpu bound and not IO bound) Cache control headers will help with return traffic More cpu cores If using nginx ensure sendfile is enabled and workers are set to auto or tuned for your setup Check ulimit file handle limits Offload static assets to cdn Since it’s a static html site, you could even host on s3, netlify, etc

brazzledazzle 3y ago
Could even host on github pages with a cname.
jwilk 3y ago
It's a static file. You need to compress it only once, not for every response.
- ptx 3y ago
  ...and here's how to do it in Apache: https://httpd.apache.org/docs/2.4/mod/mod_deflate.html#precompressed https://httpd.apache.org/docs/2.4/mod/mod_deflate.html#preco...
insanitybit 3y ago
> A single core machine already overloaded is going to get even worse introducing the cpu overhead of gzipping response bodies (assuming it’s cpu bound and not IO bound) Unless your CPU is burning due to additional system calls being made.