perf(vcs): landing on the host without waiting, with fewer writes
Radin committed
- Author
- Radin · radin@coline.appOct 28, 2026 at 03:49
- Committer
- Radin · radin@coline.appOct 28, 2026 at 03:49
- Parents
- 0b7cee1fc905
perf(vcs): landing on the host without waiting, with fewer writes Inside a project's Durable Object a landing went from 3.2 ms to 1.5 ms (32 at once: 9.6 to 3.4 ms); over HTTP, one project with 300 agents went from about 157 lands a second to 192. - SHA-256 runs in the core: Web Crypto's digest is asynchronous, and a landing waited on it twice (about 1.6 ms). - Edits on the latest version are worked out in the landing turn, on main as it is then: no merge, and one new copy of each folder instead of two. - Rules are read once; objects aren't looked up before inserting them (the insert skips what's there); storage counters are written once a batch: 31 SQL statements a landing to 18. - Landings for one project that reach a Worker while its last call is still out go together in one call (Workers keep waiting requests alive with a timer, or they're taken for hung). Measured: one Durable Object takes about 600 calls a second that do nothing, so a project's ceiling over HTTP is set by calls, not work. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3 files changed+11−0