 Posted 11/28/2011 5:18:06 AM
|
|
|
|
MGinAction is very, very slow. I suspect this is mostly to do with what .Net calls the ViewState.
Each page is about 1/2 a megabyte. This is terrifically huge. Especially because each time we use a form on the page this mass of data in the viewstate is being submitted back to the server. I promise if engineer the viewstate out of your application it will be much, much faster. The viewstate is really handy, but very poorly performing.
Here is a fantastic article explaining all about the viewstate.
http://weblogs.asp.net/infinitiesloop/archive/2006/08/03/Truly-Understanding-Viewstate.aspx
Cheers,
-Patrick Te Tau
|
|
|
Posted 1/2/2012 9:23:30 PM
|
|
|
|
They do have viewstate enabled. If they're not actually using it for postbacks etc I agree they should disable it. Since they're using jquery, I'm guessing they could probably turn it off since it's probably more ajax than classic asp.net postbacks.
However, the viewstate payload isn't actually that big. Take a random page:
http://www.mginaction.com/VideoDetails.aspx?VideoId=9774
The viewstate for that page is only 221k.
But -- you're right -- the overall payload is large.
If you run it through Firebug and look at the totals in the "net" tab results, that page weighs in at 198 requests (!) and 3.6MB total which is actually much larger than the 1/2mb you mentioned.
So, just at a glance, I'd say turning off viewstate wouldn't help. I'd start by evaluating overall page construction + response time of individual items. I'm guessing WebResource.axd is dragging and there are unnecessary calls to ScriptResource.axd (maybe something like including Telerik controls that aren't actually used)
That said, it's actually not that slow for me 
|
|
|
|