Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any value in re-running DotNet.Wasm? #3

Open
DierkDroth opened this issue Dec 10, 2018 · 2 comments
Open

Any value in re-running DotNet.Wasm? #3

DierkDroth opened this issue Dec 10, 2018 · 2 comments

Comments

@DierkDroth
Copy link

@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?

@stefan-schweiger
Copy link
Owner

stefan-schweiger commented Dec 10, 2018

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.

@DierkDroth
Copy link
Author

Thanks for sharing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants