5 captures
05 Sep 2015 - 25 Apr 2024
Aug SEP Oct
05
2014 2015 2016
success
fail

About this capture

COLLECTED BY

Organization: Internet Archive

The Internet Archive discovers and captures web pages through many different web crawls. At any given time several distinct crawls are running, some for months, and some every day or longer. View the web archive through the Wayback Machine.

Collection: Wide Crawl Number 13

Web Wide Crawl Number 13
TIMESTAMPS

The Wayback Machine - http://web.archive.org/web/20150905204416/http://lwn.net/Articles/543135/
 
LWN.net Logo

Log in now

Create an account

Subscribe to LWN

LWN.net Weekly Edition for September 3, 2015

Debsources as a platform

LWN.net Weekly Edition for August 27, 2015

Reviving the Hershey fonts

Glibc wrappers for (nearly all) Linux system calls

Minify vs Compression?

Minify vs Compression?

Posted Mar 15, 2013 19:12 UTC (Fri) by dlang (✭ supporter ✭, #313)
In reply to: Minify vs Compression? by alex
Parent article: SCALE: The life and times of the AGPL

enabling gzip with dynamic content adds a significant CPU load to the webservers. For a small site this may not matter, but for a large site, it's frequently cheaper to get the extra bandwith and send out the minified version uncompressed than to pay for the extra machines needed to enable gzip.


(Log in to post comments)

Minify vs Compression?

Posted Mar 18, 2013 16:05 UTC (Mon) by njwhite (subscriber, #51848) [Link]

But as this is regarding minification, we're talking about non-dynamic content anyway, right? So a site could (and many do) gzip their content just once.

Some frameworks offer on demand minification too (MediaWiki's ResourceLoader is the one I know), so technically minification can also be done for dynamic content, but as you say, it depends on where the bottlenecks are as to whether that's a wise move.


Copyright © 2015, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds