ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
gRPC unary RPC latency spikes only when multiple calls run concurrently on a single HTTP/2 connection. The shared connection limits the HTTP/2 flow‑control window, enforces a max concurrent streams setting, and subjects all streams to TCP head‑of‑line blocking from packet loss. Uncertainty remains whether the delay stems from application buffer draining, flo
When a fetch request is aborted via an AbortController in Firefox, the Necko networking component initiates a cancellation sequence. While the browser-side promise rejects immediately, the behavior of the underlying HTTP/2 stream remains inconsistent regarding the timing of resource cleanup. n Specifically, in high-latency environments, there is uncertainty
Goal Minimize the amount of data transferred for a single page that receives a small number of visits per month. Constraints & Uncertainty Rollup removes unused ES module exports by default, but the extent of size reduction depends on side‑effect annotations and the presence of dynamic imports. Manual chunks can split the bundle into route‑specific piece
Determine whether Envoy interprets an incoming HTTP/2 CANCEL frame as a request deadline expiration that should be forwarded to the upstream via the x‑envoy‑upstream‑rq‑timeout header and result in a graceful connection shutdown aligned with the route’s idle timeout and the current xDS lease. Observations suggest that Envoy v1.22 handles CANCEL frames on a b
Goal Determine why a production workload intermittently hits 429 or 502 errors during bulk Graph API calls, despite retry logic and documented rate‑limit headers remaining within limits. Context The Java SDK (v12.x+) defaults to a 50‑connection HTTP/1.1 pool per host. HTTP/2 is optional and can be enabled with enableHttp2(true) . The SDK exposes maxConnectio
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
grpc
firefox
rollup