Explain Non-CPU Latency With Prometheus + proxymock
Diagnose a p95 latency regression that CPU profiling cannot explain using Prometheus histograms, then prove the fix with identical proxymock replays.
Co-founder and CTO of Speedscale, expert in Agentic AI and cloud data warehousing. • 9 posts published
Diagnose a p95 latency regression that CPU profiling cannot explain using Prometheus histograms, then prove the fix with identical proxymock replays.
Find the rare payload that sends a service down a retry path, correlate it to the recorded response, and prove the fix with proxymock replay.
Use Cilium Hubble flow evidence and proxymock replay to prove whether a Kubernetes timeout came from your code, a dependency, or a dropped packet.
Discover endpoints, RED metrics, and traces in an opaque Kubernetes service with OpenTelemetry eBPF Instrumentation, then replay traffic with proxymock.
Diagnose serial N+1 API calls with Tempo and proxymock. Replay recorded traffic, inspect trace windows, and prove a concurrency fix preserves behavior.
Use OpenCost and proxymock to prove Kubernetes rightsizing lowers cost per successful request without hiding behavior or throughput regressions in testing.
Use Grafana Pyroscope and proxymock with an AI coding agent to find a Go CPU hotspot, preserve API behavior, and verify the performance fix.
The best model isn't the smartest — it's whichever should get the next unit of work. Notes from NVIDIA on routing, local models, and the AI factory.
Our v2 release looked clean in HTTP tests until we diffed the SQL workload — an N+1 loop, a startup migration, and 70 ms of extra DB time hiding in plain sight. Here's how to compare two releases without database access.
Choose the desktop proxymock or the hosted cloud trial to get started.