David MannandClaude Opus 5.5 d9eb46b485 Performance: the lower-stack cache follows an edit up the stack (P9 / P11, #5286) (#5288) ...

Repeating a duplicate or paste of a 12 MP layer cost as much as the first time because the
GPU compositor's lower-stack cache stayed at the checkpoint of the first edit after it was
filled: an edit higher up only checked that the layers below that checkpoint were unchanged,
so every refresh re-ran all passes above it (in the #209 layered document, 87 of 110 passes
over the 12 MP damage rect; the duplicate itself takes 0.3 ms, its tiles are already shared).

Each cached chunk now remembers its own checkpoint. A render captures at the highest
checkpoint below the edit, also where it resumed from a lower cached one, so the next
refresh of that edit (its undo, redo or repetition) resumes just below it. Chunks a refresh
doesn't reach keep their lower prefix; a chunk moved by a partial capture holds only that
rectangle afterwards. Validity is unchanged: a chunk survives only while the layers below its
checkpoint are untouched.

Release perf_scenarios, layered group, Windows 11, RTX 5070 Ti, 7 interleaved runs:
P9 p50 22-29 -> 12-17 ms, P11 p50 37-41 -> 11-18 ms; P8 and P10 fall too; P1-P7, P12 unchanged.

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-14 12:45:59 -04:00

..

device_loss.rs

fix(gpu): contain errors in unwatched compositor work (#4894)

2026-10-13 13:24:37 -04:00

parity.rs

Performance: the lower-stack cache follows an edit up the stack (P9 / P11, #5286) (#5288)

2026-10-14 12:45:59 -04:00

uniform_limits.rs

fix(gpu): preflight compositor uniform buffer limits (#3931)

2026-10-12 18:44:09 -04:00

vector_mask.rs

Speed up large feathered mask refreshes (#2417)

2026-10-11 07:09:04 -04:00