From 2c77e4ab56d665b579d21f2885f151eae1071fee Mon Sep 17 00:00:00 2001
From: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com>
Date: Mon, 17 Oct 2022 16:22:55 -1000
Subject: [PATCH] What's new HTTP/2 perf

---
 aspnetcore/release-notes/aspnetcore-7.0.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/aspnetcore/release-notes/aspnetcore-7.0.md b/aspnetcore/release-notes/aspnetcore-7.0.md
index ae67852028e9..627b3bcdddca 100644
--- a/aspnetcore/release-notes/aspnetcore-7.0.md
+++ b/aspnetcore/release-notes/aspnetcore-7.0.md
@@ -453,7 +453,9 @@ Previously, the HTTP/2 multiplexing implementation relied on a [lock](/dotnet/cs
 
 One place where these improvements can be noticed is in gRPC, a popular RPC framework that uses HTTP/2. Kestrel + gRPC benchmarks show a dramatic improvement:
 
-![Entity diagram](https://user-images.githubusercontent.com/219224/177910504-e93579b4-02e4-4079-8a8c-d9d24857aabf.png)
+![gRPC server streaming performance](https://user-images.githubusercontent.com/219224/177910504-e93579b4-02e4-4079-8a8c-d9d24857aabf.png)
+
+Changes were made in the HTTP/2 frame writing code that improves performance when there are multiple streams trying to write data on a single HTTP/2 connection. We now dispatch TLS work to the thread pool and more quickly release a write lock that other streams can acquire to write their data. The reduction in wait times can yield significant performance improvements in cases where there is contention for this write lock. A gRPC benchmark with 70 streams on a single connection (with TLS) showed a ~15% improvement in requests per second (RPS) with this change.
 
 ### Kestrel performance improvements on high core machines