Chrome binary size - feature call

[Patrick Meenan]

I'm working on a feature that tracks a list of ~200 URL patterns that should go into a single-keyed HTTP cache and have a question on how to make the call if it belongs on Fuchsia or not.

The CL increases the compressed size of web_engine and chrome_fuchsia by 40kb. I made a pass at zstd-compressing the static list (Patchset 10) but that increased the compressed sizes by 64kb because of the addition of the zstd library.

The feature is an optimization. Nothing will break if it is compiled out for Fuchsia but it also saves a LOT more space if Fuchsia maintains a persistent HTTP cache because it removes the duplicate storage of the common resources in the list (analytics, ads, maps embeds, youtube embeds, etc).

I'm happy to ship it or not on Fuchsia, I'm just not sure which side of the line things fall on and how much the browser is used for general browsing vs showing more controlled content.

Thanks,

-Pat