Testing @bmeurer's benchmark:
> 5.21 runs/sec ±5% (babel-standalone v6.26.0)
> 8.58 runs/sec ±8% (@babel/standalone v7.0.0-beta.31)
-
Show this thread
-
looks like 60% faster overall, seems like 45% just from the changes we made in v7 initially and like 15% from
@bmeurer quick PRs!2 replies 4 retweets 22 likesShow this thread -
we have a label for these PRs/issues if anyone is interested https://github.com/babel/babel/pulls?utf8=%E2%9C%93&q=label%3A%22area%3A%20perf%22%20 …pic.twitter.com/uMvN3mlvFy
1 reply 0 retweets 2 likesShow this thread -
should write up a guide later on how to setup the benchmark running with `d8 --runtime-call-stats dist/run.js` (basically just building v8)
1 reply 0 retweets 2 likesShow this thread -
-
Replying to @bmeurer
I basically followed https://github.com/v8/v8/wiki/Building-from-Source … but seems like came across issues depending on your OS version
2 replies 0 retweets 4 likes -
Was about to point you there :) Which issues did you run into? Btw, we’re working on hosting pre-built d8 binaries: https://bugs.chromium.org/p/v8/issues/detail?id=5918 …
2 replies 1 retweet 4 likes -
I had an issue since I was on El captain with an older version of osx xcode libs which I had to manually update
1 reply 0 retweets 1 like -
Said I needed at least MacOSX10.12.sdk, and I couldn't update it via the store so did it on GitHub but that failed + https://bugs.chromium.org/p/v8/issues/detail?id=5994 …
1 reply 0 retweets 1 like -
Found a link to new xcode and that finally worked so I'll just say prebuilt sounds good too
2 replies 0 retweets 2 likes
Starting to make this less frustrating by adding helpful error messages: https://chromium-review.googlesource.com/c/chromium/src/+/758651 … (This affects both Chromium and V8.)
-
-
(Wouldn’t have helped in your specific case, but will help others.)
1 reply 0 retweets 2 likes -
yeah for sure, I had to debug some crazy stuff but anything for easier install is great for all!
0 replies 0 retweets 1 like
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.
