History takes seconds to draw a game with thousands of snapshots #217

Closed
opened 2026-10-27 04:17:51 -05:00 by ethan-hann · 1 comment
Owner

The History screen's lists are not virtualized: every snapshot card is built and laid out. In a headless measurement a game with 3000 snapshots took about 10 s to lay out, before any search; narrowing a search to one card took 196 ms and clearing it again took 8 s. Filtering in the view model is instant, so the cost is in the views. A player with months of sessions on a mid-range PC would wait on every visit. Virtualize the History timeline and Saves column (and Recently removed), keep keyboard navigation, focus restore and screen-reader names working, and add a timing test with a few thousand snapshots.

The History screen's lists are not virtualized: every snapshot card is built and laid out. In a headless measurement a game with 3000 snapshots took about 10 s to lay out, before any search; narrowing a search to one card took 196 ms and clearing it again took 8 s. Filtering in the view model is instant, so the cost is in the views. A player with months of sessions on a mid-range PC would wait on every visit. Virtualize the History timeline and Saves column (and Recently removed), keep keyboard navigation, focus restore and screen-reader names working, and add a timing test with a few thousand snapshots.
ethan-hann added this to the 1.0 milestone 2026-10-27 04:17:51 -05:00
Author
Owner
Fixed in 0.9.18 (PR 233): https://git.tortal.tech/ethan-hann/SavePoint/releases/tag/v0.9.18
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ethan-hann/SavePoint#217
No description provided.