4 ms·
The author's testing methodology appears unable to tell leakage from caching. If your machine isn't swapping, then any unused memory is wasted. Better to keep
by jws 15y ago
The author's testing methodology appears unable to tell leakage from caching.
If your machine isn't swapping, then any unused memory is wasted. Better to keep all sorts of speculatively cached data. For a web browser that includes downloaded resources, but it could also include the rendered bitmaps of page fragments, preparsed documents, or any manner of partial computation that may be reused later. Once there is memory pressure the code can start dropping these things.
- hackermom 15y agoAssuming it's just cached content, Safari 5.1 is then caching _a lot_ more than 5.0.x did.