dotWasmBenchmark icon indicating copy to clipboard operation
dotWasmBenchmark copied to clipboard

Any value in re-running DotNet.Wasm?

Open DierkDroth opened this issue 7 years ago • 2 comments

@stefan-schweiger I was wondering if you would see value in re-running the DotNet.Wasm tests using latest Blazor + Browser version and if you had the bandwidth to do so?

DierkDroth avatar Dec 10 '18 16:12 DierkDroth

I redid a slightly more advanced benchmark with newer versions here.

My conclusion overall would still be client-side Blazor (without AOT) will never get below being 10-20x slower. More realistically not even below 30x slower.

There have been some improvements I'm aware of since my last Benchmark, but just from a quick retry it's only in the 2-3% range.

EDIT: You should also know that Chrome has a huge performance regression (about 50-100% slower) somewhere between version 65 and 69, which as far as I'm aware still hasn't been addressed in the latest version.

stefan-schweiger avatar Dec 10 '18 17:12 stefan-schweiger

Thanks for sharing

DierkDroth avatar Dec 10 '18 17:12 DierkDroth