iris bench: the fling clock, the frame ask, and a report that says what it measured (ai-app-2 42d54ee)

Browse Source

iris APK only; the Compose one is unchanged. Iris reported stuttering
when flinging that is much harder to notice with a finger on the scroll.

Two of the four findings are the report rather than the renderer: the
blocking swapchain acquire was counted as iris's CPU time, and nothing
could say a frame was never produced (`late` is cost, not cadence). The
report now splits every phase into build/acquire/submit and carries a
`missed vsyncs` count.

The two real ones are the frame loop: it asked for its next frame at the
end of the callback, so a frame past the vsync boundary cost a second
one, and the fling was advanced on the wall clock rather than the vsync
the callback carries -- which is the asymmetry with a finger drag, whose
positions come from the finger's own timestamps.

Also opt-level "s" -> 3 for the Android build: p90 0.15ms -> 0.09ms of
iris's own per-frame work, for 1.8 MB of APK.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

...

This commit is contained in:

irisandClaude Opus 5 committed 2026-09-09 00:50:48 -04:00

1 parent 5efa866727

commit ff88052a5c

2 files changed

+50 -1

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

iris/build/outputs/apk/release/iris-bench-arm64.apk

BIN

Binary file not shown.