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

Missing performance benchmark results #48

Closed
michax opened this issue Nov 30, 2016 · 5 comments
Closed

Missing performance benchmark results #48

michax opened this issue Nov 30, 2016 · 5 comments

Comments

@michax
Copy link

michax commented Nov 30, 2016

Could you include your performance benchmark results that you are talking about in following blog post?
https://svelte.technology/blog/frameworks-without-the-framework/

You've linked to https://github.com/krausest/js-framework-benchmark, but it's missing test results for your solution.

@guzart
Copy link
Contributor

guzart commented Nov 30, 2016

There's a PR waiting for merge

krausest/js-framework-benchmark#87

@Victorystick
Copy link

It's been merged!

@michax michax closed this as completed Dec 10, 2016
@evs-chris
Copy link
Contributor

I think the next round is getting ready run if someone has a bit of time to add a svelte keyed flavour to the benchmarks.

@Rich-Harris
Copy link
Member

Thanks for the heads-up @evs-chris — have opened krausest/js-framework-benchmark#181. Will be interesting to see how our new keyed updates implementation fares (since actually running the benchmarks locally is next to impossible, thanks to all the error-producing crap and absurd build times in some of the more... mainstream frameworks)

@leeoniya
Copy link

leeoniya commented May 17, 2017

(since actually running the benchmarks locally is next to impossible, thanks to all the error-producing crap and absurd build times in some of the more... mainstream frameworks)

you don't have to run the whole thing. i certainly don't.

you should do npm install && npm run build-prod in webdriver-ts and run npm install && npm run build-prod within each framework you wanna bench (prolly just vanillajs is enough to get the baseline).

npm start to run the http server.

then do npm run selenium -- --framework vanilla svelte && npm run results

you may have to tweak /webdriver-ts/src/common.ts. i also hardcode the css in each index.html to point to /css/useMinimalCss.css in all the benches i run.

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

6 participants