Skip to content

Commit 386cd35

Browse files
committed
chore: minor update
1 parent 9091f92 commit 386cd35

1 file changed

Lines changed: 12 additions & 4 deletions

File tree

docs/design/scalability-benchmarking.md

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -73,9 +73,11 @@ The work is therefore additive, not a rewrite:
7373
2. **Measure per-request latency in the load generator.** Record submission and
7474
response timestamps per request and compute exact p50/p95/p99 client-side —
7575
the node histograms are too coarse for this
76-
(`mpc_signature_request_response_latency_seconds` has 1 s-wide buckets below
77-
10 s). Still scrape `/metrics` at run end for the internal breakdown
78-
(presignature wait, signing time, store levels).
76+
(`mpc_signature_request_response_latency_seconds` uses exponential buckets
77+
2 s, 3 s, 4.5 s, … — no resolution below 2 s). Note the client-side number is
78+
end-to-end user latency and includes chain inclusion time in both directions;
79+
the node histograms are the MPC-only view. Still scrape `/metrics` at run end
80+
for the internal breakdown (presignature wait, signing time, store levels).
7981
3. **A scenario manifest.** Promote `loadtest-scenarios.sh` to a declarative
8082
manifest (cluster size, load shape, conditions, duration) so a run is fully
8183
described by data and is reproducible.
@@ -177,10 +179,16 @@ numbers, so harness saturation is not mistaken for MPC saturation.
177179
"latency_s": { "p50": 1.8, "p95": 3.2, "p99": 4.1 },
178180
"success_rate": 0.998,
179181
"timeouts": 1,
180-
"presignatures": { "start": 8192, "end": 5120 }
182+
"presignatures": { "start": 8192, "end": 5120 },
183+
"triples": { "start": 32768, "end": 18000 },
184+
"resharing": { "triggered_at": "2026-06-26T00:02:00Z", "recovery_s": 45.0 }
181185
}
182186
```
183187

188+
The `resharing` block (present only for resharing conditions) is derived from
189+
the load generator's throughput-over-time series, which the emitter keeps
190+
in-memory to compute the dip and time-to-recovery.
191+
184192
2. **Prometheus + Grafana — for live/time-series analysis.** Scrape cluster node
185193
`/metrics` into a Prometheus instance (hosted in infra-ops) and visualize in
186194
Grafana for during-run inspection and historical trends. Reuses the existing

0 commit comments

Comments
 (0)