Repository navigation
Open
Labels
p2Eventually: real, but nothing waits on itEventually: real, but nothing waits on itperformanceCPU/GPU/memory/idle cost and benchmarkingCPU/GPU/memory/idle cost and benchmarkingready-for-agentFully specified, ready for an AFK agentFully specified, ready for an AFK agent
Description
Out of V1: needs a bare-metal Linux machine with a GPU or multiple monitors, which isn't available. Don't pick this up or re-test it until one is.
Objective
Measure frame-to-frame timing (rAF callback deltas) and detect dropped frames (>16.67ms gaps). Validate interpolation smoothness claim from src/interpolate.js.
Tools
- Browser DevTools (Performance tab, record rAF timestamps)
- Custom logging: Add
console.log(performance.now())todraw()insrc/main.js:250 - Analyze: Plot histogram of frame deltas, count drops
- Optional: High-speed camera recording (240fps) to visually validate smoothness
Scenarios
- Idle perched: Sprite still
- Walking: Sprite walking
- Riding moving window: Drag window with sprite on it
- CPU load: Compile large project in background while buddy runs
- Multi-monitor: Sprite crossing seam between displays
Metrics to Capture
- Frame cadence: Histogram of rAF callback deltas (ms)
- Dropped frames: Count of deltas >20ms (missed vsync)
- Interpolation lag: Measure actual lag between Engine tick and webview render (compare timestamps)
- Frame rate (fps): Average from rAF timestamps
Expected Results
- Hypothesis (from interpolate.js): Engine ticks at ~44Hz (16-38ms deltas), webview renders at 60Hz, interpolation smooths motion
- Idle/walking: Should see consistent 16.67ms rAF deltas (60fps)
- CPU load: May see occasional drops (but interpolation should hide small gaps)
- Multi-monitor: No drops expected (each overlay is independent)
Acceptance Criteria
- Histogram of frame deltas for each scenario (plot or table)
- Count of dropped frames (>20ms gaps)
- Confirm 60fps rAF rate (or report actual rate)
- Validate interpolation lag is 1 sample (1 Engine tick behind)
- Results documented, compare to design claim
Related
- Parent issue: perf: Establish performance baseline for drawing layers + engine #423
- Design claim:
src/interpolate.js:9-23(measured deltas 16-38ms) - Renderer:
src/main.js:250rAF loop
— Cursor agent, on @omesser's behalf.
Metadata
Metadata
Assignees
Labels
p2Eventually: real, but nothing waits on itEventually: real, but nothing waits on itperformanceCPU/GPU/memory/idle cost and benchmarkingCPU/GPU/memory/idle cost and benchmarkingready-for-agentFully specified, ready for an AFK agentFully specified, ready for an AFK agent
Projects
- StatusShow more project fieldsIce Box
Activity
perf(overlay): Trace display frames behind FIDGET_TRACE_CADENCE
perf(overlay): Trace display frames behind FIDGET_TRACE_CADENCE
perf(overlay): Trace display frames behind FIDGET_TRACE_CADENCE
omesser commentedon Sep 29, 2026
Progress — #1149 merged to
mainMerge:
5dfa46763be05269bf4db2e29aa5171106605b71.Shipped (macOS only)
On
mainnow:FIDGET_TRACE_CADENCE(off by default)scripts/frame-cadence.mjs+ fixture testsscripts/bench-frame-cadence-macos.sh(idle/walking/load/matrix)docs/research/performance-baseline-v1.mdinterpolate.jscomment corrected to the measured 53 Hz Engine rate (was 44 Hz)Acceptance progress against this issue:
Still open on this issue
Findings already spun out (separate jobs, leave this open):
Leaving #426 open until the remaining scenarios/platforms are measured (or explicitly deferred).
— Cursor agent (Coder), on @omesser's behalf.
omesser commentedon Sep 30, 2026
Progress — #1166 / #1155 merged to
mainMerge:
3145d50f806976d9a865b202218308d886caa1c9. Issue #1155 closed as completed.Shipped
Idle perched no longer pays a display frame for each 250 ms
FRAME_RESENDof an unchanged placement. Overlayframelistener compares serialized placement to lasttoldand skipsarm()on a byte-identical resend; late listeners still get the first placement. Covered bytests/frame-resend.test.jsand a still-stretch bench on tip84ba6ba4(12 animation-frame changes = 12 display frames, 0 re-arms).That closes the idle-resend finding called out after #1149. It does not finish this umbrella: Windows/Linux benches, riding a moving window, multi-monitor seam, and a deterministic idle scenario (StaticDirector can pick
patrol, so whole-window totals are not comparable with #1149) remain open.Leaving #426 open.
— Cursor agent (Coder), on @omesser's behalf.
omesser commentedon Oct 1, 2026
Progress — #1203 on
main(leave open)Merge:
d85fa2a12a501187f1d1da843bc86c0366601025.Newly on main
scripts/bench-frame-cadence-macos.sh(script now exportsXAUTHORITYbefore replacingHOME) indocs/research/performance-baseline-v1.md.Still open (acceptance)
Leaving open.
— Cursor agent (Coder), on @omesser's behalf.
omesser commentedon Oct 2, 2026
Slice in #1263. The issue stays open.
Measured. macOS cadence tables and the Linux release idle, walking, and load tables were already on main. This slice adds one Linux ride from the release binary at
543dad19on the cloud VM (DISPLAY=:1, one 1920x1200 screen at 60 Hz). Anxtermglided 2 px about every 20 ms for 20 s. The window held 392hold#frames, all at y=806, x from 769 to 1177, 262 distinct positions.scripts/frame-cadence.mjsreported 546 display frames, 62.2 fps on armed stretches, 1 drop over 20 ms, engine counter 62.1 Hz, lag p50 17 ms (1 sample), lag p95 114 ms (1.07 samples).Harness, no Windows numbers.
scripts/bench-frame-cadence-windows.ps1runsidle,idle-quiet,walking,load, andmatrix. It requiresFIDGET_BENCH_GREEN_LIGHT=1andOS=Windows_NT, and it prints the same analyzer report. No Windows machine ran it, so the baseline has no Windows histogram.Still open. Crossing a display seam is unmeasured. This VM has one screen. The acceptance checkboxes need that seam and a Windows operator capture before the issue can close.
— Cursor agent, on @omesser's behalf.
omesser commentedon Oct 2, 2026
Progress — #1263 merged to
mainMerge:
241c033ac2ec0b2459a88a610985904f2823cdb4.Newly on main
scripts/bench-frame-cadence-windows.ps1— gated Windows harness (idle/idle-quiet/walking/load/matrix), green-light +Windows_NTrequired, samescripts/frame-cadence.mjsreport path as macOS/Linux.docs/research/performance-baseline-v1.mdfrom release binary at543dad19(392hold#frames, 546 display frames, 62.2 fps armed, 1 drop >20 ms, lag p50 17 ms / 1 sample).macOS idle/walking/load and Linux idle/walking/load tables were already on main from earlier PRs.
Still open (acceptance)
Leaving #426 open. Parent #423 stays closed (umbrella already completed).
— Cursor agent (Coder), on @omesser's behalf.
omesser commentedon Oct 3, 2026
Progress — #1311 Soft-gated (leave open)
Windows open item from this issue: operator capture on DESKTOP-UQIE144 (MS-7D25), release
fidget.exeatb0f57a78.Measured
FIDGET_BENCH_GREEN_LIGHT=1 scripts\bench-frame-cadence-windows.ps1 matrix -Seconds 20 -Bin target\release\fidget.exe. Header: Windows 11 Pro for Workstations, refresh 59, 20 cpus,git_rev=b0f57a78.Tables and histograms land in
docs/research/performance-baseline-v1.mdvia #1311.Still open
Leaving #426 open until the seam is measured or deferred.
— Cursor agent (Coder), on @omesser's behalf.
9 remaining items
omesser commentedon Oct 4, 2026
Progress — #1312 merged to
main(reopened)Merge:
2c3b54b8d1542b132b52510184a72296c985d7b9.GitHub auto-closed this via the PR’s Development closing link when #1312 merged. The PR body said it does not close #426 (docs Soft-FIX only). Reopening.
Newly on main
Wording Soft-FIX in
docs/research/performance-baseline-v1.md(tip4cf03cfc):No new measurements.
Still open (acceptance)
Leaving #426 open. Parent #423 stays closed.
— Cursor agent (Coder), on @omesser's behalf.
omesser commentedon Oct 10, 2026
Progress: #1478 merged to
main(reopened)Merge:
bd37844f77f3b2dd316de22bcb3d5fba593e58c8.GitHub auto-closed this when #1478 merged, because the PR body's sentence "This does not close #426" contains the closing phrase "close #426". The PR says it does not finish this issue, so I'm reopening it.
Newly on main
summarizeTimestampsturns frame timestamps into a histogram, a drop count, and an average fps, withDROP_MSas the single 20 ms threshold (covered bytests/frame-cadence.test.js).scripts/bench-frame-cadence-macos.shnow waits onprocess.logand copies the trace out before deleting the scratch home, so a release binary feeds the bench.docs/research/macos-idle-frame-cadence.md: one idle perched minute on macOS. Consecutive callbacks averaged 1.6 fps with 93 gaps over 20 ms, because a perched sprite doesn't request the next frame; one armed gap was over 20 ms; still Engine ticks averaged 21.6 ms (46.4 Hz). Interpolation lag is empty because the sprite never moved.Still open (acceptance)
Leaving #426 open. Parent #423 stays closed.
— Cursor agent (Coder), on @omesser's behalf.
omesser commentedon Oct 23, 2026
Moved off V1 at Oded's request: needs a bare-metal Linux machine with multiple monitors, which isn't available. Back to a milestone once one is.
The macOS, Windows (including the dual-display seam ride) and single-display Linux rows are on main. The only item left is the Linux display seam, and the box VM has one output per display, so it can't be measured there.
— Cursor agent (Architect), on @omesser's behalf.
omesser commentedon Oct 23, 2026
Post-merge check after #1798, which marked this issue out of V1. Acceptance items checked against
docs/research/performance-baseline-v1.mdon main (350dcece):src/interpolate.jscomment was updated.Ticked those four. Left open with no milestone: the Linux seam is the only thing left, and it waits for multi-monitor Linux hardware.
— Cursor agent (P. Coder), on @omesser's behalf.