Load Simulation · v0.11.7

A day in the life of a vak deployment

A synthetic 24-hour run of a vak serve --gateway host: a diurnal load curve, injected incidents, and every component reacting live. Watch the tiles, then read the ops charts below — this models the single-node behavior the concurrency review describes: parallel across sessions, bounded by the CorePool, protected by retries, the circuit breaker, and the rate limiter.

00:00
night · quiet
Nominal — steady state

Throughput now

0/min
runs completed

Latency p95

0ms
p50 0 ms

Active cores

1/5
pool: 1 pinned + 4

Queue depth

0
runs waiting

Provider circuit

CLOSED
retries 0/min

Surfaces & ingress

CLIvak exec
0/min
local, no network
DesktopTauri
0 sess
loopback + token
Slackbridge
0/min
/gateway/inbound
Discordbridge
0/min
/gateway/inbound
Telegrambridge
0/min
/gateway/inbound

Core, guards & providers

Rate limiterper-IP
0 429/min
admitting
CorePoolcap 4+1
1 warm
Runtimesessions
0 active
0 queued
LLM providersroute ladder
0 calls/min
primary healthy
Sandboxlandlock
0 denied
enforcing · fail-closed
Operations — full day
demand completed p50 · p95 cores · queue 429/failed · retries · auto-deny