1547797 - Entry size limits should be different for different content-types

Status: NEW

(Core :: Networking: Cache, enhancement, P2)

Description

[Michal Novotny [:michal]]

Compiled wasm stored as alternative data representation in the cache entry can be pretty large and it should have different max entry size limit. We don't expect too many large wasm entries in the cache so it shouldn't happen that they'll occupy most of the cache capacity. If it turns out that it's not true, we can implement per content type quotas.

Comment 1

[Honza Bambas (:mayhemer)]

Is there an umbrella bug for the work?

Comment 2

[Michal Novotny [:michal]]

I don't expect this work to be split into multiple bugs.

Comment 3

[Honza Bambas (:mayhemer)]

Me neither. I am asking for a bug covering the project this one should block. It's more question for Luke.

Comment 4

[Luke Wagner [:luke]]

Thanks for asking. There's not an umbrella bug; there's just bug 1487113 and bug 1545131 and there's not any other future bugs planned beyond this one.

Comment 5

[Valentin Gosu [:valentin] (he/him)]

Unassigning Michal to move bugs back to triage pool.

Comment 6

[Valentin Gosu [:valentin] (he/him)]

Do you think we need to pursue this?

Comment 7

[Yury Delendik (:yury)]

There are really huge wasm application is about to emerge. I filed bug 1719508, and I think having a separate pref for wasm alt-data may be a good approach.

I'm finalizing bug 1545131: it helps with google earth, but we anticipate larger projects, and 50MB might not be enough even when compressed.