Run the Phase 1 benchmark campaign — ingest and reads at 2 s blocks #872

TL;DR

Run the full-history benchmarks against the three Phase 1 synthetic datasets at Phase-1 cadence (2 s blocks), and publish per-profile latency numbers against the Phase-1 targets. The datasets exist (#867); this issue is the first full measurement pass over them.

Phase 1 profile and targets

Block time 2 s (applied at replay — a dataset bakes in only tx model + TPL), retention 3 months.

Targets this run measures against:

• Ingest: Phase-1 target for the meta-available-to-client path is p99 940 ms. The harness measures the ingest slice of that path; results are labeled as the ingest slice, never as the full path (composition with the read/stream slice is tracked separately).
• Reads: GetTransaction / GetEvents / GetLedgers / GetTransactions meet their SLAs at the Phase-1 TPL and block time.

Inputs

Set 2026-07-18-apply-load-20k (generated under #867):

Report

Per profile: p50 / p90 / p99 / max for the ingest slice at 2 s cadence, and read-endpoint latencies vs their SLAs. Use three-state verdicts: met / not met / not measured at this load — and state explicitly that the sac-6000 numbers cover a single chunk.

Done when

All three Phase-1 datasets have published campaign results at 2 s cadence, with a summary table against the Phase-1 targets and explicit labeling of what was and was not measured.

Related

• Synthetic ledger datasets for Phases 1–3 ("golden packs") #867 — synthetic datasets (input)
• Full-history benchmark commands — ingest across all data types #771 / Full-history query benchmark commands — reads across all data types  #856 — the harness commands this runs
• e2e benchmark campaigns workflow — dispatch, run on EC2, publish results #868 — campaign automation (this run may be manual; automation lands there)
• Read-endpoint SLAs under ingestion load #870 — read SLAs under ingestion load (deeper read-side scope)