Firefox 4 Regains Speed Mojo With No. 2 Placing 98
CWmike writes "With the release of Firefox 4 Beta 7 this week, Mozilla has returned to near the top spot in browser performance rankings. According to SunSpider JavaScript benchmark suite tests run by Computerworld, the new browser is about three times faster than the current production version of Firefox in rendering JavaScript, and lags behind only Opera among the top five browser makers. Mozilla launched Firefox 4 Beta 7, a preview that includes all the features slated to make it into the final, polished version next year, on Wednesday. Beta 7 was the first to include Mozilla's new JavaScript JIT (Just In Time) compiler, dubbed 'JagerMonkey,' which shot the browser's performance into the No. 2 slot behind the alpha of Opera 11."
Ofcourse it's only at number two (Score:1, Funny)
Re: (Score:2)
Which will be stupid, since the second page of TA is all about hardware rendering, which works even (partly) on XP, unlike IE9, and on the MacOSX.
Re: (Score:2)
Cue the "Performance in browsers isn't just about Javascript!" comments.
Here's an example: I switched from Firefox to Chromium last year, but not because of Javascript performance. I did it because Firefox had a nasty habit of doing a bunch of housecleaning when it shut down (I don't know, but I assume it was doing huge updates on an internal SQL database or something like that.) That could cause it to lock up for many seconds after I hit the close button; sometimes the window manager would pop up a dialog asking me if I wanted to terminate the unresponsive app.
That behavior wa
Re: (Score:1, Interesting)
I stopped using Firefox because it would use up large amounts of memory after only a couple of days and then start lagging every 30 seconds or so until I restarted it. That is related to page rendering performance since the lag directly affected it.
Re: (Score:3, Insightful)
Re: (Score:2)
I keep a personal compilation of benchmark results from Peacekeeper's browser benchmark. I do not like their averaging of tests but I do like their individual tests. Due to this I keep the numbers in a Google Docs spreadsheet where I can easily look at them.
Here are my results, [google.com] with Firefox 4b7 included. Beta 7 does not seem to be much faster than Beta 6, although in some tests it is a big leap from Firefox 3.6.8.
BTW, these are all ran on the same machine with no configuration changes and the same back
Re: (Score:2)
But performance in browsers isn't just about Javascript!
Whichever browser can run Farmville/Fronterville/Mafiawars (all facebook apps) the best will win over most people.
I have a modern-ish machine that runs Lord of the Ring Online quite well, but crawls when I looked up those apps.
Re: (Score:2)
Cue "we don't really care about performance", rather. I care about feature, compatibility, safety, stability... and not a jot about performance.
Re: (Score:2)
People _say_ that, but when they vote with their feet (or mice, as the case may be) it turns out that they do care about it. Often subconsciously.
Is news.slashdot.org borken? (Score:2, Interesting)
I get 404s unless I change the url to slashdot.org/...
Re: (Score:3, Interesting)
Me too. Very strange.
Re: (Score:2)
While there’s supposedly no such thing as a stupid question, that definitely comes close.
Huh?
Re: (Score:2)
I had the same issue for a while this morning. I could get to every other /. article except this one.
Realistic tests? (Score:2)
Re: (Score:2, Interesting)
No, there's not, because the outcome would inevitably be "every browser is fast (and you won't notice a difference) given enough RAM, CPU power etc". In reality, it's not things like Javascript microbenchmark performance that matter: browsers CAN be faster or slower, but whether you can get a few ms less on Sunspider is going to be lost in the noise. The real differences will stem from other factors.
As such, the whole thing is basically a giant red herring. I'm not sure why Mozilla is playing along here, ei
Re:Realistic tests? (Score:4, Insightful)
No, there's not, because the outcome would inevitably be "every browser is fast (and you won't notice a difference) given enough RAM, CPU power etc". In reality, it's not things like Javascript microbenchmark performance that matter: browsers CAN be faster or slower, but whether you can get a few ms less on Sunspider is going to be lost in the noise. The real differences will stem from other factors.
That's because you're looking at it wrong. JS performance isn't going to improve the current browsing experience, that is perfectly true. The part you are missing is that the JS performance matters for FUTURE browsing.
Why, you ask? One word: Flash. HTML5 exists purely to replicate most of Flash in native HTML. Flash is heavily scriptable and runs complex apps (see any heavily produced Flash game) with passable performance (most of the performance problems with Flash are due to the way the graphics stack was designed [it sucks]). If Canvas, Video and Audio tags are going to replace Flash, the JS needs to be comparable to Flash's ActionScript performance — preferably better to insentivize migration.
Re: (Score:2)
Re: (Score:2)
Shall we get off your lawn now?
Re: (Score:1, Offtopic)
Slashdot is full of old fogies like that. A tech site full of tech Luddites.
Re: (Score:2)
Re: (Score:2)
I recall IE6 as being pretty speedy at the time, but not working right if you followed standards of course. These days anything is faster than IE on XP, though.
Re: (Score:3, Insightful)
For standard website browsing, the biggest bottleneck is probably going to be the network connection. If you're talking about a handful of seconds to download a page, then a few milliseconds here and there on some Javascript isn't going to matter, like AC said. However, AJAXy webapps that make extensive use of Javascript may show a lot more difference if each Javascript function takes an extra 100ms to run. I think that's the point of these JS benchmarks - everything else is pretty much the same, so we'r
Re: (Score:2)
reddit loads noticeably faster using b7, esp with threads with over 500 comments.
This was coming for a while... (Score:2)
This is a great achievement from the development team who consistently improved the performance from 'quite bad' to 'competetively fast', so kudos to the developers. Please don't stop now, it seems you can still stretch performance quite a bit...
Re: (Score:2)
Adding the JIT was obviously improve performance massively. Now the path for JS optimization is much more difficult.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:1)
Firefox has a better extensions framework, better configurability, a better interface and better performance.
Verified with my SW-only Javascript 3D renderer (Score:3, Interesting)
On my aging PentiumD/2.8GHz:
Re: (Score:1)
It's just plain math and a "plotpixel" function... so I'd be happy to know what to change to make it run faster in other browsers - any suggestions?
(the good thing about Javascript - the code is open-source by nature)
Re: (Score:2)
What about the latest Chrome? 9.x
Re: (Score:1)
Re: (Score:2)
Chrome 9 is dev. The analagous test would be with Chrome 8 (beta). On my old-ass "IBM" thinkpad T60 (centrino duo w/ ATI gfx), I get 20fps on Chrome8, and 24fps on FF 3.6.12.
Re: (Score:2)
I cracked your top 15 with 67.84fps with 64bit Firefox from 10/15 (it's the only one stable with Flash still) and a mobile i5-520M. Just FYI ;)
Re: (Score:2)
URL doesn't work (Score:3, Interesting)
The link on the front page goes to http://news.slashdot.org/story/10/11/12/037241/Firefox-4-Regains-Speed-Mojo-With-No-2-Placing [slashdot.org] which doesn't work. The same URL without "news." works.
Re: (Score:3, Funny)
216.34.181.48 news.slashdot.org
in your hosts file also works
Re: (Score:1)
Why would you do that, when simply backspacing part of the url is so much simpler?
Re:URL doesn't work (Score:5, Insightful)
Re: (Score:2)
Naturally, because an ugly kludgy hack due to a temporary problem is always preferable to something simple and effective.
Along that line, is there a GreaseMonkey script to fix idle.slashdot.org? Backspacing over “idle.” is too easy.
Re: (Score:1)
127.0.0.1 idle.slashdot.org
in your hosts file also works
Re: (Score:2)
If I just didn’t want to go there, I’d just adblock all links pointing me to it like I adblocked (#a(href*=goatse.)) links taking me to goatse.cx [goatse.cx].
Re: (Score:2)
Alt+F4 speeds it up considerably, unless it crashes your browser. If you crash, try it again until it works.
Re: (Score:2)
That doesn’t work at all on this webpage [tinyurl.com], though.
(Don’t use IE. No, it’s not goatse.)
Re: (Score:2)
That would have been moderately cool if it had worked.
Re: (Score:2)
It works on Firefox.
Re: (Score:2)
With a few caveats, I suppose I should add.
The page has to have focus. If the cursor is in the address bar, all hotkeys work as advertised.
Also, for some weird reason, while alt-F4 and ctrl-W don’t do anything, ctrl-F4 still works (it closes the tab, not the window).
Re: (Score:2)
I very much agree with this statement. However in this specific case editing /etc/hosts barely qualifies as overly complicated!
I love such stories (Score:2)
I love stories who run like this: "Not-released-software A is faster than Not-released-software B". Great news! Carry on!
Re: (Score:2)
Re: (Score:2)
Except the code is right out there for you to obtain.
Test it yourself and see (Score:1)
Firefox 4 beta 7 uses twice memory as 3.6.12 (Score:2)
Plus the Aros interface of the menu/tab bars really makes the fonts unreadable
Re: (Score:2)
Javascript speed is nice and all... (Score:2)
Re: (Score:2)
Re: (Score:2)
Mod parent ironic.
why do i care about speed when (Score:2, Insightful)
when nevercooky is not in the default install
when the new addon webpage looks like a commercial for useless crap, instead of a guide to all of hte addons
when pdf handling still sucks in the default,and is, in my hands, number one cause of crashes
the browser lets other people see stuff like what type of browser I am running, and doe
Minor nitpick (Score:2)
I've Been looking Forward to This (Score:2)
Re: (Score:2)
The problem is, the performance improvement to the Javascript engine does not equate to running light on the system resource usage. My guess is you aren't going to see all that much of a difference there. (However, as an avid Chrome user, I haven't actually verified my claims with Firefox.)
How about a UI benchmark? (Score:1, Interesting)
Sure JS speed is nice, but the reason I switched to Chrome was simple, the UI is actually responsive.
Launching new windows/tabs in FireFox is noticeably slow, whereas Chrome is almost instant. Rearranging tabs, slow on FireFox, snappy on Chrome.
Try loading a large page in FireFox, while its being rendered the entire UI locks up tight. When I do Google searches I tend to open 10-20 tabs at once with the results I find interesting, then go back and look at them all. Again with FireFox this is a slow operation
Who cares? (Score:2)
You know what? If a page takes 200 milliseconds longer to run because JS performance isn't quite as fast who cares?
None of these browser speed wars addresses the problem that when I watch Hulu on machines that aren't top-of-the-line state-of-the-art, the video is jumpy often to the point of unwatchability.
My pipe is fat enough and the computers I'm using can do fullscreen video just fine. It's Flash, especially on Linux, that kills performance. Most video sites still use Flash, as do a lot of those fun l
I respect Adobe 100x more than them (Score:1)
You know what? If a page takes 200 milliseconds longer to run because JS performance isn't quite as fast who cares?
None of these browser speed wars addresses the problem that when I watch Hulu on machines that aren't top-of-the-line state-of-the-art, the video is jumpy often to the point of unwatchability.
My pipe is fat enough and the computers I'm using can do fullscreen video just fine. It's Flash, especially on Linux, that kills performance. Most video sites still use Flash, as do a lot of those fun little games, etc., and the only only alternative to Flash in most cases is to go without the site or functionality. Flash is what makes web browsing slow. Every other performance issue is like line noise in comparison.
Old times, when some company abandons/will abandon your computer/OS or you can't decide whether to join the herd (windows) or run linux/BSD, you always had Firefox at your mind. You would think it would have Firefox support and would run it one way or another.
Now, they dropped PowerPC binaries (because their cool looking addressbar not working) and speak about dropping anything below SSE3. Publicly that is...
Code is being infested by completely unportable x86 specific ASM to join cool kids with JS asm accel
How about usability (Score:1)
Evolution of JavaScript Implementation Speed (Score:2)
This story makes me curious: how has JavaScript implementation speed improved over time? I see a lot of benchmarks comparing recent versions of browsers, but does anyone have a comparison against, say, Firefox 1.0? Also, how do current JavaScript implementations stack up against current implementations of other languages, such as C, Lua, or Python?
At cost of? (Score:2, Insightful)
In other news, OS X PowerPC was dropped and there is also a crazy talk about dropping anything=SSE3. They really lost the design philosophy of Firefox or anything Mozilla. What happened to portability especially when nobody likes their mobile offerings? How many times they must learn to think outside X86 PC?
Firefox in speed race with a company who controls/knows about every single device they shipped (Apple) and another who can spend couple of billions of dollars in no time without even noticing it (Google)