M
Micah N
Greetings,
I have been searching for some info on why the DataGrid control takes soooo
long to draw to the screen with large datasets.
I have a simple report that has a lot of searching capabilities for
returning a small dataset. But when I return all records, 10,000 ( with 20
fields ), the HTML takes over 30 seconds to draw to the screen.
This aspx page, is a DataGrid being bound to a DataSet. In its most
simplest form. Small datasets draw fast, sort fast, etc.
Now then, I have some other old ASP pages that I have converted to ASPX.
One scenerio is a page ( ASP ) that you can search for an Employee.
Returning all Employees ( ~4000 records ) takes ~2 sec. The ASP code is the
traditional get the RecordSet and loop through it creating the HTML table.
The exact same page using a DataList being bound to a DataSet takes ~10 sec
to draw to the screen.
I just want to know if other users have experienced this. Is there a way to
force a "Response.Flush" type action on these controls? Is it common
knowledge that we are giving up speed for programming convienience.
Or maybe my web server is out of tune? I do not know. I have no other
benchmarks.
thanx
Micah
I have been searching for some info on why the DataGrid control takes soooo
long to draw to the screen with large datasets.
I have a simple report that has a lot of searching capabilities for
returning a small dataset. But when I return all records, 10,000 ( with 20
fields ), the HTML takes over 30 seconds to draw to the screen.
This aspx page, is a DataGrid being bound to a DataSet. In its most
simplest form. Small datasets draw fast, sort fast, etc.
Now then, I have some other old ASP pages that I have converted to ASPX.
One scenerio is a page ( ASP ) that you can search for an Employee.
Returning all Employees ( ~4000 records ) takes ~2 sec. The ASP code is the
traditional get the RecordSet and loop through it creating the HTML table.
The exact same page using a DataList being bound to a DataSet takes ~10 sec
to draw to the screen.
I just want to know if other users have experienced this. Is there a way to
force a "Response.Flush" type action on these controls? Is it common
knowledge that we are giving up speed for programming convienience.
Or maybe my web server is out of tune? I do not know. I have no other
benchmarks.
thanx
Micah