Browser benchmarks 2: even Wine beats Linux Firefox

Mozilla

We posted yesterday about Firefox having very different JavaScript performance on Windows and Linux, despite being the same version of the software.

Some people have said that we should have used a stock build from Mozilla. (We disagree, because we'd argue that most Linux users use software from their package manager rather than downloading bits and pieces from the web.) Others have said that Opera should be tested. And some people have said that it's Nvidia/AMD/Intel drivers that are slowing down Linux.

Anyway, we thought we would conduct a couple more quick benchmarks to see whether we can eliminate some of these variants. We don't have time to run the full benchmark suite and fiddle around from scratch, so we ran just a few quick tests to see what we could find.

This time the information you need to know is:

  • These benchmarks were run on the same computer as before, running the same Fedora 10 install.
  • We tried Mozilla Firefox for Linux as downloaded straight from Mozilla.
  • We also tried Mozilla Firefox for Windows as downloaded from Mozilla, but running it using Wine on Fedora.
  • We installed and tested Opera 9.63 for Fedora 10, as downloaded from Opera.com. Note: we were only able to find i386 builds on the Opera site; this isn't optimal so if someone can point us towards an i686 build for Fedora 10 we will happily update the article.
  • We ran the Google V8 Benchmark suite V3, as before.

To be absolutely clear: we took the Windows Firefox and ran it on Fedora Linux using Wine 1.1.12 as provided by Fedora:

  • "Firefox Windows" is Firefox running on Windows.
  • "Firefox Fedora" is Firefox running on Fedora using the Fedora package.
  • "Firefox Mozilla" is Firefox running on Fedora using the Mozilla build.
  • "Firefox Wine" is Firefox as compiled for Windows running on Fedora using Wine.
  • "Opera" is, well, Opera 9.63 running on Fedora.

With all that in mind, here's how the results look now:

Firefox on Windows, Linux and Linux/Wine

Firefox running on Windows, Linux and Linux/Wine, plus Opera.

The end result: Firefox from Mozilla or from Fedora has almost nil speed difference, and Firefox running on Wine is faster than native Firefox. Opera lags behind, but we're inclined to believe that number would increase if a better build was used.

Is this the end of the story? Probably not - we expect some commenters will come up with some other reason why the slowdown is clearly Nvidia/ATI/someone else's fault. Go on, folks: try the benchmark yourself. If you're running Linux, install Wine and try Windows Firefox on Wine and make up your own mind.

You should follow us on Identi.ca or Twitter


Your comments

Anothet test results

Gentoo Linux Amd64
gcc 4.3.3, FF-3.0.6, wine 1.1.16
CFLAGS="-g -DNDEBUG -march=k8 -O2 -msse3 -pipe"

Google V8 Suite (draw)
Firefox Wine (1.1.16) 150, 146, 150
Firefox Linux 150, 150, 145

SunSpider (Linux Native wins)
Firefox Wine (1.1.16) 4731.8ms +/- 0.7%
Firefox Linux 4403.0ms +/- 1.2%

My results

Ubuntu Firefox: 99
Wine Firefox: 160
Epiphany: 167
Wine IE 5.5: Could complete 38% only

The beginning of the end

This is just one more example of the unclothing of Emperor Linux. Can anyone suggest for a moment that the Firefox team wouldn't use every possible tool or technique available to ensure that the Linux distro performs as well as possible? Of course not. The issue clearly lies with the quality of the operating system. But of course the infected carriers of MDS (Microsoft Derangement Syndrome) still see glittering royalty in a code set that looks like a Rube Goldberg contraption fastened together with thousands of frayed strips of duct tape.

Mozilla hates Linux. That

Mozilla hates Linux.

That explains why Firefox is so slow on Linux.

Very interesting results.

Very interesting results. I've been using Ubuntu for a few years now as my main OS and I've found the main weak point of the later builds is Firefox. It tends to crash (i.e. freezes and needs force quit to close it) or just be really slow at doing some things. My (entirely empirical) observation was that the threading doesn't seem to work as well as it should, so a 'busy' tab can stop things working in other tabs. Also very poor when in contention for bandwidth with, say, bittorrent, so that pages that should load, albeit slowly, never load at all. By contrast when I boot XP to play games and end up doing a bit of browsing things are far snappier, looks like you may be homing in on one possible cause.

SPM

If Firefox on WINE on Linux runs at nearly the same speeds as Firefox on Windows, then that is definitive proof that Firefox's slowness on Linux is nothing to do with Linux or X rendering, but due to the Linux version of Firefox alone. I also doubt if it is anything to do with the compiler used, since the effect sould not be that dramatic. I think it is due to Firefox not being optimised on its Linux version.

and factor responsible for slowness is..

GTK

That's right - it's not secret that this joke-toolkit written in C many years ago to provide free and open source (as of then) competition for Qt is ironically much less responsive and laggy than Qt written in C++ (especially 4.5 with raster renderer - and OpenGL renderer is WIP).

Fortunately, in March 2009, Qt 4.5 will be released and licensed LGPL - that being said - the only reason GTK ever existed will cease to be and GTK should die along with it.

Stop blaming compiler and compilation parameters - I'm using Gentoo for many years and I know well enough that enabling mindless optimizations is not a factor for such dramatic speed improvements - especially comparing to default -O2 which already enables most sane optimizations and is far good enough.

Graphics

I don't know how much graphics the tests do, but an interesting fact of X11 is that it is very slow (each rendering operation is to be done in a separate process).

Qt 4.5 toolkit offers an option for pure software rendering (i.e. in the process of the application), and contrary to what one would think (X11 having hardware acceleration etc.), that software rendering is actually many times faster.

Now if GTK+ toolkit had such a software based rendering mode...

Javascript optimisation is a work in progress.

With benchmarks relating to javascript execution speed (using JIT compilation), one should bear in mind that the lightening increases in speed that have occurred very recently are a work in progress, and the full optimizations have only been introduced to Windows so far - Google Chrome is Windows only so far, as is I believe the Firefox optimizations.

Hence is is a bit of FUD to claim as some have done that this proves Linux is slow compared to Windows - wait a few months for the javascript optimizations to the Linux versions and Linux benchmarks will match or beat Windows.

For comparison look at how IE6 on Windows (not optimised for javascript) runs on Windows compared to Firefox on Windows

Quote/

Just ran the V8 benchmark for FF 3.0.6 and IE 7.0 with the following results:

IE 7.0 31
FF 3.06 115

/Unquote

On the same basis, one could run Firefox 3.06 with the javascript on Linux under WINE and compare it to IE6 on Windows and claim that Linux is more than 3 times as fast as Windows - fodder for the fudsters, shills and fanboys, but disproved by the fact that Firefox for Windows running under WINE under Linux is as fast as Firefox running natively under Windows.

filesystem ext3?

I remember there being an issue with firefox and ext3. I wonder if there's an issue with the caching behavior of the browsers?

I suppose testing to see if the results are different on ReiserFS or ext4 and seeing if the benchmarks change when the caching is disabled...

Jithin

I dont know about the bench marks. But from my use experience I always felt Opera is way more fast that firefox from my ubuntu repository.

Ubuntu?

Add Ubuntu to your benchmarks!!!

Optimizing compilers?

<i>"To the poster who said that "There is only so many ways you can write an optimizing compiler". It is exactly the opposite. It is actually a fun fact - it is proven that there are infinite number of ways to write an optimizing compiler."</i>

Kudos to the first person who can write a compiler that optimizes your app to 0kb!

Midori?!

Firefox Linux: 153
Epiphany: 155
Midori (WebKit): 1473 (what the hell?!)

I confirm this too

What was an unspoken truth has come out as a big shout!

Firefox on Linux needs optimization and the developers should give back to the community from which they derive much.

Firefox on windows is a lot faster and I usually find it faster while running my Firefox Portable using wine.

I think this is due to Firefox developers giving more time to their bigger customer slice who are on Windows. __After all why give a damn to Linux users who have limited choice in case of web browsers (we don't have IE or Chrome and Opera or Konqueror are not much choice).__ (pun intended)

Strange this happens with other apps too!

Sumatra PDF again downloaded from portableapps.com, renders pdfs faster than native OKular or GNOME's Evince

This is pretty sad...

This is a pretty sad article on the part of the author. In fact it makes me question the technical competence of the author.

In your test the Linux system is running both Wine and FF. FF is running native code and FF-Wine is running an "emulation" layer thats still running native code under it. FF-Wine has an additional layer of work to do. So if Linux itself is slow then its going to be slow in both cases. The only differences between the two are the FF code bases (Win vs Lin) or the graphical toolkits used (GTK, QT).

Now maybe someone can come up with a way to test out GTK and QT so that we can eliminate them from the equation. However I get the feeling that the author doesn't really care about the suggestions. He just wants to make a case that Linux is slow without trying to find the reasons and take them to the devs.

Also...

Have you tried comparing other browsers on both systems to see if this is a Firefox phenomenon or if Linux runs browsers slower across the board. I just tried Midori for comparison and if beat the breaks off FF on Ubuntu.

You don't seem to be trying to eliminate any variables here. You just run one browser on two OSes and proclaim one to be slower. Do you really want to get to the root of the problem?

Now you can whine and scream about the average user not using Midori but if you do then you have missed the point ENTIRELY. If you're a Linux fan and want to make it better then lets do some real investigative work and track down the problem.

My tests

Gentoo on 1.6Ghz Pentium M, GCC 4.1.2
CFLAGS="-Os -march=pentium-m -pipe -fomit-frame-pointer"

on google v8 test:
native Firefox 3.0.6 129
wine Firefox 3.0.6 150

Debian Bechmarks

Debian sid 64-bit. Tests were performed 5 times. Error is standard deviation.

iceweasel amd64 3.0.6-1: 140 +/- 3
iceweasel i386 3.0.6-1: 123 +/- 3
firefox i686 3.0.6 : 118 +/- 2
firefox wine 3.0.6 : 144 +/- 4

It looks like we have a problem.

Conclusion

It is clear that the companies prefer to spend most of their time fine tuning their strategic and time consuming apps for the leading OSes. Period.
It is quite reasonable spending almost no time for supporting an OS that has less than 3% market share, according to other stats - less than 1%.

For now, if the Linux community wants better code, it must either greater market share or participate itself and improve the quality of the corresponding portions of the Linux code.

Things that it is NOT due to

No the Linux kernel, X, GCC or graphics drivers. These are all involved in Firefox for Windows running under Wine.

So it is down to two possibilities:

(1) The GUI toolkit/widgets used in Firefox native Linux, or
(2) Firefox native Linux core code itself.

I'd opt for (2) above, given that the Windows version of Firefox uses an optimisation technique call "Performance Guided Optimisation" (PGO), where the Linux version currently does not.

Apparently this is soon to be fixed, however:

"The windows version of Firefox has got PGO enabled since version 3. The Linux version does not. Version 3.1 WILL be compiled with PGO enabled for Linux."

So, if this lack of optimisation in the compilation of the Linux version of Firefox for versions earlier than 3.0.x is indeed the culprit, then happily the next release of Firefox for Linux should see this performance difference disappear.

JAVASCRIPT PROFILE GUIDED OPTIMIZATION

The explanation for this is javascript Profile Guided Optimization for JIT features. This and Javascript was introduced into Firefox and Chrome to boost javascript performance by a factor of 10 to 20 over existing browsers like IE6. PGO has been incorporated into Windows Firefox in version 3.0x whereas it will be introduced into Linux versions of Firefox in version 3.1. It is also the explanation why IE is massively slower than the Linux versions of Firefox on the same benchmark (by a factor of more than 3) - IE6 does not have any javascript JIT features at all.

Basically, the bottom line is that the Firefox Linux version is a couple of months behind the Windows Firefox in the implementation, but implemented it will be. Unfortunately as can be seen from a number of the comments, this has not stopped wishful thinking Windows fudsters, fanboys, shills etc. proclaiming that Linux is a toy, what would you expect from a free OS, it shows Linux is obsolete etc. Just part of the course I guess.

V8 Benchmarks aren't about rendering...

@the anonimous author of "The beginning of the end"
THANKS you made me laugh :) please keep trolling about unknown

btw. the V8 benchmark suite isn't about rendering, it's a test to know how much time the javascript engine takes to execute an algorithm, as stated by google's page: "This page contains a suite of pure JavaScript benchmarks that we have used to tune V8."

So, GTK and X here are not a problem (you are not rending anything), Linux (i'm talking about the kernel) is not really touched. The poor performance is caused by the less-optimized javascript engine in firefox's unix code (even in OSX firefox score sucks)

The benchmark's purpose is to give a score to the Javascript (ECMA not java) engine.

peace:)

Other benchmarks suites?

I have not looked too closely at what the google benchmarks actually do to come up with these scores. And even with everything else perfectly aligned, the performance difference between ff on win vs lin is probably still a mystery.

But I can't help wondering whether the 300% speed increase going from ff to webkit could be a feature of the benchmark suite itself, rather than a compiler/code-quality thing? And if that is the case, perhaps something in the windows build is somehow treated preferential in the benchmarks as well?

Is there another benchmark suite out there, besides the google suite, that we could try to verify these results with?

FWIW, I get 193 in Firefox under Fedora 10 (x86_64) and 807 using webkit on the exact same machine.

One more interesting data point

It would be interesting to see the same benchmark run under the Linux version 2.0pre3-alpha Seamonkey. Some of the operations are notably faster. And for grins including Chrome would give people a reference point.

Opera results

My scores

Opera 9.63 static-qt (Debian 5.0): 91
Opera 9.63 Wine (Debian 5.0) 165

Disturbing.

Google Chrome 1.0

Please show scores os google chrome it's twice as fast as ff on windows ;)

It's gotta be a Microsoft

It's gotta be a Microsoft fault somehow. Maybe Mozilla is being paid by M$ to make Firefox slower on Linux.

FreeBSD results?

An easy way to see if GCC is responsible would be to compile FF using FreeBSD's compiler - IF it is better, than we have a possible cause, but if it's the same, the result is also pretty much useless...

Interesting the choices made in this test.

>Javascript used to be interpreted until very recently Google Chrome, Firefox, and Safari introduced JIT compiling to increase javascript speed by a massive factor, however all the features are not enabled yet on all browser variants.

>On the Webkit benchmarks the two slowest benchmarks by a large margin are IE7 and IE8.

>PGO isn't enabled yet on the Linux version of Firefox, and hence it currently runs slower than Firefox on Windows, but much faster than IE7 or IE8 on Windows. PGO will be enabled soon on Firefox Linux versions and then Firefox will run as fgast or faster on Linux than on Windows.

In other words, almost any comparison of javascript performance on Linux versus Windows would have yeilded the result that the Linux version was much faster ... except for the versions chosen by the original authors.

In order to get the result where Windows javascript performance was better, the original posters HAD to choose Firefox 3.0.x on Windows XP versus Firefox 3.0.x. on Linux.

ANY other choice for comparison would have yeilded opposite results. Choosing to compare Linux vs Vista, or choosing Firefox 3.1, or choosing any version of Firefox 2.x, or choosing to compare Firefox on Linux against IE (any version) on Windows (any version) ... would have resulted in the result that Firefox on Linux had the better javascript performance.

Interesting.

Agenda, perhaps?

I am not sure there is an agenda...

...at least with regard to the author of the article. Firefox 3.1 hasn't been released you except as a beta. Some of the Windows fanboy/shill posters clearly seem to have an agenda which they are very quick to jump on though.

The single most sensible suggestion

As posted recently, you should indeed compile the windows version with gcc and recompile the linux version with gcc using the same options and see if indeed the compiler is implicated.

Having established whether (or not - and my gut feel is not) this is the case, then all that remains is poorly optimised Linux code within Firefox. Profiling ought to pin that down, I would have thought. I remember years ago having a performance issue with a Windows application and finding that the leading bottleneck was a call to get the decimal point character for the locale - the developer had called this virtually every time a number needed formatting and it turned out to be a surprisingly expensive call.

GCC

It is generally known that GCC does not produce FAST code.

It may be good, it may be free, but the result is not FAST.

Try compiling a program with compilers that does not use GCC as backend, like freepascal, and you will be surprised of executions almost instantaneous... which is normal with the super fast CPUS we are using this days.

To be absolutely clear

As we can see in the graph Firefox Mozilla got 181 bananas in the benchmark whereas Firefox Wine got 227 druken penguins.

Is it so hard writting WTF the units mean!? comparison with a reference system (as in this case), DOM accesses per second, time to load whatever... And at least saying something like "higher is better".

On my rig, and the numbers

On my rig, and the numbers are not terribly important, Epiphany outperforms Firefox on both the Google V8 v3 and Sunspider.

GTK?

Isn't it obvious that it's GTK that's slow here?

robert@ocallahan.org

Our Windows build uses profile-guided optimization and our Linux build does not. Also, MSVC generally produces faster, smaller code than gcc. That is easily enough to explain the differences you're seeing here. It also explains why running the Windows build under WINE is faster.

Almost all Linux Firefox users are actually using a distro packaged build. So hassle your distro to use PGO if they aren't already.

Also, be aware that the Google V8 benchmark is fairly narrow and bogus; it basically tests recursive method calls. Sunspider is a much better all-round benchmark.

robert@ocallahan.org

Oh, just to allay conspiracy theorists: far more Mozilla developers use Linux than Windows. Partly because it takes about 20 minutes to build Firefox on a good Linux box vs an hour on Windows. And also of course because of free software.

Windows still rules

Just wait till Windows 7 comes out. I exhaustively benchmarked the latest IE8 beta and it is two orders of magnitude faster than anything else on the market, AND I did it on my netbook with only 512 mb of ram. Web surfing on Windows 7 compared to Linux and OS X is like comparing an F1 race car to a horse drawn cart or a 60's Volkswagen Beetle, respectively.

.

.

GCC slow? No it isn't.

I have a project at work that looks up items in a custom memory mapped database. It was developed in C++ on Linux and ported to Windows, built on Server 2008 with VC 2008.

It does a lookup about 5 times slower on Windows built with MSVC. It is all in the compiler too, because the inner code uses no API calls at all.

There are a couple of reasons for that speed difference. The Linux version does profile optimization and Windows doesn't, because of bugs using certain types of DLLs for profiling in VC2008.

The GCC version gains a lot of speed by mashing all the source files together into single sources as an alternative to the IPO that MSVC offers.

That probably isn't practical for Firefox. The resulting pile of source would be massive and GCC would probably want 20 GB of RAM to compile it. But I believe it does show that GCC does not produce slow code.

Swiftfox is not the solution and FF 3.1b2 does worse

I'm using Kubuntu 8.10, with native FF 3.0.6 from the repos I get 161 and with Swiftfox I get only 171, not good enough IMHO, On WINE I get around 188.

Ironically FF 3.1b2 which uses the new TraceMonkey JS engine gets 154 when using the native linux binary and 173 when using WINE(javascript.options.jit.content = true in both)

My thoughts

The main reason for Firefox-Windows performing faster than Firefox-Linux is the default GCC compiler flags used in the builds:

Fore Windows Mozilla defaults to -O2 optimization;
for Linux Mozilla defaults to -Os optimization.

This is apparently because of the huge file size reduction offered by -Os on Linux.

I have compiled Firefox for Linux using the -O3 flags and the performance is dramatically increased on my Athlon box.

Midori 2

On same hardware both using libgtk-x11-2.0 :

FF : Score : 71 ->
Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.9.0.6) Gecko/2009020407 Iceweasel/3.0.6 (Zenwalk GNU Linux)

Midori : Score: 775 ->
Midori 0.1.1-a4e6720

x10 !!!! Mozilla team : how about checking your code ?

I am GAY,OK?

I am GAY,OK?

Maybe it's due to the

Maybe it's due to the wine-gecko implementation

Upside down graph anyone?

It seems to me... that opera is winning, native firefox is in second, and windows based ff is last. Why? Because its up to my interpretation. You see, the original poster obviously failed his/her graph theory course, as there are NO metrics whatsoever on that benchmark.

Is that iterations per second? Some vague qualitative analysis not based on any real world metric? If its the latter, this means diddly. If its the former, you're all ranting on the wrong build.

Just thought I'd point that out, since 25 points here and there could mean as much as a split second for all we know.

No surprise

I used linux for a year now, and I'm quite aware of the difference. Occasionally I'll launch Opera or Firefox in Wine to get a page that freezes in linux. To me it's rather a disappointment, however I didn't leave windows for the performance issues - more because I really wanted to get away from the kind of evil inherent to the platform.

V8 benchmark is probably not the best.

Hi guys, just thought I'd let you know that I've repeated the test with the latest 3.1 candidates and got similar results with the V8 benchmark, Wine Firefox comes in at 118 on my machine while Linux Firefox scores only 61.

However on the SunSpider benchmark, Firefox Wine and Firefox Native are *much* closer, with Firefox Wine coming in at ~2500ms and Firefox Native at ~2800ms.

Amazingly on Celtic Kane's Javascript test Native Firefox is shown as being over twice as fast as Wine Firefox, coming in at ~530ms vs ~1100ms.

So it seems that this whole thing could be much ado about nothing as Shakespeare said, and serves as a lesson about why we should take micro-benchmark results with a grain of salt.

Unless, that is - that you believe Firefox on Linux can be simultaneously half as fast, just as fast and twice as fast as it's Windows cousin.

However, after saying all that, I was unable to test Firefox in Windows on this machine, so I assume there is still going to be a fair speed deficit between Firefox on Windows and Firefox on Linux... at least as far as microbenchmarks are concerned.

Why do you wonder about that

I am using both, Windows and Linux (at work) and I really hate using Linux as a Desktop because it is just way slower than Windows is.
It feels like working with a 386 machine especially when I use Firefox.
I wonder why there aren't more people complaining about that. And please don't think that I am an unexperienced user who is not able to configure his system properly. I am using Linux and Windows for ages.
Every kind of browser is working in windows much better compared to Linux and I am not talking about the rendering time. No, its about scrolling, switching tabs etc. Linux just feels (and it is) way slower. Don't misunderstand me, I really like Linux and I am not a Microsoft fan at all but we just need to realize that Linux Desktops are far behind Windows ones.

Cheers,

Fedora user :-)

Wow, that's a lot of data in

Wow, that's a lot of data in the comments. Maybe it coul be leveraged to get some meaningful statistics (kind of a poor man's Phoronix Test Suite for browsers... and that would be a really poor man).

Anyway, here's my results, running KDE4 with openSuSE 11.1 on a Celeron M 1.6 with 1.5 GB RAM and a homebrew 2.6.28.7 kernel:

Firefox - Linux (3.0.7): 87,8
Firefox - Wine (3.0.7): 95,2
and, surprisingly,
Minefield - Wine (3.1b2): 93,2

Admittedly, I do have quite a few add-ons installed on my linux build that I didn't care to install in Wine. But, all in all, gosh, are those results low!

Ubuntu 8.10 my results on

Ubuntu 8.10

my results on Sunspider

firefox 3.0.7 native => 6065.0ms +/- 5.8%
minefield 3.2.a1pre native => 3361.8ms +/- 17.3%
firefox 3.0.7 under WINE => 4926.4ms +/- 2.8%

V8 Benchmark Suite - version 3

firefox 3.0.7 native => Score: 112
minefield 3.2.a1pre native => Score: 147
firefox 3.0.7 under WINE => Score: 155

hope it helps, does anyone know in Minefield is using PGO??

Compiler.... compiler

You did not compare apples to apples, but also means that we need to be fairly reasonable.

The compiler used in Firefox Winodws build have a bigger inherited level of optimizations. The same issue appears also in OpenOffice.

Anyway, your machine is a 64 bit capable, and for the sake of comparison, the 64 bit binaries in computational intensive tasks gain between 10-20% in real world applications. So you may get the same improvement using the 64 bit version of the distros. In real life there is no reason why you shouldn't use a 64 bit version. Also, the Firefox builds are 32 builds, so they will not give any optimizations.

What should be done in future to not make the difference so big? Mostly the distro makers should use Profile Guided Optimizations using the most used sites: gmail, ymail, and JS benchmarks. This will get a win of 5% overall (it may be as 15% in 2-3 cases) but will reduce the gap. As most Distro makers do not do that, if I would have your machine and I want Linux and speed, and no head hassle, for sure I would pick a Linux 64 distro!

another benchmark

hey there, i did my tests too

Details : FF 3.0.8, Fedora 10 x86_64, 2.6.27.21
AMD Athlon(tm) 64 Processor 3500+
cpu MHz : 2200.000
(during tests)

Results :

Score: 74.5
Richards: 36.9
DeltaBlue: 75.9
Crypto: 84.1
RayTrace: 98.0
EarleyBoyer: 114
RegExp: 65.2

What?

How the heck does this happen? Shouldn't it take slower since WINE has to load libraries and whatnot? That is really weird.

Actually, on my computer, it takes windows about 5 seconds to load Firefox, while on Linux, it takes about 2.

What?

How the heck does this happen? Shouldn't it take slower since WINE has to load libraries and whatnot? That is really weird.

Actually, on my computer, it takes windows about 5 seconds to load Firefox, while on Linux, it takes about 2.

Whoops

Double post

How long have you been playing ball?

Compiler optimizations will yield better performance. Glibc, GCC, and the Linux kernel compiled for the architecture will perform better.

* note: architecture meaning i486, i586, i686 and Pentium 4, Pentium Core Duo, Pentium Core 2, Xeon

Windows probably has binary checks to enable features for different architectures. Only Windows operating system developers from Microsoft could truly explain this.

With all that said,

Fedora enables SELINUX by default. This is more of a hinderence to performance. Their kernel is compiled Pentium 2, i586, probably with the server preemption kernel option and 250 hz timer resolution option.

Ubuntu:
A better distribution to test against because they are user oriented supposedly. Perform your tests again on Ubuntu 8.04 which is the current maintained distribution of Ubuntu. I'd advise avoiding Ubuntu 9.04 as there are major issues with the Intel graphics drivers. This will reflect what the majority of users currently use.

Identifying the problem:
So the real culprit here is the kernel and operating system.
If you are seeking the results you get from wine and Windows then recompile the kernel with the following options.
* CPU type, ie. Core 2 or whatever your cpu architecture is
* 1000 hz timer
* Voluntary Preemption
* Tickless Timer Optional
* Disable kernel profiling

Recompile GLibC for i686 cpu architecture.

Recompile Xorg for i686 cpu architecture.

Recompile Firefox for i686 cpu architecture.

Disable Xorg's compositing.

Run your test again and be amazed.

ArchLinux and Gentoo handle the majority of what I've outlined here. They are superior versions to all other Linux distributions when seeking performance.

Call-outs:
Nothing is ever handled upstream. This is a bad practice. If you're going to help save the world .... computers, come on people need food, water, and good teachers. Machines will be the death of the human race.

Thank you for your time.

Epiphany wins no competition

These is the score of epiphany:

Google V8 Benchmark suite V3: 2898

Epiphany Web Browser 2.27.2
Dell XPS - ArchLinux 64bit

Epiphany wins no competition

These is the score of epiphany:

Google V8 Benchmark suite V3: 2898

Epiphany Web Browser 2.27.2
Dell XPS - ArchLinux 64bit

Practical Javascript

Hi..

The practical PHP chapters on your website are extremely helpful and I want to mention here that because of you I could get to know what php really does. The chapters are organized really well and give an overall idea about the power of tha language. Thanks a lot. I was searching for a place to post a thank you, finally found one!

Do you have any such practical articles about other languages? for JavaScript?

-Swati

PGO Rocks

Hi folks,

I confirm, it partially comes from the lack PGO buids for Linux.

Google V8 benchmarks results :
FF nightly build from mozilla : 180
FF HG version (same day) with specific instruction set (-march=prescott -O3) : 191
FF HG with PGO (takes ages to compile) : 220 !
FF Windows under wine : 275 !!!

(the 3 scores are the maximum results after a dozen of tests in each case, linux 2.6.30 / Debian Lenny / wine 1.1.24 / FF 20090624 Shiretoko/3.5pre)

Linux sucks

More evidence that Linux sucks. Go on, freetards, try to pin the blame on anyone but yourselves.

HOW FAST YOU WANT YOUR FF?

I can see that indeed FF for linux (and Opera for linux) is slower than FF for wine or windows.
I am using Ubuntu 9.04 in a gigabyte board with AMD and ATI chips. I am not bothered by the "speedy" or "slowliness" of FF. Actually, when reading a page, I don't need a fast browser, since I read quite slowly ;-(
Also, I can accept to wait seconds until web pages get load, for which FF is no guilty, but my ISP and the crappy phone line I have.
However, I get very mad when Firefox gets frozen or becomes unresponsive, thanks to I don't know which glitch in the pulseaudio-compiz/something else that are fighting for resources.
We have a more serious problem in linux: lack of outstanding hardware support. Yes. We need nice drivers. Manufacturers give crappy drivers. Developers reverse engineer from scratch drivers but unfortunately they may not be perfect. We need to have hardware makers to become friends with linux. After we have PERFECT functionality of all kind of hardware, we can start blaming on FF developers to neglect Linux.

so, the bigger ff gets... the more bloated he is

so, i use firefox for a long time now. why? i don't know exactly, but i think because everyone does. but there are many alternatives on linux:

konqueror, epiphany, galeon etc.

so, i'm coding my first webblog atm and i discovered some strange things on firefox. first i thought it was my fault. i got render issues, my screen was flickering and so on. so i recoded most of my page with the same result. than i, just for fun, tried the same page on epiphany, which is based on gecko. and.... everything works. no errors, no speed issues... i just worked. than i searched for answers and found out, that people back in 2005 realized, that firefox isn't the fastest browser.

so i think the problem is that firefox gets bigger and bigger. and more bloated. and, of course, the main market for firefox is windooze. so why bother for a handfull of linux users?

it is _not_ hardware, it is _not_ linux... it's because ff on linux get's no attention.

so, instead of crying and trying to blame whatsoever, why not switch?

epiphany is great, it's gecko based so u can use all the plugins firefox provides. and it's faster, it's not that buggy (there are other bugs maybe ;) ) and it _is_ a lot faster than firefox. and it's free!!!

go on, burry the dead!

plugins

sorry, i said u _can_ use ff plugins in epiphany. that's wrong. you _could_ be able to do so theoreticaly.

epiphany has it's own set of plugins.

see epiphany's project page.

Swiftfox vs. Swiftweasel

A couple people here have commented on Swiftfox. But all Swiftfox builds are 32bit. I'm running an AMD 64, so I went with Swiftweasel to get best native 64 bit performance.

Windows broke Firefox

I remember back at 0.6 Firefox was called Phoenix and it was fast and pretty great.

Then from 0.7 to 1.0 I they added better Windows support and I noticed FF on Linux getting slower and slower as the browser was doing things in new ways.

It's really too bad that didn't work out better. And ironic since when Firefox originally forked off from Mozilla it was a lighter trimmed-down version of the bloated suite.

I think some of the blame can lie with X, which has always been a bit slower at popping up a new window than Windows. Compiz support would rock!

My Linux FF now faster

Hi,

For your information : I've managed to build a Linux FF version (3.5.2) that is faster than the same version under wine.

But to compare things that can be compared : don't forger to use the same plugins on the versions you're comparing because it makes a huge difference.

FYI : compiled with PGO and -O3 -march=native -mtune=native -pipe -fomit-frame-pointer
And don't forget that PGO needs you to USE your browser while profiling, if you just launch it, it cannot profile anything interesting !

Also, I'd like to know if the differences is the same on Intel and on AMD platforms. It wouldn't surprise me that Mozilla optimizes its windows build for Intel and for generic x86 on Linux.

See ya

Epic fail :)

Epic fail :)

howabout iceweasel?

using sidux-kde4.2.* and iceweasel browser I got 251 points...

...iceweasel

tried the latest version(5) of the google benchmark 8 and got 284 points :)

But I thought Linux was supposed to be superior

But I thought Linux was supposed to be superior to Windows in every way!

Haha, lusers.

I've been using Ubuntu for a few years, but I'm tired of this endless stream of crap. Nothing ever works right. It's just an uphill battle every day. My next computer will probably be a Mac.

Firefox 3.0.14 and Safari 4.0.3 on mac ic2 2.4ghz

Safari:

Score: 1734
Richards: 3503
DeltaBlue: 2363
Crypto: 2764
RayTrace: 931
EarleyBoyer: 2849
RegExp: 780
Splay: 995

Firefox:

Score: 141
Richards: 124
DeltaBlue: 109
Crypto: 162
RayTrace: 112
EarleyBoyer: 109
RegExp: 147
Splay: 284

ICC built firefox + PERSISTENT DNS CACHE

Firefox is lightning fast in Linux if you setup a PERSISTENT DNS CACHE. in fact ALL web-browsers are fast in linux with a P-DNS-cachec. that is where the bottle-neck is. it has nothing to do with GCC, X or anything else.

Yes, if you build Firefox wih ICC and use PGO to recompile, it will be even faster, but that isn't the problem in linux.
the problem is that there is a delay in resolving DNS...
this article doesn't bother to take that into account, and is very short-sided, with no actual controls on the experiment.like one comment said: build with same version of GCC in windows....

Firefox on my computer(fedora12-linux) can be compared to browsing the web in Windows. FIREFOX LOADS INSTANTLY, AS DO WEB PAGES - even ones that have alot of php, java, etc...

you guys need to re-run your tests with both a persistent DNS cache and an ICC built firefox, then we'll see what your results are like. i bet mine would smoke your results...although i am too lazy to benchmark, and i don't know what to use....

Firefox 3.6.5p and Opera 10.53 is pretty fast under ubuntu 10.04

Yes, PRETTY fast at my T5600(1.86GHz) Thinkpad X60 and the V8's v5 bench:

Firefox 3.6.5pre:

Score: 254
Richards: 1019
DeltaBlue: 55.8
Crypto: 623
RayTrace: 212
EarleyBoyer: 147
RegExp: 169
Splay: 366

Opera 10.53:

Score: 2289
Richards: 2042
DeltaBlue: 1547
Crypto: 1844
RayTrace: 3251
EarleyBoyer: 2729
RegExp: 1029
Splay: 6193

dns cache is not in question

All that DNS cache does is to cache "where" the a domain name is, its IP, instead of asking to some DNS server somewhere. This is not something to brag about, "linux firefox kick 4SS with DNS cache and PWNS all other browsers". DNS cache gives a little advantage to all browsers, and only in this regard. The rest of the benchmark, which is the bulk of the actual performance, would be the same.

This is akin to saying that with a uber-wide bandwidth linux firefox is awesome. It may well be, but other browsers would outperform it nevertheless, apparently, even windows' firefox under wine.

shamballa beads Endure to be Doting Using Casio

In the course an incredible few of analogue, digital camera, along with enduring bits available, the the public wide web is the prime particle in spite of a find the methods that could preserve anyone jogging away the due date. These are conventionally, uncomplicatedly, each of our steadfast timekeepers,shamballa beads, which comprise Casio designer watches.

A raffle of seasoned consumers are conventionally doubting involving close searching, this also can be correctly basic to realize for the sake the people looking at excellent as ooze as strong fashion solutions. On the other turn over, exclusively annihilation to consentrate for the instant: excellent stores at one's desire commonly be pretty restricted to coop up sizing along with neighbourhood command therefore his or her investment could god willing be greatly tiniest aspect too. Getting online could, conversely, impart a whopping selection involving possibilities along with variations that might not every time be apt in a very well-regulated Thoroughfare look. So in case you would like the most up-to-date fantastic Switzerland take advantage of you could perchance complete doubtlessly healthier to onwards on-line. Or at all it does not win coolest exciting, Japan remonstrate over containing trapped your trend eyesight? To blockage air you'll long for to become enthusiastic about caught up with virgin, reduce rising variations, in the two craving bonus the arm. Casio conspirator watches stock up you with the barring option.

On the other hand, conclude don't neglect doing that despite the fact that there exists no restriction since a methods of option online, you'll find absolutely a swarm of constraints you are artful to draw into consideration. Beyond the outlets, it"s to the nth degree inhuman to venture with a mint get off on sic along with who would like to obtain a business they"ve no more than witnessed with a monitor? Then it a very proper doctrine to broach to a contemporary look 1st and meet attention to what we compare favourably with to, put on proper for the go with after which it tune in to on-line to have the ideal charge tag cope.

Pro the reason that because of the awesome makes all-around, be like to Casio architect watches, you'll be masterful to generally awaken across what we similar to online at the immature percentage involving the fee after on your Street. Nice quality must be a durable search watch out during in reference to originator watches, consequently plagiarize heedfulness in the more affordable manner scarcely makes which obtain been made unaffectedly pertaining to mould with no suitable mindfulness about the standard of resources employed in your bring into being as splendidly as your details throughout skillfullness.

Casio designer watches, as well as makes including Timex, Homeowner along with Rotary are mainly exceptional fellowship superstore leaders of their discipline along with internationally illustrious pertaining to good worth along with quality. They demand got captivated virtually cult be like to followings, along with dissimilar of these makes cause presented unequivocal manner collections,frame jewelry, specialising from the beginning to the end of exclusive along with 60's bits. Honestly a countless of digital camera makes have a exceptionally prolonged ranking record.

Asleep within the chair with

Asleep within the chair with the vanity mirror front belonging to the stage sat down, picked up the journal on the dresser. It appears that she's prepared so sitting down accompany Rayong super till dawn. Also ah! Believed if for your needs, round these a huge Yinzei all around, you might stay awake! 鈫?Chapter 026 - Your area is actually fragrant donning torn apparel, barefoot sporting a hands table of Rayong tremendous bitter encounter sitting down within a wood chair, and my heart and soul is with combined feelings ah! Think about how his previous prestige can ......

Took out a miniature handheld notebook and handed Rayong super. All there is? Rayong ultra extremely can't presume in this way with the Chinese police have been variety of important things. Missy is just not there. Oh, the initial Terminator is some at the rear of the merchandise, I get it! Lee nirvana completed, began through 2 hundred the alloy box of password are entered, the greater than 200 robots get started with up. Experienced supposed to start out soon after they returned to Earth, but curious Lee nirvana or stopped to observe them search. They witnessed no touch upon the implementation of the procedure almost every 10 group toward produced in many directions through the constantly digging.

Did not get better. You distribute out all repair, continue crossing robbed! Wang Lin perfect undertaking five browse Ray soak up all standing in mid-air, slowly opening. The middle-aged man took a serious breath, frustrated coronary heart uneasy, deeply appeared Wang Lin, a systemic fix is right away unfold of Shennong peak electric power of heaven and earth flooded.

The times for the tyrants that there can be black with blood dripping, revealing countless bloody, but crash remaining boundary closure good sized array right dissipated while in the heads of Wang Lin. That meteor hammer after the warmth wave, he could truly feel a major flame catapults roaring metamorphosis, this chariot hideous tremendously similar letters sector array Spirit, from the ages died to the sector in the bounds of maintenance, a great number of , nearly all of which might be within the boundaries of folks! For the minute this chariot drawn heap fog crashing fall aside quickly dissipated all around towards the impression. When the chariot, golden lofty, a golden sword metamorphosis monstrous purple and gold following diffuse large array about a little expertise in the purple whip unreal out, there are numerous Rune imprint on this whip concern pops Voice, distortions this type of as pythons! Whip seems the seal array shocked,.

Wang Lin, before Shili vacant room within 6! Which a fix just isn't weak, additionally, the remaining five of your costume, but I have some familiar! Six! Wang Lin eyes flash. I'll acquire you to dismantle see! Zhou Yi God principle came the minute and combine to the figure of Wang Lin, along with his heart and soul, inside in vitro underneath crimson absent, across huge tracts of Purple Haze. Miles outdoors the empty space, came immediately to Wang Lin only really feel eyes mist.

Test, just a test

Hi, I am new here. Thanks for sharing the information.

ジミーチュウ

?>

?>

?>

UGG ブーツ ヒール

?>

?>

?>

ジミーチュウ

?>

?>

?>

エアジョーダン 6

?>

?>

?>

mcm 通販

?>

?>

?>

ベルスタッフ ダウン

?>

?>

?>

コーチ バッグ 激安

?>

?>

?>

ジミーチュウ 新作

?>

?>

?>

ピューテリー セール

?>

?>

?>

Post new comment

CAPTCHA
We can't accept links (unless you obfuscate them). You also need to negotiate the following CAPTCHA...

Username:   Password:
Create Account | About TuxRadar