perf(render): specialize singleton display spawns#65
Merged
Conversation
Arbousier1
force-pushed
the
codex/perf-display-spawn-singleton
branch
from
July 16, 2026 06:56
0a524e2 to
a61bdb2
Compare
TypeThe0ry
marked this pull request as ready for review
July 16, 2026 07:31
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
DisplayEntities.spawnAllwhen a region contains exactly one specArrayListand subsequent copy for the 268 singleton regions in the representative table profileScope
Production candidate only: four added lines in
DisplayEntities.java. No benchmark, threshold, workflow, dependency, or configuration changes.Validation
All functional checks and benchmarking run only on GitHub. After Build/Test are green, this candidate will run the merged base-owned
display-spawnpaired A/B profile and may merge only if the final decision isPASS_OPTIMIZED.