Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use fast compression instead of none
Historically Chrome's mini_installer has disabled compression for developer builds in order to improve turnaround times. However the mini_installer has grown enough to about 2 GB in debug builds which has caused the executable to be corrupt (for some unknown reason). It turns out that using fast compression rather than no compression is just as fast, while removing some code paths, and the reduced size makes the mini_installer easier to transfer between machines. Since compression is always enabled the enable_archive_compression config and its derivatives were deleted. This change shrinks the debug installer from about 2 GB to about 500 MB. A release non-official install shrinks from about 340 MB to 125 MB. For context, a fully compressed release build would be about 94 MB. The official build mini_installer is unaffected. The mb_config.pyl changes required running mb.py which required fixing it so that it generated correct line endings on Windows. Bug: 1408213 Change-Id: Ib669488f0d2554b09a852f19dfada2b43de9bbc4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4175292 Reviewed-by: Greg Thompson <grt@chromium.org> Commit-Queue: Bruce Dawson <brucedawson@chromium.org> Reviewed-by: Sorin Jianu <sorin@chromium.org> Cr-Commit-Position: refs/heads/main@{#1097544}
- Loading branch information
1 parent
c0658a1
commit acc7c7d
Showing
14 changed files
with
90 additions
and
147 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.