Spidermonkey has passed V8 on Octane performance
robert.ocallahan.org
Spidermonkey has passed V8 on Octane performance
1–10 of 338 posts
Re: Spidermonkey has passed V8 on Octane performance
#2Good job Mozilla!
Re: Spidermonkey has passed V8 on Octane performance
#3Just about 5 years ago, it was looking to me like it was the end of Firefox. It was Chrome all the way. New features were coming out one after another. Faster rendering. Safe process isolation for each tab. Looked better.
But I just switched back last month. It happened kind of randomly. Saw an announcement of a new release ( 33, I think ), downloaded, re-imported my bookmarks from Chrome and just kind of kept using it instead of Chrome since then.
I like how the tabs look also I think it feels lighter and snappier on my (now old-ish) laptop.
Re: Spidermonkey has passed V8 on Octane performance
#4Re: Spidermonkey has passed V8 on Octane performance
#5Over 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 addons, blah blah...doesn't work for me. Same problem.
I'm really looking forward to the new threading model coming up. I have a feeling that once each tab has a thread, things like this will be much more self-repairing. It's not always easy to kill a rogue execution path in an event loop, but killing a thread is pretty straightforward =].
Also, congrats on the firefox team for really taking performance seriously.
Re: Spidermonkey has passed V8 on Octane performance
#6Re: Spidermonkey has passed V8 on Octane performance
#7Re: Spidermonkey has passed V8 on Octane performance
#8Firefox 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 resets your profile while preserving history, cookies, bookmarks, etc.
> I'm really looking forward to the new threading model coming up. I have a feeling that once each tab has a thread, things like this will be much more self-repairing. It's not always easy to kill a rogue execution path in an event loop, but killing a thread is pretty straightforward =].
First, it's "process", not "thread" :)
The plan is to start with just two main processes -- one for chrome (browser UI, mostly) and one for web content. So no processes will be killed in normal operation. This is because additional processes incur certain extra costs, particularly when it comes to memory consumption.
Still, it might help with your problem; it's hard to say for sure.
Re: Spidermonkey has passed V8 on Octane performance
#9Re: Spidermonkey has passed V8 on Octane performance
#10You 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.
Here's how I think browser benchmarking should be done: https://blog.mozilla.org/nnethercote/2014/06/16/a-browser-be...