Repository navigation
AOT-compile the GitHub Pages deploy - #155
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deploy publishes with
RunAOTCompilation=true. PR checks and local dev stay on the plain build.PublishTrimmed=true, so AOT builds turn it on and root every assembly. Nothing gets trimmed and Roslyn still sees the full API surface.WasmInitialHeapSizeis set for AOT to skip thellvm-sizestep, which fails on Windows with one huge command line.wasm-toolsworkload install to deploy.Measured locally: download 26 MB -> 55 MB (Brotli), publish about 2.5 min -> about 1 h. Gum UI frame time is much lower with AOT.
Not verified in CI: deploy only runs on main, so the first AOT deploy happens on merge. Since deploy has
cancel-in-progress, merging again within the hour cancels the deploy that's still running.Closes #154