Context assembly 10.5s to 1.8s
Alex OS assembled its content blocks on every request. A read-through block cache cut assembly time from 10.5s to 1.8s, verified end-to-end.
1.8s (from 10.5s)
- Proof type
- performance
- Confidence
- verified
Every Alex OS request rebuilt all content blocks from the CMS: ~10.5s.
Read-through block cache serves assembled blocks: ~1.8s.
How it was measured
Timed the Alex OS context-assembly path before and after adding the read-through block cache, using the service's own request duration on the same question and the same content set. 10.5s is the uncached rebuild of all content blocks; 1.8s is the same request served from the cache.
Honest limitations
A single before/after run on a development machine against a local database — not a benchmark harness, no repeats, no percentiles. The 1.8s figure is a warm-cache read; the first request after a content change still pays most of the original cost. Network latency to a hosted database would change both numbers.