# Contrail backfill benchmark Fresh, repeatable local-D1 benchmarks for complete Contrail discovery and historical backfill runs. From the repository root: ```bash pnpm bench --config calendar.config.json ``` D1 is the default backend. Use `--backend sqlite` for a fresh in-memory native SQLite run; the result records Node and SQLite versions and gains `-sqlite` in its filename: ```bash pnpm bench --backend sqlite --config calendar-records-only.config.json ``` `calendar.config.json` mirrors the retained indexing shape from `11-atproto/02-atmo-rsvp`: calendar events, RSVPs, profiles, follows/feeds, query indexes, relation counts, and event full-text search. Removed product modules and read-only pipeline handlers are intentionally absent because they do not participate in indexing. To run the same full workload with strict runtime Lexicon validation and canonical DAG-CBOR CID verification enabled: ```bash pnpm bench --config calendar.config.json \ --validation-lexicons apps/benchmark/lexicons/calendar ``` The validated run uses the same config, scheduling limits, and fresh-D1 lifecycle. Its result filename gains `-validated`, records the Lexicon directory/document count, and includes aggregate rejection diagnostics. Compare validation overhead only against an adjacent run with identical limits; live-network differences still need alternating repetitions before they are treated as stable. ## Pinned benchmark runtime This benchmark app pins Wrangler 4.84.1 and its compatible Workers types. Wrangler 4.118.0/workerd 1.20260730.1 made the matched records-only local-D1 workload roughly 2.4× slower than workerd 1.20260421.1, including HTTP and identity phases that Contrail's source-ordering code does not control. Other example and deployment apps remain on the current Wrangler release. Do not update the benchmark runtime as ordinary dependency housekeeping. Rebaseline it deliberately, record both Wrangler and workerd versions, and run old/new Contrail code under the same runtime before attributing a change to…