Repository navigation
Phase 1: Build GPU effect kernels lazily - #9
Merged
Merged
Conversation
Brent001
force-pushed
the
phase1/lazy-effect-kernels
branch
from
October 20, 2026 06:44
2dd3a70 to
0889d88
Compare
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
1 participant
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.
Phase 1 — GPU startup/performance
Port upstream PR storytold#1705 to avoid compiling all ~208 effect kernels during GPU context startup. Kernel families are built on first use from smaller WGSL modules; failures remain eligible for CPU fallback instead of blocking first window presentation.
Source: storytold#1705
This is intentionally isolated because it touches
crates/gpu/src/context.rs, which is also affected by subsequent GPU-cache work. Check Windows DX12/FXC, Vulkan, browser/WASM, and CPU fallback paths before merging.