This site is under active development. Some services and pages may not be fully ready yet.

All documentation

Performance Testing

k6 load test scenarios, concurrency baselines, and performance benchmarks.

Load testing is about finding the point where the queue stops keeping up, not about a headline requests-per-second figure. Almost everything expensive on this platform is asynchronous.

Worth measuring

  • Client portal browsing — read-heavy, cache-sensitive.
  • Checkout through to invoice creation — the write path that matters commercially.
  • Provisioning throughput — how many jobs per minute the worker clears against a real panel.
  • Scheduled billing on a realistic dataset — the daily run is the heaviest scheduled work.

Reading the results

Watch queue depth over time rather than response latency alone. If depth grows for the duration of the test, the worker is the bottleneck: raise QUEUE_WORKER_DEFAULT_PROCS or move provisioning to its own tier before touching anything else.

NoteNever point a load test at a live panel. Provisioning drivers create real accounts on real servers.