circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

#68 Make panning, zooming and pinching meet the 150 ms budget at the documented sizes

–

  • github
  • github/openchronology/timeline-app
  • github/openchronology/timeline-app#68
  • issue
  • state:closed

The UI benchmarks (#51, `bench/ui.mjs`) show that navigation is the one area that misses its budgets: view changes and the longest frame in a gesture should both stay within 150 ms. Discrete actions, such as opening a moment, typing, saving and searching, stay well within budget almost everywhere. Medians on a Ryzen 7 7730U laptop in headless Chromium (`docs/benchmarks.md#interactions`): | | Browser 1,000 | Browser 4,000 | Browser 10,000 | ×4 CPU 1,000 | Platform 10,000 | Platform 100,000 | |---|---:|---:|---:|---:|---:|---:| | Wheel zoom (to the view drawn) | 135 ms | **215 ms** | **279 ms** | **350 ms** | **316 ms** | 44 ms | | Drag to pan (longest frame) | 83 ms | 150 ms | **217 ms** | **350 ms** | **183 ms** | 17 ms | | Pinch zoom (longest frame) | 83 ms | **233 ms** | **300 ms** | **367 ms** | **233 ms** | 17 ms | **Observations:** - **The cost follows what is drawn, not what is stored.** The platform is fast at 100,000 moments, where the view collapses into summaries, and slow at 10,000, where many labels are drawn. - **Each zoom step costs a full redraw.** At 1,000 moments, frames during wheel zooming are 67–83 ms each, one per step (the drag frames are 33–50 ms). So a smooth 50 ms frame budget is out of reach until per-step drawing is cheaper. - **Opening a new duration** costs 135 ms at 10,000 moments in the browser and 193 ms on a 4× throttled CPU at 1,000, for the same reason: it redraws. **Directions to evaluate (profile first):** - During a gesture, move already-drawn markers with a transform, and lay labels out again only when the gesture settles or grouping changes. - Reuse label nodes across frames, and avoid layout reads during drawing. - Limit how many individual labels are laid out per frame, and settle the rest after the gesture. **Done when:** `bench/ui.mjs` shows navigation within budget at the comfortable sizes, for both the browser at full speed and the throttled browser (see #69 on calibrating those sizes). The CI gate can then move to larger sizes. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://github.com/openchronology/timeline-app/issues/68

Related

Open #68 Make panning, zooming and pinching meet the 150 ms budget at the documented sizes in the timeline

#68 Make panning, zooming and pinching meet the 150 ms…