iris bench: one retained move for pinned growth (ai-app-2 fffed42)

This commit is contained in:
iris committed 2026-09-09 16:23:48 -04:00
1 parent 96fc463ed4
commit 6d813942d0
2 files changed
+21

No files matched your search

+21
View File
@@ -9,8 +9,29 @@ build machine. Add this checkout as a project in Dev Updater (its
beside the real app under their own application ids and need no server,
no enrolment and no permissions.
**This is the publication repository, not the source repository.** The iris
APK is built from `~/repos/ai-app-2`'s `rustify` branch, copied to
`iris/build/outputs/apk/release/iris-bench-arm64.apk` here, then committed and
pushed on this repository's `main` branch. Dev Updater pulls this repository
and serves that committed APK; pushing `ai-app-2` by itself publishes nothing
to the benchmark card.
The rest of this file is the runbook that was delivered with the APKs.
**2026-09-09 (latest): pinned growth moves the retained transcript once.**
`iris-bench-arm64.apk` rebuilt from ai-app-2 `fffed42`. This is the
framework-level `LazySpan` change: when a streaming message grows and pushes
the transcript upward, retained rows keep stable local boxes and one shared
child-coordinate slot moves the subtree. There is no transcript-specific
rendering shortcut.
The layer-1 upload rig over 401 streamed events now reports instance uploads
at **2.9% against a 2.9% floor**, from 71.9% against 71.8%; median instance
upload fell from **176,496 bytes to 1,728 bytes**. Settled list movement is one
real list draw and one shared move-slot write. The framework and app suites,
the transcript edge/clamp tests, the arena rig, and a phone-shaped headless
fling replay all passed before this APK was published.
**2026-09-09 (later): the report itself was wrong in three places, and
two of them were mine from this morning.** Rebuilt from ai-app-2
`9bf714f`, iris APK only. Your run said "now THAT is smooth" and the
Binary file not shown.