perf(render): apply regions directly with prepared fingerprints#113
Closed
TypeThe0ry wants to merge 1 commit into
Closed
perf(render): apply regions directly with prepared fingerprints#113TypeThe0ry wants to merge 1 commit into
TypeThe0ry wants to merge 1 commit into
Conversation
Arbousier1
force-pushed
the
codex/perf-region-direct-apply
branch
from
July 18, 2026 12:57
11ddee1 to
2bed25c
Compare
Collaborator
|
Formal trusted A/B run did not pass: INCONCLUSIVE_NOISE_OR_NO_GAIN. Evidence: https://github.com/EllanServer/MahjongEngine/actions/runs/29645451416. Closing per the performance gate policy. |
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.
What changed
Why
Every refresh built multiple temporary lists and hundreds of captured actions, while exact FNV fingerprints were recomputed on the region thread.
Impact
Region keys, exact FNV values, entity specifications, update order, and one-tick deferred behavior remain unchanged.
Evidence
Eight paired runs:
Validation
TableRegionDisplayCoordinatorTestjmhJarspotlessCheck