I can really feel the swing back to Firefox happening like the switch to Chrome back 5-7 years ago.
Go Firefox!!!
p.s. Great work on Firefox OS too!
Spidermonkey has passed V8 on Octane performance
11–20 of 338 posts
Re: Spidermonkey has passed V8 on Octane performance
#12Firefox is awesome and I love it, but my one complaint after all these years is that I have to restart the browser every day. It's not the end of the world, but it's still frustrating, especially when I'm in the throes of debugging or important research. Over the course of a day, the browser becomes unresponsive and CPU usage idles at 10-15%. Restarting with the same tabs brings it down to 0%. Yes, I know, disable ad…
It's not threading, it's processes that's coming up. I would be surprised if each tab didn't already have its own thread, because eg. multiple tabs can load at the same time...
And umm, not sure what I'm doing differently but I usually keep Firefox open for weeks at a time and have no issues. Though I cut back a bit on keeping tabs open, I used to keep like 60-80 tabs open all the time but now I usually clean up when I'm done with something (more to reduce cognitive overhead than resource utilization).
Re: Spidermonkey has passed V8 on Octane performance
#13Check out http://arewefastyet.com/ (the website mentioned in the article), which tracks javascript engine performance. Spidermonkey is faster than v8 and Safari's JSC on all three popular javascript benchmarks [1]
[1] Octane (google's benchmark), Sunspider (Apple/Webkit's benchmark), and Kraken (Mozilla's benchmark).
Re: Spidermonkey has passed V8 on Octane performance
#14Firefox is awesome and I love it, but my one complaint after all these years is that I have to restart the browser every day. It's not the end of the world, but it's still frustrating, especially when I'm in the throes of debugging or important research. Over the course of a day, the browser becomes unresponsive and CPU usage idles at 10-15%. Restarting with the same tabs brings it down to 0%. Yes, I know, disable ad…
Genuinely curious if this is a common use case or not. I personally close chrome maybe half a dozen times an hour.
Re: Spidermonkey has passed V8 on Octane performance
#15"This puts us in a position of strength, so we can say "these benchmarks are not very interesting; let's talk about other benchmarks (e.g. asm.js-related) and language features" without being accused of being sore losers."
But are asmjs benchmarks interesting? They are not representative of the vast majority of real-world JS, so wouldn't an asmjs-laden benchmark suite really be a case of optimizing for your own set of benchmarks, tuned to your own idiomatic-JS?
But anyway, congrats on the achievement. I like the fact that V8, JSC, and FF performance are converging. If the performance differential is too great, it creates additional headaches for the developer targeting a certain level of efficiency.
Re: Spidermonkey has passed V8 on Octane performance
#16You know, I just don't know who to believe these days when it comes to browser benchmarks. All browser vendors pretty much say they lead all browsers in _something_. Honestly, I don't even know what all these benchmarks mean most of the time.
The point in this one is SpiderMonkey is beating V8 in the benchmark designed such that V8 wins on it.
Re: Spidermonkey has passed V8 on Octane performance
#17As soon as firefox gets per process tabs in stable I'll switch back, I really want to switch from chrome but that's a deal killer for me.
Re: Spidermonkey has passed V8 on Octane performance
#18Firefox is awesome and I love it, but my one complaint after all these years is that I have to restart the browser every day. It's not the end of the world, but it's still frustrating, especially when I'm in the throes of debugging or important research. Over the course of a day, the browser becomes unresponsive and CPU usage idles at 10-15%. Restarting with the same tabs brings it down to 0%. Yes, I know, disable ad…
It's not threading, it's processes that's coming up. I would be surprised if each tab didn't already have its own thread, because eg. multiple tabs can load at the same time... And umm, not sure what I'm doing differently but I usually keep Firefox open for weeks at a time and have no issues. Though I cut back a bit on keeping tabs open, I used to keep like 60-80 tabs open all the time but now I usually clean up when…
All tabs are on the same thread in Firefox. Tabs appear to load concurrently only because io is async.
Re: Spidermonkey has passed V8 on Octane performance
#19Check out http://arewefastyet.com/ (the website mentioned in the article), which tracks javascript engine performance. Spidermonkey is faster than v8 and Safari's JSC on all three popular javascript benchmarks [1] [1] Octane (google's benchmark), Sunspider (Apple/Webkit's benchmark), and Kraken (Mozilla's benchmark).
Is there a reason they don't have the new Safari 8 FTLJIT in those numbers? JSC (Java Script Core?) was Safari 7 wasn't it?
Re: Spidermonkey has passed V8 on Octane performance
#20Check out http://arewefastyet.com/ (the website mentioned in the article), which tracks javascript engine performance. Spidermonkey is faster than v8 and Safari's JSC on all three popular javascript benchmarks [1] [1] Octane (google's benchmark), Sunspider (Apple/Webkit's benchmark), and Kraken (Mozilla's benchmark).
Is there a reason they don't have the new Safari 8 FTLJIT in those numbers? JSC (Java Script Core?) was Safari 7 wasn't it?
According to [1]:
"Last week I asked for benchmarks of the new JavascriptCore Fourth Tier LLVM JIT. Arewefastyet from Mozilla now includes such results. FTLJIT does particularly well on asm.js examples."
You can see JSC performing better than chrome on the asm.js benchmarks: http://arewefastyet.com/#machine=12&view=breakdown&suite=asm...
[1] http://blog.llvm.org/2014/05/llvm-weekly-19-may-12th-2014.ht...