Research

Recovery tracks live state, not history depth.

0.6–0.9 ms

TCC recovery · depth 10 → 1,000

61 ms → ~1.7 s

Temporal reconstruction · same workload

Recovery latency vs prior durable-boundary depth 1ms 10ms 100ms 1s 10 100 1000 durable-boundary depth
TCC recovery Temporal reconstruction Controlled evaluation · ~4 KB live state

In the matched local depth workload, with live continuation state held at ~4 KB, TCC recovery remained approximately history-insensitive across 10–1,000 durable boundaries. Temporal in-flight workflow reconstruction increased with accumulated workflow history.

These are local-harness measurements. They characterize a scaling law. They are not a production-server speedup headline.