Raising grpc.max_concurrent_streams above 100: latency spikes under bursty load on a single HTTP/2 connection
Context A gRPC service currently runs with the default concurrent stream limit (100 in many implementations) over a single HTTP/2 connection per client. Under bursty concurrency, p99 latency rises sharply even though sequential-request benchmarks show flat, low latency. The plan under consideration is to raise grpc.max_concurrent_streams rather than add more