aspnetcore/test/Microsoft.AspNetCore.Server...
Nate McMaster c343628926 Implement max connection limits
- Added new options to allow configuring the maximum number of concurrent connections and upgraded connections.
- `KestrelServerLimits.MaxConcurrentConnections` defaults unlimited.
- `KestrelServerLimits.MaxConcurrentUpgradedConnections` defaults to unlimited.
- Calls to IHttpUpgradeFeature.UpgradeAsync() will throw when the MaxConcurrentUpgradedConnections limit has been reached.
- Kestrel will close new connections without response when MaxConcurrentConnections is reached.
2017-05-26 12:27:48 -07:00
..
Mocks Implement max connection limits 2017-05-26 12:27:48 -07:00
configs
DotSegmentRemovalBenchmark.cs
ErrorUtilities.cs
FrameFeatureCollection.cs Fix broken microbenchmarks (#1861). 2017-05-25 16:01:17 -07:00
FrameParsingOverheadBenchmark.cs Fix broken microbenchmarks (#1861). 2017-05-25 16:01:17 -07:00
FrameWritingBenchmark.cs Fix broken microbenchmarks (#1861). 2017-05-25 16:01:17 -07:00
KestrelHttpParserBenchmark.cs
KnownStringsBenchmark.cs
Microsoft.AspNetCore.Server.Kestrel.Performance.csproj
PipeThroughputBenchmark.cs
Program.cs
Readme.md
RequestParsingBenchmark.cs Fix broken microbenchmarks (#1861). 2017-05-25 16:01:17 -07:00
RequestParsingData.cs
ResponseHeaderCollectionBenchmark.cs Fix broken microbenchmarks (#1861). 2017-05-25 16:01:17 -07:00
ResponseHeadersWritingBenchmark.cs Fix broken microbenchmarks (#1861). 2017-05-25 16:01:17 -07:00
StringUtilitiesBenchmark.cs

Readme.md

Compile the solution in Release mode (so Kestrel is available in release)

To run a specific benchmark add it as parameter

dotnet run -c Release RequestParsing

To run all use All as parameter

dotnet run -c Release All

Using no parameter will list all available benchmarks