Setup a benchmark

[kaushalyap]

Setup a benchmark with other WASM front end frameworks like Yew, Percy

Also add Seed to this benchmark which will allow us to compare Seed with front-end JS frameworks/libraries, currently Yew is there.

Point of benchmarking

• Way to compare with other frameworks/libraries
• To identify places where we could improve performance
• To know about performance regressions

[kaushalyap]

I suggest you to compare Yew with other JS frameworks using this benchmark, I think Seed will be able to do better than Yew or even better than JS frameworks/libraries, since as I read the following in here

Yew is based on stdweb that has a lot of features but also is really heavy-weight. Frameworks like seed on the other hand are based on wasm-bindgen that is focused on (mostly) "zero-cost" interaction with e.g. the. DOM etc.

[MartinKavik]

@seed-rs/core, @kaushalyap Is there a volunteer?

I have VirtualDOM updates in my todo list so it would be nice to compare results before and after refactor. And comparing with other frameworks would be very nice for marketing (or motivation to make it better 😃 ).

[kaushalyap]

@MartinKavik sorry to say currently I do not have enough free time. Hopes someone will do it.

[MartinKavik]

krausest/js-framework-benchmark#696

[MartinKavik]

• Support for element keys has been merged (Optionaly patch nodes by keys. #357), so we should add keyed version to krausest/js-framework-benchmark.

• @1init found this benchmark - https://github.com/ivanceras/sauron-perf. I think it's good enough to write about it in README.

• There is a new example - bunnies - it can be a good demonstration of performance for browser games.

Note: Benchmark updates should be done once Seed 0.7.0 is released.

[Ben-PH]

Now that benchmarks are up, it would be good to update the about section on the webpage.

ctrl-f performance for the relevant part.

It might also be worth having a section on performance. Speaking from my own perspective, I'm coming from a very "low-level and systems" background and have little grasp of frontend considerations. An overview that puts the performance traits of seed into context would be quite useful for me.

[MartinKavik]

@Ben-PH Thanks for feedback/ideas.

I want to rewrite the content of seed-rs.org after the next release, so I'll try to add a section on performance and I'll maybe add it also into the README.

We've decided to not include it in README yet, because the main focus is still on the best public API as possible, so we don't have many benchmarks and Seed isn't very optimized yet (but the speed should be enough for the most use-cases now).

However there is a growing list of possible improvements - #385 (see also comments and don't be afraid to recommend new ideas) and it's on our roadmap.

[Ben-PH]

because the main focus is still on the best public API as possible.

<3