Spate run by the vendor
native · etl-framework · Apache-2.0 · active · rust
Homepage · Its configuration in this repository
Has this configuration been reviewed upstream?
n/a — the vendor of this system is upstream.
What it was asked to guarantee
at-least-once · offset-commit every 5s
The envelope it ran in
32 CPU · 96g memory
sut— data-plane · 32 CPU · 96g
Its arms
- Native
native· realistic · native · defaultthreads 32 · shards 32 · inflight 4 · linger_ms 2000 · max_rows 1048576 - RowBinary
rowbinary· realistic · rowbinarythreads 32 · shards 32 · inflight 4 · linger_ms 500 · max_rows 262144
Where it has been measured
c8gd-metal-24xl-ec2-docker · drain
| Arm | Place | Throughput per core | Throughput | Cores used | Measured |
|---|---|---|---|---|---|
| Native | 1 of 6 | 1.59M range 3.4% | 20.37M range 2.5% | 12.79 range 0.9% | 2026-08-26 · 3 reps |
| RowBinary · shown, not ranked: infra-bound | — of 6 | 1.66M range 0.1% | 10.24M range 4.2% | 6.15 range 4.2% | 2026-08-26 · 3 reps |
Declared deviations
- The framework's writer sets insert_deduplication_token on every sealed batch, so ClickHouse skips content-hash deduplication for this arm's inserts; every other arm's inserts are deduplicated by block content hash. — The token is part of the framework's shipped at-least-once delivery path (rule 1: the system's own API, as any user would run it), but it changes what the arm asks of the shared target and favours the vendor's arm, so it is declared rather than left in a SQL comment. See workload/clickhouse/ddl.sql. · affects server-side
Tell us we got this wrong
If this system is configured badly here, that is a bug in this benchmark rather than a result about Spate, and the pull request that fixes it is the most valuable one this repository can receive. How to send one. The whole configuration is at entrants/spate.
This system also reports CPU per row, Cores, data plane, Peak memory, data plane, Peak charged memory, Throttled, ClickHouse CPU per row, ClickHouse CPU, ClickHouse CPU per written row, ClickHouse CPU wait, Bytes inserted, Rows per insert, Rows written server-side. Those figures are on each arm’s own disclosure in the results table.