Web Browser Grand Prix: Chrome 25, Firefox 19, And IE10

Page 4 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
Status
Not open for further replies.
As a bit of a note, I have just tested the Microsoft Maze Solver, and Firefox's completion times have increased since last time. (I know that Firefox has a bug with the Maze solver, but it might be fixed now?)
My test results: Chrome 26 completion time: 2.3 seconds on 30x30 maze, 6.5 seconds on the 40x40 maze.
Firefox gets completion times of 8.6 seconds and 24 seconds respectively - although Firefox is slower, it is definitely quicker than before (I remember when it took over a minute for Firefox to complete it!) This is on a Intel i5-480m processor, 6gb ram and windows 7 home premium.
 
Oh yeah, and may I add that Chrome is now having problems logging into Tom's site. When I tried to log in, it wouldn't, even though I was using the correct details, and trying to submit a comment was nigh-on impossible. Change password etc didn't help - I had to use Firefox instead - good job I have a backup browser(I am typing this with Firefox). The old Tom's site had no problems at all with Chrome - so is this a ploy to get me to change to Firefox? If it is, thn it won't work for me, and I will be forfeiting my Tom's account instead of my Chrome browser.
 



Sounds more like a bug in the new Chrome that broke compatibility.
 
For the 40 tab test, are the tabs opened from within the first tab (e.g. middle or control click) or are they opened as completely separate tabs (e.g. +T or the '+' button on the tab bar)? It makes a difference in Chrome. The first method runs the new tab in the same process, where the second method spawns a new process in Chrome.

The first method would see lower RAM usage for all 40 tabs, but the second method would do a lot better once the 39 tabs are closed. Since it has killed off the processes, there would only be room for bloat in a memory segment shared among multiple processes or a resource pool. The distinction becomes important when you're going through a page and loading a few dozen links into new tabs. If they're all in the same process the CPU usage doesn't scale to multiple cores, unless they've fixed something I didn't notice.

I probably open and close 1000+ (maybe 10,000+) tabs a week for several weeks before restarting my browser. I remember FireFox would eat as much as 4GB of RAM before I closed it. That was around the v4.0 days or so. I know it's gotten better, but I'm opening a and closing lot more tabs now. Since I now have a lot more services running as websites, I really want something I can leave open. With current memory densities and prices, it's easy to get plenty of RAM for 100's of tabs, and it isn't too difficult for me to manage them (Chrome, multiple monitors, multiple desktops on a cube). Maybe the 40-tab test should be expanded 100-1000x.
 
Mr. Overa,
there is something fishy on page 4 - Startup time. On Win7, IE9 beats Chrome in each of the four subresults, yet the arithmetic mean graph shows their order reversed. How come?
 
Am I the only person who is concerned that these benchmark tests are being conducted on a docsis 2.0 mdm, and a router that is several years out of date?
 
Thanks for the helpful review.
IMO, Google Chrome is not just very good is performance, it is also simple to use. Internet Explorer, once the king of the browsers, is constantly jumping the shark and now it's market share is far below Chrome
 
Status
Not open for further replies.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom