← All performance runs

Regression

delivery · 2026-09-13 09:30 UTC

20260913T093040Z-iv27ma

3 scenario(s) regressed against the baseline; 2 scenario(s) missed their SLO. Worst: entitlement-check at p95 284ms against a 210ms baseline and a 256ms (floor 181ms + 75ms) SLO.

Citing this run

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

https://monetizekit.github.io/performance/run/20260913T093040Z-iv27ma.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 248ms 181ms 270ms 220ms +13% 250ms, informational 61 0.00% informational
platform-baseline 228ms 175ms 354ms 199ms +15% 400ms, informational 301 0.00% informational
entitlement-check 284ms 216ms 366ms 210ms +36% 256ms (floor 181ms + 75ms) 601 0.00% regressed
entitlement-batch 286ms 227ms 419ms 267ms +7% 331ms (floor 181ms + 150ms) 601 0.00% pass
customer-reads 301ms 226ms 511ms 250ms +21% 381ms (floor 181ms + 200ms) 601 0.00% regressed
catalog-reads 271ms 208ms 370ms 244ms +11% 331ms (floor 181ms + 150ms) 601 0.00% pass
usage-ingest 283ms 214ms 376ms 239ms +18% 331ms (floor 181ms + 150ms) 601 0.00% pass
usage-ingest-backdated 277ms 212ms 351ms 226ms +23% 331ms (floor 181ms + 150ms) 600 0.00% regressed
usage-ingest-batch 843ms 665ms 1.30s 847ms -0% 1681ms (floor 181ms + 1500ms) 101 16.83% 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 8 comparable run(s)

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