Topic

Performance

Following a slow path down to the operation that causes it.

All technical writing

2026

  1. A faster check has to fail the same way

    Two optimization campaigns and a queue change on agent tooling, where golden outputs, differential checks and A/B gates test whether a speedup keeps its behaviour.

    Agent systemsPerformanceVerification

  2. A prompt that holds still while the files change

    How provider-specific reasoning replay and a frozen working set of files keep a prompt prefix cacheable while the agent is still told what changed.

    Agent systemsPerformance

  3. Making an agent’s memory useful without slowing its next reply

    Capture, evidence, retrieval, projection and delivery can each fail alone. A small replay found a fact lost before search could see it, and 92 live calls carried no receipt that any memory had arrived.

    SelectedAgent systemsMemoryRetrievalPerformance

  4. Copying code on purpose when applications can’t share a crate

    When an application may link only one crate, shared code has to be copied. A canonical source tree, declared mounts, file hashes and a drift check keep the deployed copies aligned.

    PlatformsVerificationSecurityPerformance

  5. Why opening a conversation should not wait for its whole history

    A page asking for twelve entries could still wait 31 seconds. Pagination limited the answer and not the work behind it, so the design serves the first view from read models the writers maintain.

    PerformanceArchitectureAgent systems

  6. Publishing a SQLite database through one compare-and-swap

    How a WebAssembly SQLite adapter makes a whole database image live through one manifest swap, why deletes follow publication, and what bounded cleanup leaves behind.

    PlatformsPerformance

  7. Real files on disk, with sync running beside them

    Two systems that give tools an ordinary directory and sync alongside it: echo detection without clocks, a guarded remote commit, and measured cold-restore times.

    PlatformsPerformanceAgent systems

  8. Reducing allocation churn in an agent platform

    Why an agent gateway with broad retained state allocated gigabytes a minute, how repeated sizing and serialization drove it, and what bounded buffers and encode-once paths do and don't fix.

    PerformanceMemoryProfilingTypeScriptAgent systems

  9. The invalidation that arrives while the loader is running

    Why a cached entry must record tag epochs before its loader runs, why writers invalidate after they write, and why leases only limit duplicate loads.

    PlatformsPerformance

  10. Twenty-one workspaces sharing one filesystem flush

    Diagnosing a 5.6× slowdown across 21 agent workspaces with a durability-matched control, and why a filesystem-wide syncfs made deployment layout part of its design.

    PerformancePlatformsAgent systems

  11. What an agent can afford to lose

    Sorting an agent platform’s data into irreplaceable work and rebuildable cache, and letting that decide journal storage, migration, eviction and restores.

    Agent systemsPlatformsPerformance