HTML5 and Page Size reduction - My Perspective

AT&T network serving 16 petabytes of Data each day http://en.wikipedia.org/wiki/Petabyte
This is not 100% HTML content it includes video/audio other media type content. I found based on html5 new tags, the size of the page can be reduce upto 50% of the total mark up size. What it means is using concise tags eliminate unnecessary markup like extra html tags and CSS and otherstuffs. And also two important media tags Video and Audio would reduce plugin code (it may be one time + some other extra stuffs) It would be huge boon to network. Websocket will enable easy push feature and binary data transfer which also will play friendly to payload. So ultimately new version html (html5) will need less mark up to achieve same effect and also some time less extra enabler code. Size reduction is mainly due to as I said above, Since reduction in html code to achieve same look and feel will ease the Search engine parsing -- it also saves power cost and hence environmental friendly --- connecting loose ends. One more side effect would be performance improvement on the browser as browser needs to parse, understand and apply style etc to only few elements.

1. New html tags so less mark up
   
2. New media tag - video and audio so less dependency need for using media
3. Websocket -- duplex communication eliminates unnecessary round trip and concise data transfer
   
4. Improved browser performance
   
5. Search engine friendly -- less markup to parse and no proprietary plugin to understand
   
6. Less power usage - markup generation and Search engine content parsing
   

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....