perf: complete macOS render, decoder, and capacity controls - #81
Merged
Conversation
This was referenced Aug 29, 2026
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.
Summary
This is the coordinated follow-up for the macOS performance roadmap:
HYPERWALL_RENDER_PROFILE=low-costtier without changing Windows/Linux defaults.analyze_run()reports and select the highest passing mode.Operational intent
The goal is to make the wall behave predictably under pressure: reduce avoidable GUI queue work, keep one bad resource from changing wall-wide decoder policy, and avoid silently promoting an unsupported cell count. The default HQ render path remains unchanged until a fixed-corpus comparison proves the cheaper tier is acceptable.
Validation
python3 tests/run_all.py: all suites green.git diff --checkpass.Hardware boundary
This PR provides the controls and reporting needed for the M5 run. It does not claim that 8-cell playback is production-ready, does not make VideoToolbox a global default, and does not use the rejected
30 fps / 25 Mbpslive-transcode shaping. The physical 4/6/8-cell M5 matrix and fixed-corpus visual comparison remain qualification work.Tracking
Refs #75
Refs #76
Refs #77
Refs #78
Refs #79