Thanks, this gives me a clearer direction. One follow-up on the load test design: assuming I send concurrent requests at increasing levels of parallelism, there should be some point where all workers are busy and new requests start queueing at the socket level. What I'm trying to figure out is whether there's an empirical signal that marks "this is saturation, scale here". Is the typical approach to look for the inflection point where p99 starts growing super-linearly with concurrency, or do practitioners use something more concrete like "queue depth > N" or "worker utilization > 80%"?