PERFORMANCE Signal 437
Harper 5.2 adds record cache and isolated commits, benchmarks co-located architecture against Vercel stack
↗
Harper released version 5.2 with a record cache serving repeated reads five to eight times faster and isolated database commit paths that reduce p99 latency on unrelated operations from 223.7ms to 2.6ms, alongside a benchmark showing its co-located architecture outperforms a Vercel-based multi-system stack on live personalized-data workloads by up to ~14×.
The release directly addresses a real operational pain point, shared commit paths that stall unrelated work under heavy writes, while the benchmark provides concrete data on when a single-runtime architecture beats a distributed stack. The results are workload-dependent: co-located runtimes win on personalized data paths, while serverless stacks win on cacheable content and high-concurrency fan-out.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Harper 5.2 adds a record cache serving repeated reads five to eight times faster and isolates each database's commit path to prevent heavy writes from starving unrelated work.
Isolating commits dropped the p99 of an unrelated filesystem call from 223.7ms to 2.6ms, fixing a problem where all database commits shared Node's libuv worker pool.
Harper's benchmark shows its co-located architecture outperforms a Vercel-based stack on live personalized-data workloads by up to ~14×, but Vercel wins on cacheable content and high-concurrency fan-out.
THE CLUSTER