[Fuchsia] Evaluate whether combining WebEngine and WebRunner into one binary is worthwhile. |
|||
Issue descriptionWe currently provide separate binaries for WebEngine and WebRunner, which has the benefit that each only includes the required code for its particular function. However, WebEngine is far larger, and WebRunner includes very little Runner-specific code; we may find that the bulk of the WebRunner is "free" if we roll it into the same binary as the WebEngine. We can still distributed the two as distinct packages; since WebRunner requires WebEngine, the potential down-side in terms of size is just that the WebEngine package, if installed without WebRunner, may be a little larger than is necessary.
,
Jan 17
(5 days ago)
,
Jan 17
(5 days ago)
,
Jan 17
(5 days ago)
We should update US-583 with findings from this.
,
Jan 18
(5 days ago)
I did a quick and dirty one binary build containing all the contents of http_service, web_runner, cast_runner and the chromium binary, which resulted in a binary that is about the same size of service_exe: 80003440 bytes v. 79945040 bytes, that is a 57 kiB difference. The web_runner and cast_runner binaries are each a bit under 1 MiB and the http_service binary is about 6.7 MiB, bringing the potential installed size savings to about 8 MiB total if we did a single binary for all of these. |
|||
►
Sign in to add a comment |
|||
Comment 1 by w...@chromium.org
, Jan 17 (5 days ago)