Hi

We've noticed that various sites that we've migrated to DNN 6.0.0+ (DNN 6.1.5, DNN 6.2.2) perform horribly in admin mode.

The Page Managemer seems to be especially slow. We have several large sites (1000+ tabs) where the Page Manager is unusable for our clients. Load times exceed 10 seconds.

On top of that, we have very high memory usage (sometimes over 500MB!) in virtually all of our sites that run DNN 6.0.0+

 We've tried pretty much everything (caching, app pool settings etc.) - No dice.

 Thanks for your answer. We'll probably have to at least replace the control panel. 

I think websites with over 1000 pages are not unheard of and pretty common, especially in the enterprise space. In fact we have many websites that run on DNN that have over 1000 pages and that are still on versions below 6.0.0. DotNetNuke should be able to handle such scenarios in my opinion. At the moment the site administrators of the sites we've already updated are begging us to downgrade.

Actually, there are several reasons why this user control is so slow, all of them having to do with bad design.

 First, the protected property Tabs is reference often in the ascx file.  See its definition here:

 protected List<TabInfo> Tabs
        {
            get
            {
                return TabController.GetPortalTabs(rblMode.SelectedValue == "H" ? Null.NullInteger : PortalId, Null.NullInteger, false, true, false, true);
            }
        }

 Exactly... Every time it's referenced, the GetPortalTabs method is called.  That means, for example, every time AddChildNodes is called (which is called for each and every node).  For my site, that means over 1000 times on a page load.

Just fixing this issue will be like night and day.  I shaved 30 - 45 seconds off of a page load simply by storing the info in a session object.  You could do it with caching, set a property on the init or any other method, as long as it's only being called once.

Second, the tree view is extremely inefficient.  It loads everything all at once during the .  It doesn't rely on dynamically loading the information, although it looks like some attention was given to that possibility at one time, the way it's been designed.  RadTreeView is capable.  I'm currently on rewriting this control for just that capability...

And there are more bad design decisions there, but I'm not going to nitpick as I couldn't do too much better....

Cheers,