Repository navigation
ng1: add resident lifecycle and telemetry bounds (M7+M8) - #758
Merged
techomancer merged 5 commits intoNov 17, 2026
Merged
Conversation
Tzeentchnet
force-pushed
the
feature/gpu-upstream-m7-m8
branch
2 times, most recently
from
November 17, 2026 02:09
f5e9d14 to
42a905b
Compare
Tzeentchnet
force-pushed
the
feature/gpu-upstream-m7-m8
branch
from
November 17, 2026 03:06
42a905b to
c77976a
Compare
Tzeentchnet
force-pushed
the
feature/gpu-upstream-m7-m8
branch
from
November 17, 2026 03:34
c77976a to
7523a9f
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
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.
Important
#757 is integrated as
30fb9840. This branch is rebased onto upstreammainata4848ef7and now contains only the five M7+M8 commits.Summary
Efficiency evidence and limits
This responds to the concern that efficient wgpu acceleration of REX3 may not be possible by making the costs visible and bounded, not by claiming a speedup.
A fresh independent mixed-workload rerun on both backends accepted 30 operations with zero unsupported work and produced:
The committed PROM-replay measurements remain test-path evidence, not production application timing. The optional local recorder input is not in the repository, so it was not used as fresh PR evidence. The mixed gate also includes GPU setup and a CPU oracle, so no host-CPU or end-to-end speed claim is made; production IRIX application acceptance remains open.
Scope
This PR adds five M7+M8 commits directly above merged #757: four milestone commits plus the post-CI corpus reconciliation. Production activation and frontends remain M9/M10 work.
Validation
The exact 130-case resident gate passed on both required hardware backends on an NVIDIA RTX 5070:
Additional checks passed:
cargo check --locked -p iris --no-default-featurescargo check --locked -p iris --no-default-features --features wgpucargo check --locked -p iris --no-default-features --features rex-gpucargo check --locked -p iris-gui --features iris/wgpumainata4848ef7following ng1: add resident HostR and explicit observers (M5+M6) #757's squash merge