Adhoc Browser Performance Testing (IE8, Google Chrome2, Firefox3.5) - Round 2 (with SSD)

This time I tried with IE8 and entirely different system again I used the same link to see the performance http://ideamill.synaptrixgroup.com/jquery/tablefilter/largetabletest.htm

(I also open/close the borwser few times to bring all the moving parts close to the heart of OS -:) )

	Chrome2	IE8	Firefox3.5
Loading the above link button – iteration 1	0.5 sec	1.6 Sec	1.2 Sec
Loading the above link– iteration 2 (Close the browser, reload it again)	0.5 sec	1.7 Sec	1.1 Sec
Clicking GO button – iteration 1	1.9 Sec	Broken and it took 5.5 Sec to hide the table and stopped rendering the table below “Go” button. I tried compatible mode but it also didn't help.	4.3 Sec

For the kick, I checked with iPhone OS3.0 safari, It took 0.5 sec to show few rows and tool almost 3.5 minutes to render the entire page. I also checked it render all the rows. I tried to click the "Go" button, It did not work. Though it is not bad as it is not meant for this kind of load.

System used:

Core2Duo 3 GB DDRII RAM

Gskill Falcon 128GB SSD

All the test ran on the same system.

Disclaimer:

I considered Network latencies, Network congestion etc would be same for all the browser

as it is tested on the same system. You can still use the given Link to try it yourself.

Adhoc Browser Performance Testing (IE, Google Chrome, Firefox)

I came across complex requirement. Here is that,

It is huge grid table with context menu, filter, sorting etc, no of rows goes beyond 1000 and column is more than 16. I found Ext JS’s Grid is used. It is taking almost a while to load completely. It is really slow and it feels as if CPU 100% utilized and no memory is available. I wanted to picture the problem; here is the test something similar to my requirement http://ideamill.synaptrixgroup.com/jquery/tablefilter/largetabletest.htm

	Chrome2	IE6	Firefox3.5
Loading the above link button – iteration 1	1.6 sec	2.3 Sec	1.8 Sec
Loading the above link– iteration 2 (Close the browser, reload it again)	1.5 sec	1.8 Sec	1.9 Sec
Clicking GO button – iteration 1	3.1 Sec	25.5 Sec	6 Sec
Clicking GO button – iteration 2	3 sec	25.2 Sec	6.1 Sec

Note: I used iPhone stop watch to test it. Though it is not fair to compare when IE 8 is out, but I have to work with IE6. I am interested in last 2 rows. Even with the margin of 0.5 sec error, Google chrome and to some extend the firefox3.0 gouged the IE.

System used:

Pentium D 3.0 GHz, 2 GB of RAM

All the test ran on the same system.

There are 2 things should happen,

IE should die including IE8 or it should reinvent itself for betterment of community. Microsoft should not punish the community and enterprise. Please do Microsoft....

My experience using Google's Chrome

Today I downloaded google's chrome browser. It is natively integrated with google gear tightly. Address bar is now have dual role and serve as search bar too and its start of end of address bar and search is going to prevail (look at URL is dead ). Short cuts are cute and powered with Google gear - makes its awesome. "Most visited" page when I open the browser is good and resembles googly.

Featurtes

-------------

1. Open link in a new tab : (Right Click on link - context menu) The order of Open link in a new tab is changed from both IE (Internet Explorer and Firefox) it is placed first ahead of "open in new window" it is heavily used features and causing litle bit of experience realignment issue. I did not change any setting as I used out of the box installation, though.
2. Awesome bar/ Omnibar : It looks good and simplifies the job of using 2 different boxes for achieving the same thingy (though, it seems overstated by saying address bar and search bar are doing same job but my real world experience is saying it is singular activity, look at URL is dead....
   

Hm I am not covering everything in it in a single shot but describe about it frequently as and when I find it and to say something about it.