Last post Apr 13, 2010 05:06 PM by Slick86
Apr 03, 2010 09:19 PM|Slick86|LINK
I am currently working on a page that has 13 gridviews in it. Each one is in a control and a separate updatepanel. The time from link click to page load is 20 seconds though and I am looking for ways to load the controls asynchronously so that the page
can load and then the data can come after. I have tried a few different methods so far but have been unsucessful so far. I thought about using the Ajax incremental page display pattern but I did not think this would work because it only returns html. I need
to load the gridviews in and they need to support pagination and sorting. Any ideas? Thanks.
Apr 04, 2010 02:09 AM|Das.Sandeep|LINK
however Yow can make it sync by doing this way use workertheaditem and bind your gird there after we run thraed just use WaitHandler class
to wait that thead to finish before we bind another grid
i hope this will help everyone to make asyc cal forcfully sync
For more details find TheadPoolManager class in MSDN
you will get how to use it and then find for WaitHandle class that will help you get how current thread will wait while other thead will finish
ensuse thread and we will call set method on handler only when we will get response.
try it out.
Apr 05, 2010 04:56 PM|atconway|LINK
I am currently working on a page that has 13 gridviews in it. Each one is in a control and a separate updatepanel. The time from link click to page load is 20 seconds
This does not surprise me at all. The AJAX UpdatePanel is kind of a double edged sword when it comes to performance in my experience. Using them sparingly to asynchronously manipulate controls works well, but once too many are added to the page, or they
have their triggers improperly configured and you will have a mess on your hands and a really slow page. Now the next (2) sites are a bit on the extreme basically stating to
not use them which I don't all together agree with, but it does have some valid points. Most don't realize that an UpdatePanel goes through the full page lifecycle on the server even though only a portion of the ViewState is actually modified giving
the asynchronous change feeling. The 1st post explains how using JSON as an alternative as a much lighter mechanism for the same end goal. They also explain the underwokings of the control and why you are having performance issues:
Why ASP.NET AJAX UpdatePanels are dangerous:
Why you should not place your whole site in an UpdatePanel:
Lastly, check your ViewState to make sure it is not getting out of hand; 13 GridViews is a lot on a single page. Use the ViewStateHelper tool to help analyze your pages:
ASP.NET ViewState Helper:
Hope this helps!
Apr 06, 2010 12:23 AM|Slick86|LINK
My viewstate right now is about 25k. It was really bad before. I inherited this code and the viewstate was over 100k which was ridiculous. I really like the use of JSON with Page methods and actually used them today, but how would I implement these with Gridviews?
Or would it be best to just create tables dynamically? I would love to get rid of the update panels right now but we use a tabpanel to hold all of the gridviews and having the postback flicker is not an option
Apr 06, 2010 10:56 AM|atconway|LINK
I really like the use of JSON with Page methods and actually used them today, but how would I implement these with Gridviews?
I would seek out the help of the AJAX forums and also check out the following links:
Apr 13, 2010 05:06 PM|Slick86|LINK
Thank You! I will try this out