Open
Bug 1124823
Opened 9 years ago
Updated 2 years ago
HTTP cache: Allow on-demand intermediate memory caching of (otherwise disk cached) content
Categories
(Core :: Networking: Cache, enhancement, P5)
Core
Networking: Cache
Tracking
()
NEW
People
(Reporter: mayhemer, Unassigned)
Details
(Whiteboard: [necko-would-take])
Two good reasons: - get rid of ImageLib cache and let it rely on HTTP caching - cache some of render blocking data (CSS,JS,HTML) Now we have it just as an overall #define compile time option. Would be nice to have the option at run-time and per entry. Impl notes: we need a new pool (maybe generalize them completely?) and a new limit with a new pref, what should the limit be? ; new API to instruct the cache (through the nsICachingChannel iface?). What about prefetches? Do we control them too?
Comment 1•9 years ago
|
||
Thanks for filing this, Honza! One idea that I think might make this more palatable to the memshrink folks would be to land this pref'ed off initially, and pref it on at the same time that we disable the ImageLib cache. We'd then be in some sense "transferring" the ImageLib cache's memory usage to the generic HTTP in-memory cache, which would probably reduce the impact on e.g. AWSY quite a bit.
Updated•8 years ago
|
Whiteboard: [necko-would-take]
Comment 2•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•