Run the Phase 3 benchmark campaign — ingest and reads at 600 ms blocks #874

TL;DR

Run the full-history benchmarks against the three Phase 3 synthetic datasets at Phase-3 cadence (600 ms blocks), and publish per-profile latency numbers against the Phase-3 targets. Phase 3 is the epic's end-state load; two datasets are complete 20,000-ledger sets and the SAC dataset covers one full 10k chunk (#867).

Phase 3 profile and targets

Block time 600 ms (applied at replay — a dataset bakes in only tx model + TPL), retention 2 years.

Targets this run measures against:

• Ingest: Phase-3 target for the meta-available-to-client path is p99 140 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-3 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 600 ms 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. If the ingest slice cannot sustain the 600 ms cadence, report the sustained cadence it does hold in addition to the latency distribution.

Done when

All three Phase-3 datasets have published campaign results at 600 ms cadence, with a summary table against the Phase-3 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)
• #TBD — Phase-1 campaign (template and shared packs; fill in once posted)