Web Browser Grand Prix VIII: Chrome 16, Firefox 9, And Mac OS X
-
Page 1:Web Browser Grand Prix VIII
-
Page 2:Chrome, Firefox, Internet Explorer, Opera, And Safari
-
Page 3:WBGP VIII Test Setup
-
Page 4:Startup Time Performance Benchmarks
-
Page 5:Page Load Time Performance Benchmarks
-
Page 6:JavaScript Performance Benchmarks
-
Page 7:DOM And CSS Performance Benchmarks
-
Page 8:Flash Performance Benchmarks
-
Page 9:Java And Silverlight Performance Benchmarks
-
Page 10:HTML5 Performance Benchmarks
-
Page 11:Harware Acceleration Performance Benchmarks
-
Page 12:WebGL Performance Benchmarks
-
Page 13:Memory Usage Efficiency Benchmarks
-
Page 14:Memory Management Efficiency Benchmarks
-
Page 15:Page Load Reliability Benchmarks
-
Page 16:Standards Conformance Benchmarks
-
Page 17:Benchmark Analysis
-
Page 18:Crowning Two Champions In Windows 7 And OS X
Memory Usage Efficiency Benchmarks
Light Load

IE9 uses the least amount of memory to display a single tab under Windows 7, just under 50 megabytes. Apple Safari comes in second place, using just over 50 megabytes, followed closely by Opera. Chrome places fourth, consuming nearly 65 megabytes, while Firefox uses the most memory (90 megabytes), placing last.
Safari leads in OS X at just under 60 megabytes, followed by Opera at just over 70. Firefox overtakes Chrome to place third by using 120 megabytes, while Google's browser uses the most memory (140 megabytes).
Heavy Load

Under a heavy load of 40 tabs, Safari for Windows uses the least amount of memory (just 725 MB). Firefox comes in second at 910 MB, followed closely by Opera at 925 and Chrome at 995. Microsoft's own IE9 uses the most memory (1.75 GB).
Opera is the only competitor to use less than a gigabyte of memory in Mac OS X. Safari comes in a close second, eating just over 1 GB, followed by Firefox at 1.25 GB. Chrome reports a whopping 2.3 GB of usage with 40 tabs open, which is significantly more than any other browser.
- Web Browser Grand Prix VIII
- Chrome, Firefox, Internet Explorer, Opera, And Safari
- WBGP VIII Test Setup
- Startup Time Performance Benchmarks
- Page Load Time Performance Benchmarks
- JavaScript Performance Benchmarks
- DOM And CSS Performance Benchmarks
- Flash Performance Benchmarks
- Java And Silverlight Performance Benchmarks
- HTML5 Performance Benchmarks
- Harware Acceleration Performance Benchmarks
- WebGL Performance Benchmarks
- Memory Usage Efficiency Benchmarks
- Memory Management Efficiency Benchmarks
- Page Load Reliability Benchmarks
- Standards Conformance Benchmarks
- Benchmark Analysis
- Crowning Two Champions In Windows 7 And OS X
I think add ons are much easier to find with FF, and there seems to be a wider variety. Then again I do realize this article wasn't about browsers with add ons.
Yes, we're using everything stock. There is no one-size-fits-all combination of plug-ins to standardize on, and every browser might not have the exact same plugins available. So that throws out a fair comparison between browsers - wouldn't work for the WBGP. Perhaps an article concentrating specifically on Firefox (or another Web browser) with and without various plug-ins would clear that up?
Why do people seem to forget Chrome has this built in. All you have to do is go into the options menu and disable JavaScript.
i know i know, chrome is faster, has market share, ie 9/10 are coming up, blah blah. but ff can still fight. google's benevolent (read: to antitrust-pacifier) fund injection should help ff. besides, chrome is a sneakware bundled with numerous softwares. ff has scriptblockers that block statcounter.
Thanks for the feedback, and good catch. I must have goofed and started making the graphics with an older file when I already had the newer one. Doh! It's all fixed now, and it should update momentarily.
Firefox can do the same with tab mix plus. I couldn't live without scrolling though my tabs.
Just like VHS vs Beta, NTSC vs PAL or Gasoline vs Electric... just because the public likes something does not mean it is the best solution.