aspnetcore/test/Microsoft.AspNetCore.Server...
David Fowler 1094cc0670 Use StreamSocketOutput for writing benchmarks (#1507)
- Use StreamSocketOutput with a null stream to get a
better picture of what actual performance looks like
2017-03-18 13:20:07 -07:00
..
configs Clean up benchmarks (#1487) 2017-03-12 22:52:24 -07:00
DotSegmentRemovalBenchmark.cs Span-based RemoveDotSegments (#1448) 2017-03-17 14:42:13 -07:00
ErrorUtilities.cs Clean up benchmarks (#1487) 2017-03-12 22:52:24 -07:00
FrameParsingOverheadBenchmark.cs Clean up benchmarks (#1487) 2017-03-12 22:52:24 -07:00
FrameWritingBenchmark.cs Clean up benchmarks (#1487) 2017-03-12 22:52:24 -07:00
KestrelHttpParserBenchmark.cs Clean up benchmarks (#1487) 2017-03-12 22:52:24 -07:00
KnownStringsBenchmark.cs Clean up benchmarks (#1487) 2017-03-12 22:52:24 -07:00
Microsoft.AspNetCore.Server.Kestrel.Performance.csproj Re-add .NET Framework to tests and other cleanup (#1494) 2017-03-14 11:02:49 -07:00
PipeThroughputBenchmark.cs Clean up benchmarks (#1487) 2017-03-12 22:52:24 -07:00
Program.cs
Readme.md
RequestParsingBenchmark.cs Clean up benchmarks (#1487) 2017-03-12 22:52:24 -07:00
RequestParsingData.cs Clean up benchmarks (#1487) 2017-03-12 22:52:24 -07:00
ResponseHeaderCollectionBenchmark.cs Speed up WritableBuffer.WriteXxx (#1504) 2017-03-18 12:25:10 -07:00
ResponseHeadersWritingBenchmark.cs Use StreamSocketOutput for writing benchmarks (#1507) 2017-03-18 13:20:07 -07:00
WritableBufferExtensions.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