Speedscale

@Speedscaleai

Auto-generate Kubernetes load tests & mocks with real-world traffic. Validate app performance and recreate realistic conditions for devs. 🚀

speedscale.com

Joined May 2020

Speedscale
@Speedscaleai
3h
CPU is at 20%. The service is still painfully slow. That’s because CPU usage doesn’t tell you how long a request spends waiting on a database, network, lock, or dependency. Prometheus shows the CPU isn’t the problem. Proxymock helps replay the request and find where the time
Explain Non-CPU Latency With Prometheus + proxymock | Speedscale
From speedscale.com
Speedscale
@Speedscaleai
Aug 27
A request succeeds. Everything looks fine. Except your service quietly retries it 4 more times. A rare dependency response triggered a retry path that added 420ms of backoff and extra calls. Loki showed us the pattern. proxymock let us replay the exact request and reproduce it
Speedscale
@Speedscaleai
Aug 26
A request times out after 5 seconds, but the dependency’s dashboards are green, and its latency looks normal. So what actually failed? That’s where Hubble helps: it shows what happened to the packets, while proxymock captures and replays the request to prove whether the
Speedscale
@Speedscaleai
Aug 18
Some services are black boxes. No source access, no documentation, and no easy way to know why a request is slow. OpenTelemetry eBPF can give you visibility without changing the application. Then proxymock lets you capture and replay the actual traffic, so you can validate what
Speedscale
@Speedscaleai
Aug 17
Nothing failed. The response was correct. CPU was mostly idle. And one API request still took ~300ms. The trace showed why: 8 inventory calls, running one after another. Tempo found the bottleneck. proxymock showed what input created it. The fix cut latency to ~80 ms, without
Diagnose Serial N+1 API Calls With Tempo + proxymock | Speedscale
From speedscale.com