| |||||||||||||
|
| |||||||||||||
Bitmap cacheBitmap cachePosted Jul 28, 2007 14:00 UTC (Sat) by Los__D (subscriber, #15263)In reply to: Bitmap cache by man_ls Parent article: Still waiting for swap prefetch
It really depends on the cost of CPU vs. the cost of memory.
For most usage patterns, I agree, but for those that likes to have 30+ tabs open (for some reason), caching the uncompressed bitmap is a _big_ waste.
The question is if the best approach wouldn't be to just forget or limit those caches for that kind of usage. At least the bitmap approach is asking for disk trashing.
(Log in to post comments)
Bitmap cache Posted Oct 9, 2007 18:49 UTC (Tue) by Blaisorblade (guest, #25465) [Link] I've read time ago a comment from a OLPC developer on exactly this issue. I'm writing a summary of his comments I recall.Basically, an application can store an uncompressed bitmap in the X server. And Firefox caches all images this way! That's the problem. Probably avoiding the caching would be even faster (due to no swapping).
IMHO (and this is my opinion, I don't recall his one) a reasonable solution would be to extend the X protocol to allow caching compressed images in most reasonable formats (including especially JPEG). Then the X server can keep a cache of most shown decoded images.
Since the JPEG compression ratio is huge, there would be a huge gain from this.
|
|
||||||||||||