Greetings,
I am a relative newcomer to ASP.Net AJAX. So hopefully the answer to this question will be quick and easy.
I've created a CascadingDropDown list that gets store locations based on the company. In some of these datasets there are as many as 6,000 - 10,000 records that need to be loaded into the TargetControl. This ends up being quite a lot of data. I was having problems with this origanally because of the default maxJsonLength in my webconfig which I've now corrected.
The TargetControl now gets loaded and it works with this one exception: For queries with exceptionally large datasets the client is taking up to 30 seconds or more to load the target control. I did caching on the server side in the webservice to cache data sets and that doesn't seem to be the problem. I've done some analysis with Fiddler v2.0 and it appears that the round trip request/response is taking only about a 5th of a second (see capture below):
Request Count: 1
Bytes Sent: 545
Bytes Received: 701,964
ACTUAL PERFORMANCE
-----
Requests started at: 13:58:38:1621
Responses completed at: 13:58:38:3496
Total Sequence time: 00:00:00.1875024
RESPONSE CODES
-----
HTTP/200: 1
RESPONSE BYTES (by Content-Type)
-----
~headers: 239
application/json: 701,725
So the question is: why does it take the CascadeDropDown control so long to load the data? What is client doing for the other 29.8124976 seconds?
When I did this web app in ASP.Net 2.0 (without AJAX), it was taking 2- 3 seconds max for these large data sets to load doing direct databasecalls.
Any help would be appreciated.
Thanks,
Scott Lance
Application Developer
Children's Miracle Network
I have the same problem in my application. Large sets of data are not uncommon in the large applications.
Can anybody, please, take a look at this
No comments:
Post a Comment