browser.cache.disk.max_entry_size is too small for wasm altdata
Categories
(Core :: Networking: Cache, enhancement, P4)
Tracking
()
People
(Reporter: yury, Unassigned)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [necko-triaged])
While working on bug 1487113, I hit the limit of the cache entry. The JIT'ed code at earth.google.com takes about 55MB, so the entry is discarded.
Can we increase the limit of 50MB that is set at "browser.cache.disk.max_entry_size"? Or perhaps have different one for altdata?
|
||
Comment 1•3 years ago
|
||
Let's have a different one for altdata.
What is the priority of this issue? Do you want work on this bug?
|
Reporter | |
Comment 2•3 years ago
|
||
What is the priority of this issue?
It depends on landing of bug 1487113. Since it is possible to configure the settings via about:config it is okay to block on the former bug and increase priority if testing results will be promising.
Do you want work on this bug?
I rather stick to wasm aspects of the issue.
|
|
||
Updated•3 years ago
|
|
||
Comment 3•2 years ago
|
||
We'll probably need to get this reprioritized in Q2 and ideally addressed in Q3, as wasm caching will be ineffective on the sites that matter most without a different cache limit. Serious applications (Photoshop probably the most prominent one) turn into hundreds of MB of machine code, and we really want this to be cached.
Description
•