* Decouple connection objects from the server (#2535) - Making progress towards being able to use the connection objects on the client side. * Wait for input writer to complete before calling OnConnectionClosed (#2566) * Wait for the ConnectionClosed token to stop tracking connections (#2574) - The prior strategy of waiting for the pipe completed callbacks doesn't work because blocks are returned to the memory pool after the callbacks are fired. * Consistently handle connection resets (#2547) * Provide better connection abort exceptions and logs * void IConnectionDispatcher.OnConnection |
||
|---|---|---|
| .. | ||
| Mocks | ||
| AsciiBytesToStringBenchmark.cs | ||
| AssemblyInfo.cs | ||
| DotSegmentRemovalBenchmark.cs | ||
| ErrorUtilities.cs | ||
| Http1ConnectionBenchmark.cs | ||
| Http1ConnectionParsingOverheadBenchmark.cs | ||
| Http1WritingBenchmark.cs | ||
| HttpParserBenchmark.cs | ||
| HttpProtocolFeatureCollection.cs | ||
| InMemoryTransportBenchmark.cs | ||
| Kestrel.Performance.csproj | ||
| KnownStringsBenchmark.cs | ||
| PipeThroughputBenchmark.cs | ||
| README.md | ||
| RequestParsingBenchmark.cs | ||
| RequestParsingData.cs | ||
| ResponseHeaderCollectionBenchmark.cs | ||
| ResponseHeadersWritingBenchmark.cs | ||
| 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 -f netcoreapp2.0 -c Release RequestParsing
To run all use All as parameter
dotnet run -f netcoreapp2.0 -c Release All
Using no parameter will list all available benchmarks