Run this simple test inside your browser of choice...

Win 7 64 bit rtm build

Chrome 3.0.195.27:

http://www.shrani.si/f/20/yB/27872hmN/chromepng.png

FF 3.5.4:

http://www.shrani.si/f/3G/vZ/4VJoQexd/ff.png

IE 8:

http://www.shrani.si/f/46/n5/HUkr8Ur/ie.png

All tests successful, 1 subtest skipped with FF in Sandboxie. Of course, I had to allow the JS with NoScript first. :wink:

Google Chrome in a runaway lead for browser performance supremacy, which is the recent Beta News browser speed test results. There are even comparisons between Windows OSes.

Another aspect of these tests which we, end-users should note is that developers are very aware of the influence over them and that they seem to be trying to get better scores.

Mozilla's team has been making efforts to better Firefox' control flow scores, evidently knowing how much they influence test results like ours. The evidence comes from the latest daily builds of Firefox 3.7 Alpha 1, on the "Minefield" track, whose [b]control flow[/b] scores recently quantum-leaped down to 8 ms.
There are certain things that Chrome does where the score differences are factors of 10, where one might get the impression that Google is improving Chrome just to score better with Betanews (the company has been expressing its interest to us directly in recent days) or more likely, with its own internal test suite. Indeed, the company's V8 benchmark suite would have users thinking the browser is hundreds of times more capable than its competition -- a claim for which we just don't see the practical evidence just yet, which is why V8 isn't part of our tests.

BTW, yet another aspect that makes things unnecessarily complicated is that end-users’ fanboy/galism about their favorite applications, including OSes. Too much enthusiasm of other users makes it tough to look things straight. We have to rely on various second opinions from various sources. I admit that I am biased, too, but I’m trying to be neutral when giving information since I know it’s hard to find info rather than biased opinions on the net.

You can find lots of info on the net but they are are all biased one way or another.

Maybe I should join the Exciting World of BiomedExperts?
http://www.biomedexperts.com/Abstract.bme/10794372/Biased_information_search_in_group_decision_making

What do you think of the Windows OS-based comparisons, considering your arguments about OSes while back? You can try to make fool of the others but I wonder whom you actually end up with fooling. :frowning:

Can someone give me an idea about why there is the disparity between different browsers in some tests. Although I only use two, I found them both very similar in XP. Both around 6 and a half seconds. I haven’t tried Vista SP2 yet. ???

RoRo

Hi malware fighters,

Do not forget, my good friends, that IE8 is becoming slower and slower all the time because of all the patches: Internet Explorer 8 is becoming slower with every patch (and we cannot do without them), this is shown by various benchmarks. The browser is only 1,5 times faster as IE7, at the moment IE came out it was three times as fast as IE7.

Betanews tests show that IE8 becomes slower and slower after each patch-round while other browsers will get only faster and faster. The performance of IE8 is going down under the patch-load…

Since the monster patch of Tuesday, Oct. 13-th the performance of IE7 was 1,54 times as fast as IE7 on a Vista SP2. While the last JavaScript-update was only for XP and Vista, IE8 performs best on Windows Seven.

For the browser results here it is important at what moment the tests are performed, as the browser is launched, after half an hour, with loads of tabs open, the number of extensions or objects etc.

In Benchmarks GoogleChrome performs best, wondering what their OS will be doing, can’t wait to see it…

pol

It’s because of these disparities between all the browsers that I keep coming back to Google’s Chrome.
I don’t have the time to wait on the others. :slight_smile:

Here is Lifehacker’s test on the browsers on Windows 7.

I thought polonus or someone who is more knowledgeable about what the test is really doing could give you a picture… What I noticed is that the results can vary depending on the settings of the browsers, which is why I felt the needs of a more professional take on this one. I hope Beta News’ test would give you a bigger picture. As as side note, you might be interested in testing your browsers on Mozilla’s Dromaeo site, introduced in Lifehacker’s test above.

Bit off topic but Here coming another Android cell phone from a well-known maker although it seems to be still struggling to be completed.

async.js… ok
bad_plan.js… ok
buffer.js… ok
builder.js… ok
builder_death.js… ok
circular_data.js… ok
curr_test.js… ok
details.js… ok
diag.js… ok
instance.js… ok
jsan.js… ok
harness.js… ok
more.js… ok
output.js… ok
simple.html… ok
simpler.html… ok
simple.js… ok
test_result.js… ok

All tests successful, 1 subtest skipped.
Files=18, Tests=294, 3.576 seconds

Sandboxed Firefox 3.5.5 Xp Pro Sp3 32 bit:

All tests successful, 1 subtest skipped.
Files=18, Tests=294, 2.863 seconds

Sandboxed IE 8, XPpro Sps3 32bit:

All tests successful, 1 subtest skipped.
Files=18, Tests=294, 2.938 seconds