3 ms·
The stuff that's big (rich media) already has its own native compression. The stuff that's relatively small (text) also already compresses pretty well without s
by gojomo 15y ago
The stuff that's big (rich media) already has its own native compression. The stuff that's relatively small (text) also already compresses pretty well without shared-dictonaries.
I think that's the reason: it's not that big a win over the total traffic of a modern browsing session. For example, I doubt jgrahamc's experiment yields a 90% savings over the entire browsing session with BBC News, when getting images, and if gzip is already enabled on the HTML/CSS/JS. I'd guess closer to 10%.
Updated after taking a quick look at BBC News homepage in Firebug's net panel:
The BBC News homepage has about 150KB of HTML/CSS… but they haven't even bothered to turn on gzip, which might bring that down to 30KB. It has about 230KB of images, which wouldn't be helped by a shared dictionary.
If they turned on gzip, text would be about 30/230=13% of the bandwidth. Even 99.99% compression – a dictionary of exactly today's content already on the client! – could only shrink the homepage download by 13%.