Engineering Guides

Practical performance engineering & load testing guides

Technical deep dives into queueing theory, Little’s Law concurrency sizing, p50/p95/p99 tail-latency percentiles, and responsible cloud load testing.

Load Modeling7 min readUpdated 2026-11-06
Understand closed-loop Virtual Users (VU) vs. open-loop Requests Per Second (RPS), Little’s Law concurrency math, think time, and how to avoid Coordinated Omission in API load tests.
  • Virtual Users (VUs) model a closed queueing system where a new request only starts after the previous response finishes plus optional think time.
  • Requests Per Second (RPS) models an open arrival rate where traffic hits your endpoint independent of how fast the backend responds.
  • When backend p99 latency spikes during a fixed-VU test without rate targets, actual throughput drops automatically—masking saturation unless you monitor both RPS and percentiles.
Latency Engineering6 min readUpdated 2026-11-06
Learn why arithmetic average response time hides production outages, how p50, p95, and p99 latency percentiles behave under queueing, and how to set SLA thresholds.
  • Arithmetic mean (average) latency treats a 2,500 ms database stall and a 5 ms Redis cache hit as a comfortable ~29 ms average when 99% of requests hit the cache.
  • p50 (median) measures typical user experience; p95 captures regular slow paths (cache misses, cold queries); p99 exposes tail-latency risks (lock contention, GC pauses, noisy neighbors).
  • In microservice architectures where one page load triggers N downstream API calls, tail latency compounds exponentially.
Platform Architecture6 min readUpdated 2026-11-06
Compare traditional cloud load testing tools like Loader.io with LoadTest: p50/p95/p99 percentile telemetry, fail-closed DNS/HTTP domain verification, and shared team workspaces.
  • Traditional browser-based load testers popularized quick HTTP checks with domain verification, but often rely on coarse average latency metrics and dated single-user workflows.
  • LoadTest combines zero-script dashboard simplicity with p50/p95/p99 percentile telemetry, multi-resolver DNS TXT and HTTP /.well-known verification, and tenant-scoped team workspaces.
  • Fail-closed pre-flight verification ensures domain ownership is re-validated before execution, protecting infrastructure from unauthorized traffic.