IE performance for rendering huge html data

views:

answers:

+1 Q:

IE performance for rendering huge html data

I have a few perl CGIs which almost query the whole table with more than 5000 rows as result and send that data to browsers. The size of html data generated is around 1MB.

Earlier I was using tables(which should be ideal approach).

Unfortunately most users use IE and it does not display data till it receives closing table tag. Can we do something about it.

To push output as soon as its generated, I used another approach where in I was using printf and <pre>. Which reduced the response size by 200kb and and it appears more faster in display. Again IE (not any other browser) eats up CPU and hangs for couple of seconds... :-( .. Can we do something about it too. FYI I am using IE8.

More people use ie? http://www.w3schools.com/browsers/browsers_stats.asp

anyways why do you still use tables? we all know they are easy to maintain, easy to get confused and in your case slow...

output it as div which will show all the data and does not need to wait for a table tag to finish. as div and span have the least properties.

Val 2010-10-14 03:18:00

Different applications have different browser statistics. It depends entirely on which segment of the market the application targets.

mattbasta 2010-10-14 03:21:34

I know but still he had a bold statement :)

Val 2010-10-14 03:42:42

Let me give Div a try and see if it takes me to some conclusion. But question here is more with IE performance tweaking or some methodology which can help me in providing smooth response.

awake416 2010-10-14 03:59:03

:-( ... Use Divs for the purpose they are made. ..much slow response. that is not the solution.

awake416 2010-10-14 07:02:35

then go for the pagination option on the above answer.

Val 2010-10-16 14:58:08

+2 A:

Perhaps it would be wise from a UX perspective to use some sort of pagination method. Having a single page with thousands upon thousands of rows sounds entirely unfriendly for the end user. Something like a simple means of pagination ("Skip to page =dropdown=") would certainly solve your problem, as well as decrease load times and increase usability.

There are also several solutions which are pre-built and would likely integrate rather easily. One which comes to mind almost immediately is Sencha's Paging Grid:

It's pretty nifty and you'll likely get some kudos for using a hip new technology. There are other options, too:

Ingrid: http://www.reconstrukt.com/ingrid/src/example3.html
YUI Data Grid: http://developer.yahoo.com/yui/datatable/#data
MyTableGrid: http://pabloaravena.info/mytablegrid/

Hope this helps!

mattbasta 2010-10-14 03:31:21

I was thinking about pagination aswell but if someone is using tables still i don't think s/he would of known what it meant :)

Val 2010-10-14 03:46:04

Yes That is best solution, But Unfortunately, due to restrictions on legacy product, we can not use much javascript libraries etc...I do not like it but I have to live with it till we upgrade this application.

awake416 2010-10-14 03:56:26

ansaurus

tags:

views:

answers:

IE performance for rendering huge html data

related questions