PaulSpoerry.com

With so much being said about Google Chrome’s performance (I’ve played with it… it IS fast), everybody started wondering about FireFox’s reaction. After all, it has been the golden boy as of late. The question on everyone who’s a follower of FireFox beta’s is how does the new beta Google Chrome browser stack up against the beta 3.1 FireFox release in JavaScript performance. Note… BOTH of these are beta releases.

Here are the results from head-to-head SunSpider on Windows XP on a Mac Mini and Windows Vista on a MacBook Pro, testing against last night’s Firefox automated build and yesterday’s Chrome beta:

The entire results of the test are worth looking into as they provide where V8 (Chrome) excels versus TraceMonkey (FireFox) in JavaScript performance.

Get the full scoop here.

The Acid test,  tests how well a browser complies with a given set of Web standards. Acid2 tests a variety of web standards published by the World Wide Web Consortium and the Internet Engineering Task Force.

Harrison Hoffman, co-founder of LiveSide.net and contributor to the CNET Blog Network is reporting that Google’s Chrome browser is outperforming the latest “stable” builds of both Firefox 3 and Internet Explorer 7 in the popular Acid3 test. All the browsers tested pass the Acid2 test. However, the only currently released browser to beat Google’s Chrome browser was Opera, which scored an 83. FireFox scored 71 and IE scored 14, whereas Google’s Chrome (which is still beta) hits a 78 out of 100.

Developer builds however, including Firefox 3.1 Beta 1 (85), Opera (91), and Safari 4 (100) do beat out Chrome.

Read the full details over at CNET.

CNET ran benchmarks on the newly release Google Chrome browser. It turns out that not only does Chrome beat the competition, it completely annihilated them.

Here’s the site description of the speed tests:

• Richards: OS kernel simulation benchmark, originally written in BCPL by Martin Richards (539 lines).

• DeltaBlue: One-way constraint solver, originally written in Smalltalk by John Maloney and Mario Wolczko (880 lines).

• Crypto: Encryption and decryption benchmark based on code by Tom Wu (1,689 lines).

• RayTrace: Ray tracer benchmark based on code by Adam Burmister (3,418 lines).

• EarleyBoyer: Classic Scheme benchmarks, translated to JavaScript by Florian Loitsch’s Scheme2Js compiler (4,682 lines).

Get the full scoop over at CNET.