aspnetcore/benchmarks/Kestrel.Performance
Stephen Halter 668f8e3b4b
Lazily allocate protocol-specific connection objects (#2190)
* Refactor Http[12]?Connection
2017-12-04 15:59:12 -08:00
..
Mocks
configs
DotSegmentRemovalBenchmark.cs Validate benchmarks (#2126) 2017-10-23 09:51:00 -07:00
ErrorUtilities.cs
Http1ConnectionParsingOverheadBenchmark.cs Lazily allocate protocol-specific connection objects (#2190) 2017-12-04 15:59:12 -08:00
Http1WritingBenchmark.cs Lazily allocate protocol-specific connection objects (#2190) 2017-12-04 15:59:12 -08:00
HttpParserBenchmark.cs
HttpProtocolFeatureCollection.cs Lazily allocate protocol-specific connection objects (#2190) 2017-12-04 15:59:12 -08:00
Kestrel.Performance.csproj
KnownStringsBenchmark.cs
PipeThroughputBenchmark.cs
README.md
RequestParsingBenchmark.cs Lazily allocate protocol-specific connection objects (#2190) 2017-12-04 15:59:12 -08:00
RequestParsingData.cs
ResponseHeaderCollectionBenchmark.cs Lazily allocate protocol-specific connection objects (#2190) 2017-12-04 15:59:12 -08:00
ResponseHeadersWritingBenchmark.cs Lazily allocate protocol-specific connection objects (#2190) 2017-12-04 15:59:12 -08: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 -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