From a86bda1fc386e1dd40af40c11360ec16dab468c5 Mon Sep 17 00:00:00 2001 From: Alaa Masoud Date: Sat, 28 Sep 2024 23:41:58 +0300 Subject: [PATCH] Fix incorrect Kestrel's default stream window size According to https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.server.kestrel.core.http2limits.initialstreamwindowsize?view=aspnetcore-8.0#microsoft-aspnetcore-server-kestrel-core-http2limits-initialstreamwindowsize, the default size is 768 KB not 96 KB --- aspnetcore/grpc/performance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/grpc/performance.md b/aspnetcore/grpc/performance.md index ea0f89782d..0285105a69 100644 --- a/aspnetcore/grpc/performance.md +++ b/aspnetcore/grpc/performance.md @@ -185,7 +185,7 @@ builder.WebHost.ConfigureKestrel(options => Recommendations: -* If a gRPC service often receives messages larger than 96 KB, Kestrel's default stream window size, then consider increasing the connection and stream window size. +* If a gRPC service often receives messages larger than 768 KB, Kestrel's default stream window size, then consider increasing the connection and stream window size. * The connection window size should always be equal to or greater than the stream window size. A stream is part of the connection, and the sender is limited by both. For more information about how flow control works, see [HTTP/2 Flow Control (blog post)](https://medium.com/coderscorner/http-2-flow-control-77e54f7fd518).