Fields - http2MaxConcurrentStreams :: Word32
- http2StreamWindowSize :: Word32
- http2ConnectionWindowSize :: Word32
Connection window size This value is broadcast via a WINDOW_UDPATE frame at the beginning of
a new connection. If the consumed window space of all streams exceeds this value, the
sender will stop sending data. Therefore, if this value is less than
http2MaxConcurrentStreams * http2StreamWindowSizeserverOverrideNumberOfWorkers for the server.
See https://github.com/kazu-yamamoto/network-control/pull/4 for more
information. - http2TcpNoDelay :: Bool
Enable TCP_NODELAY Send out TCP segments as soon as possible, even if there is only a
small amount of data. When TCP_NODELAY is NOT set, the TCP implementation will wait to
send a TCP segment to the receiving peer until either (1) there is
enough data to fill a certain minimum segment size or (2) we receive an
ACK from the receiving peer for data we sent previously. This adds a
network roundtrip delay to every RPC message we want to send (to
receive the ACK). If the peer uses TCP delayed acknowledgement, which
will typically be the case, then this delay will increase further
still; default for delayed acknowledgement is 40ms, thus resulting in a
theoretical maximum of 25 RPCs/sec. We therefore enable TCP_NODELAY by default, so that data is sent to the
peer as soon as we have an entire gRPC message serialized and ready to
send (we send the data to the TCP layer only once an entire message is
written, or the http2 write buffer is full). Turning this off could improve throughput, as fewer TCP segments will
be needed, but you probably only want to do this if you send very few
very large RPC messages. In gRPC this is anyway discouraged, because
gRPC messages do not support incremental (de)serialization; if you need
to send large amounts of data, it is preferable to split these into
many, smaller, gRPC messages; this also gives the application the
possibility of reporting on data transmission progress. TL;DR: leave this at the default unless you know what you are doing. - http2TcpAbortiveClose :: Bool
Set SO_LINGER to a value of 0 Instead of following the normal shutdown sequence to close the TCP
connection, this will just send a RST packet and immediately discard
the connection, freeing the local port. This should not be enabled in the vast majority of cases. It is only
useful in specific scenarios, such as stress testing, where resource
(e.g. port) exhaustion is a greater concern than protocol adherence.
Even in such scenarios scenarios, it probably only makes sense to
enable this option on the client since they will be using a new
ephemeral port for each connection (unlike the server). TL;DR: leave this at the default unless you know what you are doing. - http2OverridePingRateLimit :: Maybe Int
Ping rate limit This setting is specific to the http2
package's implementation of
the HTTP/2 specification. In particular, the library imposes a ping
rate limit as a security measure against
CVE-2019-9512. By
default (as of version 5.1.2) it sets this limit at 10 pings/second. If
you find yourself being disconnected from a gRPC peer because that peer
is sending too many pings (you will see an
EnhanceYourCalm
exception, corresponding to the
ENHANCE_YOUR_CALM
HTTP/2 error code), you may wish to increase this limit. If you are
connecting to a peer that you trust, you can set this limit to
maxBound (effectively turning off protection against ping flooding). - http2OverrideEmptyFrameRateLimit :: Maybe Int
Empty DATA frame rate limit This setting is specific to the http2
package's implementation of
the HTTP/2 specification. In particular, the library imposes a rate
limit for empty DATA frames as a security measure against
CVE-2019-9518. By
default, it sets this limit at 4 frames/second. If you find yourself
being disconnected from a gRPC peer because that peer is sending too
many empty DATA frames (you will see an
EnhanceYourCalm
exception, corresponding to the
ENHANCE_YOUR_CALM
HTTP/2 error code), you may wish to increase this limit. If you are
connecting to a peer that you trust, you can set this limit to
maxBound (effectively turning off protection against empty DATA frame
flooding). - http2OverrideSettingsRateLimit :: Maybe Int
SETTINGS frame rate limit This setting is specific to the http2
package's implementation of
the HTTP/2 specification. In particular, the library imposes a rate
limit for SETTINGS frames as a security measure against
CVE-2019-9515. By
default, it sets this limit at 4 frames/second. If you find yourself
being disconnected from a gRPC peer because that peer is sending too
many SETTINGS frames (you will see an
EnhanceYourCalm
exception, corresponding to the
ENHANCE_YOUR_CALM
HTTP/2 error code), you may wish to increase this limit. If you are
connecting to a peer that you trust, you can set this limit to
maxBound (effectively turning off protection against SETTINGS frame
flooding). - http2OverrideRstRateLimit :: Maybe Int
Reset (RST) frame rate limit This setting is specific to the http2
package's implementation of
the HTTP/2 specification. In particular, the library imposes a rate
limit for RST frames as a security measure against
CVE-2023-44487. By
default, it sets this limit at 4 frames/second. If you find yourself
being disconnected from a gRPC peer because that peer is sending too
many empty RST frames (you will see an
EnhanceYourCalm
exception, corresponding to the
ENHANCE_YOUR_CALM
HTTP/2 error code), you may wish to increase this limit. If you are
connecting to a peer that you trust, you can set this limit to
maxBound (effectively turning off protection against RST frame
flooding).
|