Repository navigation
frame-cost todo: option 3 is done, and what it did not fix - #44
Merged
Merged
Conversation
The table in this file quoted numbers from before the Candles gather landed, and its option 3 was still written as future work. Both are now true again, and the numbers are re-measured on merged main. The headline worth keeping: koln (31.9 ms) and apollo (32.9 ms) now fit a 30 fps frame; promises (50.2 ms) and nocturne (41.7 ms) do not, and both are bounded by AuroraVeils/NoiseGlow seams that no candle work touches. Option 1 is the only remaining one that covers promises, because the problem there is two expensive scenes of the same kind blended together rather than one wasteful primitive. Also noted: repeat runs vary by a few ms — the ranking of seams is stable, the individual figures less so — and the two shows that now fit a frame fit it with nothing else running, which is not the condition they will be played in. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FbzmvdzTNSUxDUjVraRZMx
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.
Bookkeeping I said I'd do once the merge order settled. The file landed with #42 quoting pre-Candles numbers and listing option 3 as future work; #43 then did option 3. Both facts re-measured on merged main.
kolncoming-to-rest(NoiseGlow + Motif)apollomatta(AuroraVeils)promisesanswer(AuroraVeils into AuroraVeils)nocturnedeep-sea(NoiseGlow + Starfield)kolnandapollonow fit inside a 30 fps frame,apolloonly barely.promisesandnocturnedon't, and both are bounded by seams no candle work touches — option 1 is the only remaining one that coverspromises, because the problem there is two expensive scenes of the same kind blended together, not one wasteful primitive.Two honesty notes added to the file: repeat runs vary by a few ms (the seam ranking is stable, the individual figures less so), and the two shows that now fit a frame fit it with nothing else running — no codec, no serial, no viewers, no six boards attached. That is not the condition they will be played in.
Docs only; no code touched.