{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 孤傲高冷的网名 的问题《Why is IE7 so slow compared to Safari?》','https://www.manongdao.com/q-939198.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I have a large "grid" of data that takes about 40 seconds to generate and dump as plain text. If I wrap the text with html table formatting (with fixed td widths) it takes over 200 seconds to completely display in IE7, and under a minute to display in Safari. Small "grids" display in under 5 seconds in either browser, so I don't think it's related to anything other than data volume. Is there anything I can do on the server side to speed up IE7 display? Telling the users to stop banging their heads against the wall is not an option.
相关问题
- How to fix IE ClearType + jQuery opacity problem i
- Faster loop: foreach vs some (performance of jsper
- Why wrapping a function into a lambda potentially
- Is TWebBrowser dependant on IE version?
- Ado.net performance:What does SNIReadSync do?
相关文章
- Safari blocks play() on video despite being called
- IE/Edge not applying transform: translate to table
- DOM penalty of using html attributes
- Which is faster, pointer access or reference acces
- Django is sooo slow? errno 32 broken pipe? dcramer
- Number of Javascript lines executed during page lo
- Understanding the difference between Collection.is
- What is the definition of HTTP_X_PURPOSE?
Even the Safari "under a minute" seems unbearable. Wherever I have anything that slow I put up a progress bar and some stats about the data.
Kazar's pagination idea may be the way to go, or progressive loading as Oscar Reyes suggests.
Just how many rows and columns is this data that it takes that long?