Profile HTTP/2 and identify hotspots

[shirhatti]

Scenarios:

• TechEmpower plaintext but over HTTP/2
• Basic POST. Request is text/plain string of name. Reply is text/plain "Hello " + name
• Basic gRPC. See gRPC tutorial
• Streaming gRPC. The same as the basic gRPC but the server streaming multiple messages
• Stream per connection vs multiple streams on one connection
• H2 vs H2C
• Kestrel and IIS HTTP/2 performance
• Server streaming

Output:

• Create new HTTP2 issues with screenshots/traces/numbers from profile

[davidfowl]

This is an old benchmark from preview4 #6567

[jkotalik]

@JamesNK is #13752 sufficient for the info covered here?

[BrennanConroy]

@JamesNK Any remaining work? And is it for Next Sprint or Backlog?

[JamesNK]

Backlog

[JamesNK]

I think there are improvements still to be made to writing frames on busy multiplexed connections but not a priority for 6.0

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[JamesNK]

I'm going to close this. With .NET 7 we've hit the known remaining hotspots: upload flow control, and download concurrency.

In the future, we can have individual issues for future HTTP/2 perf hotspots.