← All performance runs

Regression

delivery · 2026-09-15 09:24 UTC

20260915T092419Z-4cvntl

1 scenario(s) regressed against the baseline; 2 scenario(s) missed their SLO. Worst: entitlement-check at p95 289ms against a 210ms baseline and a 252ms (floor 177ms + 75ms) SLO.

Citing this run

MonetizeKit delivery, 2026-09-15, build 0952c11: entitlement-batch p95 285ms, measured at up to 100 requests/minute against dataset v2 with workload w2.

https://monetizekit.github.io/performance/run/20260915T092419Z-4cvntl.html

This URL is permanent. Run ids are timestamped and never reused, so a later run cannot change what this page says.

Scenarios

Scenario p95 p50 p99 Baseline Δ SLO Requests Errors Verdict
network-floor 236ms 177ms 295ms 217ms +9% 250ms, informational 61 0.00% informational
platform-baseline 246ms 172ms 367ms 194ms +26% 400ms, informational 301 0.00% informational
entitlement-check 289ms 215ms 388ms 210ms +38% 252ms (floor 177ms + 75ms) 600 0.00% regressed
entitlement-batch 285ms 221ms 378ms 258ms +11% 327ms (floor 177ms + 150ms) 601 0.00% pass
customer-reads 289ms 220ms 438ms 260ms +11% 377ms (floor 177ms + 200ms) 600 0.00% pass
catalog-reads 265ms 205ms 367ms 238ms +11% 327ms (floor 177ms + 150ms) 601 0.00% pass
usage-ingest 271ms 209ms 328ms 239ms +13% 327ms (floor 177ms + 150ms) 600 0.00% pass
usage-ingest-backdated 275ms 209ms 395ms 232ms +19% 327ms (floor 177ms + 150ms) 601 0.00% pass
usage-ingest-batch 902ms 654ms 1.34s 822ms +10% 1677ms (floor 177ms + 1500ms) 101 8.91% slo-breach

What shipped since the last measured build

Nothing: the same build was measured as last time, so any movement here is environmental rather than ours.

Conditions

Build0952c11317c357f78b5b374baf6dd077e65e1feb
Targethttps://app.monetizekit.delivery
Datasetv2
Workloadw2 · k6 1.4.0
Rate limit100 requests/minute
Triggerschedule
Duration4333s
Baselinemedian of 10 comparable run(s)

Raw Run Document (JSON) · Machine-written by packages/pipeline/src/persist.ts. Append-only: this run is never rewritten.