aspnetcore/benchmarks/Microsoft.AspNetCore.Blazor...
Steve Sanderson e71db85149 Handle overlapping events (#1655)
* Add failing unit test to demonstrate overlapping events bug

* Handle overlapping events

* Make RemoteRenderer.UpdateDisplay's return task not complete until client sends explict ACK

* CR: Rename UpdateDisplay to UpdateDisplayAsync

* CR: Fix namespace

* CR: Catch synchronous SendAsync exceptions (if they can happen)
2018-11-13 12:08:08 +00:00
..
AssemblyInfo.cs
Microsoft.AspNetCore.Blazor.Performance.csproj
Program.cs
RenderTreeDiffBuilderBenchmark.cs Handle overlapping events (#1655) 2018-11-13 12:08:08 +00:00
readme.md

readme.md

Benchmarks

Instructions

Run All Benchmarks

To run all use * as parameter

dotnet run -c Release -- *

Interactive Mode

To see the list of benchmarks run (and choose interactively):

dotnet run -c Release

Run Specific Benchmark

To run a specific benchmark add it as parameter

dotnet run -c Release -- <benchmark_name>

Troubleshooting

The runner will create logs in the <project>\BenchmarkDotNet.Artifacts directory. That should include a lot more information than what gets printed to the console.

Results

Also in the <project>\BenchmarkDotNet.Artifacts\results directive you'll find some markdown-formatted tables suitable for posting in a github comment.