Add NamedPipeTransportOptions.ListenerQueueCount property

[JamesNK]

Background and Motivation

There are performance benefits of multiple listen queues with named pipes. This property allows someone to customize the number.

Proposed API

namespace Microsoft.AspNetCore.Server.Kestrel.Transport.NamedPipes;

public sealed class NamedPipeTransportOptions
{
+    public int ListenerQueueCount { get; set; } = Math.Min(Environment.ProcessorCount, 16);
}

Usage Examples

services.Configure<NamedPipeTransportOptions>(o =>
{
    o.ListenerQueueCount = 2;
});

Alternative Designs

Risks

[ghost]

Thank you for submitting this for API review. This will be reviewed by @dotnet/aspnet-api-review at the next meeting of the ASP.NET Core API Review group. Please ensure you take a look at the API review process documentation and ensure that:

• The PR contains changes to the reference-assembly that describe the API change. Or, you have included a snippet of reference-assembly-style code that illustrates the API change.
• The PR describes the impact to users, both positive (useful new APIs) and negative (breaking changes).
• Someone is assigned to "champion" this change in the meeting, and they understand the impact and design of the change.

[halter73]

API Review Notes

• This is similar to SocketTransportOptions.IOQueueCount. Do we have any better naming suggestions? ListenerLoopCount? AcceptLoopCount? No.
• Namespace looks good.

API Approved as proposed!

namespace Microsoft.AspNetCore.Server.Kestrel.Transport.NamedPipes;

public sealed class NamedPipeTransportOptions
{
+    public int ListenerQueueCount { get; set; } = Math.Min(Environment.ProcessorCount, 16);
}

[adityamandaleeka]

Looks like this was merged in preview 2 (#46259). Closing this issue.