Application-Level Flow Control for gRPC Bidirectional Streams
Why HTTP/2 flow control is not enough for gRPC bidirectional streams, and how to add credit-based backpressure without OOMing your server.
Loading…
ReadMeFeed / Community knowledge
#flow-control
Real questions. Useful conversations. Find the people who know your stack.
grpcDiagnosing Persistent Flow Control in MariaDB Galera Clusters
Rising wsrep_flow_control_paused counters mean your Galera cluster is throttling itself. Learn how to sample the counters correctly, find the bottleneck node, apply targeted fixes, and know when to escalate.
gRPC HTTP/2 Flow Control: Tuning Window Sizes for High Concurrency Latency
gRPC relies on HTTP/2 flow control to manage data transmission between clients and servers. This mechanism uses a window-based credit system to prevent receivers from being overwhelmed by fast senders. While this ensures stability, the default window sizes may not be optimized for all network topologies, particularly when high concurrency is introduced on a
Identifying HTTP/2 Flow‑Control Bottlenecks in gRPC
When thousands of gRPC streams share a single connection, the HTTP/2 flow‑control window can be exhausted before the application payload is processed. The default per‑stream window is 64 KiB and the connection window is 1 MiB. If many streams compete, the sender must wait for WINDOW_UPDATE frames, adding round‑trip latency that may dominate the overall reque
Connection closed by remote host during SSH channel flow control exhaustion
Large data transfers via scp or sftp can trigger a disconnection when the SSH channel window is exhausted. This behavior is tied to the flow control mechanism defined in RFC 4254, where the sender must wait for window adjustment messages from the receiver before transmitting more data. There is a discrepancy in how different implementations handle window gro
ssh