knock-knock-who-there-file-compression-talk_FINAL_2.tar.trz.bz2.gz
summary
Shows an actual Node HTTP server that uses fs, zlib and pump to stream and gzip/deflate files and measures outcomes with curl and wc, claiming minification can save ~50%. Measured gzip and deflate give similar sizes and latency (~0.15–0.18s), brotli halves payload size at the cost of higher CPU and latency, and snappy trades compression for speed. Demo uses on-the-fly compression of assets including yourFavPhilCollinsSong.wav and prints concrete size and timing numbers.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:28Abraham Lempel and Jacob Ziv
- 0:46this seasons hottest codebuster
- 6:08generate frequency table
- 11:42create better tradeoffs
- 21:40intune to HTTP compression
related talks
24mknock-knock-who-there-file-compression-TALK-FINAL-4.tar.trz.bz2.gz
46mNot Only Gzip
03mWhen small is better: Brotli compression in a real case
47mWeb Compression: How to (Re)Take Control?
42mHoney, I Shrunk the Bits. Or how modern HTTP compression works.
52mCompression Dictionaries
51mWeb Compression: How to (Re)Take Control?
43mzip Code: Unpacking Data Compression