Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
My web application I am creating features a lot of grids, and one baffling requirement is that it needs to be able to show a GridView, which sometimes has over 1000 rows, all without paging and in within one scrollable panel. The column count is also large, with around 20 on there.
The query isn’t too slow, but the slowness seems to come from the gigantic size of the HTML source being displayed. Are there any methods of reducing the size of the source file?
As Davide mentioned, paging is essential. If server resources are cheap, you could consider
1) Removing whitespace from the html using a response filter. There are standard modules available. A quick search leads to sample module
2) Enable gzip compression on IIS for dynamic content
But, the slowness may not be due to the size of the html. Some other things to watch out for:
1) Inefficient Javascript manipulating the DOM, esp on document load\ready.
2) Enabling caching headers for static resources (these are turned by default on IIS)