the page takes so much time to load if the gridview contains more records

Question

1.00/5 (1 vote)

See more:

Dear All, I am facing a problem.

The problem is that, i have a simple aspx page with a gridview and two dropdowns for State and Districts. On page load within !ispostback the gridview is binded with about 3000 records from database. On selectedindexchanged of State dropdown the district dropdown is binded (gridview is not binded this time). But it takes so much time to populate the districts.

But if in the pageload, the gridview is binded with 100-200 records (selecting 100-200 records from database) in that case the district is populated within a second.

I cannot figure out what exactly the problem is.So Please help me.

Posted 19-Jun-15 4:07am

sunilsourav

Add a Solution

Comments

virusstorm 19-Jun-15 10:38am

Your problem is you are binding 3000 records. This is a lot of data to bind and display. You need to implement paging.

sunilsourav 29-Jun-15 10:20am

Hi,Thanks a lot for your suggestion. Now i have resolved it by extracting only 10-20 records at a time with dynamic paging implementation.

2 solutions

Solution 2

I suggest you to build your grid view along with bootstrap data table plug-in. https://datatables.net[^]

This will automatically handle paging, sorting and filtering. Also very quick. Give it a try.

If you can't avoid asp.net view state try using bootstrap data table or else do paging instead of loading all data at once.

Posted 19-Jun-15 20:18pm

Sreekanth Mothukuru

Comments

sunilsourav 29-Jun-15 10:18am

Hi,Thanks a lot for your suggestion. Now i have resolved it by extracting only 10-20 records at a time with dynamic paging implementation.

Sreekanth Mothukuru 30-Jun-15 0:41am

You're welcome!

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2015-06-19T04:50:00

Solution 1

The simple solution is: don't try to load so many records.

Of course it takes time to load: 3000 records is a lot of text to pump across the internet (with appropriate HTML wrapping). And to make things worse, do you expect your users to find their record easily in that lot?

Only ever populate a user control with around 100 rows at most, and provide paging, searching, and filtering: it's faster, easier and a lot more user friendly!

Posted 19-Jun-15 4:50am

OriginalGriff

Comments

Richard Deeming 19-Jun-15 11:37am

Not to mention the time it takes to post the ViewState back to the server, and for the server to deserialize the state and re-hydrate the 3000-record GridView and all of its child controls! :)

OriginalGriff 19-Jun-15 11:41am

But...but...it's easy for me to codezzzzz!
:laugh:

sunilsourav 29-Jun-15 10:20am

Hi,Thanks a lot for your suggestion. Now i have resolved it by extracting only 10-20 records at a time with dynamic paging implementation.

OriginalGriff 29-Jun-15 10:34am

You're welcome!