Commentary

Thomas Claburn
 

Mozilla Fires Back At Google: Our JavaScript Engine Runs Faster

Everyone's running speed tests to see how Google's new Chrome browser measures up.

Everyone's running speed tests to see how Google's new Chrome browser measures up.Google during its launch event tested Chrome against Microsoft Internet Explorer 7 and found that Chrome (77.28 milliseconds) was about three times faster loading local static page files than IE (220.64 milliseconds).

I used WebWait.com to test how quickly Chrome 0.2, Firefox 3, Safari 3.1, and Internet Explorer 7 loaded the InformationWeek.com home page. The results for three page loads averaged were: Firefox (5.21s) Safari (6.34s), Chrome (6.48s), Internet Explorer (8.90s).


More Internet Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

CNET's Stephen Shankland ran a series of JavaScript benchmarks designed by Google and found that "Chrome clearly trounced the competition." ZDNet's Ed Burnette ran the same test suite and found that "Chrome is 42x faster than IE7, 9x faster than FF3."

LifeHacker tested browser startup time, JavaScript & CSS, and memory usage for Chrome, Firefox, and Internet Explorer. Chrome for the startup test, Firefox and Chrome tied for JavaScript test, and Firefox won the memory test.

Not to be outdone, Mozilla CTO Brendan Eich posted data from a speed test that pitted Chrome's V8 JavaScript engine against Mozilla's new TraceMonkey JavaScript engine, which should appear in Firefox 3.1. The results: TraceMonkey was 1.28x faster than Chrome's V8 running under Windows XP (on a Mac Mini) and 1.19x faster when running under Windows Vista (on a MacBook Pro).

"Maybe we should rename TraceMonkey 'V10' ;-)," Eich quipped.

As always with such statistics, your mileage may vary. The real test is whether Chrome meets your needs and whether you enjoy using it more than other browsers. Personally, I'm going to stick with Firefox, at least until Chrome plug-ins start appearing.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links