aspnetcore/test/Microsoft.AspNetCore.Server...
Pavel Krymets 07cbf7faa9 Use pipelines for SocketOutput
- Changed socket output to be based on pipelines
- Changed connection filter glue to be based on pipelines
- Codegen that used `MemoryPoolIterator` for output now uses `WritableBuffer`
- Made `UvWriteReq` async/await friendly with `LibuvAwaitable<T>`
- Deleted MemoryPool and friends
2017-03-18 00:26:00 -07:00
..
configs
DotSegmentRemovalBenchmark.cs Span-based RemoveDotSegments (#1448) 2017-03-17 14:42:13 -07:00
ErrorUtilities.cs
FrameParsingOverheadBenchmark.cs
FrameWritingBenchmark.cs
KestrelHttpParserBenchmark.cs
KnownStringsBenchmark.cs
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
Program.cs
Readme.md
RequestParsingBenchmark.cs
RequestParsingData.cs
ResponseHeadersBenchmark.cs Use pipelines for SocketOutput 2017-03-18 00:26:00 -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