3 ms·
Not a big surprise. We've hit a point in the I/O bandwidth-to-spare-CPU-cycles ratio where this now saves us time getting bits into RAM. IIRC, the latest Firef
by mmastrac 17y ago
Not a big surprise. We've hit a point in the I/O bandwidth-to-spare-CPU-cycles ratio where this now saves us time getting bits into RAM.
IIRC, the latest Firefox (3.6) is now compressing files on-disk using HFS' built-in compression to cut ~20% off launch time.
- jerf 17y agoActually we hit this point at least a decade ago; I remember getting improved performance by using a compressing filesystem for Windows 3.1. CPUs have been outrunning disks for a while, only the number of orders of magnitude has really changed. Part of this is that even very cheap algorithms can consistently get "some" compression; as the article observes, bzip is still a net loss for many cases, but gzip-style compression has been better-than-free for a while now, as long as your CPU isn't loaded.