We have a reasonability large DNN site (DNN version 4.3.3) with 800 tabs and 35,000 users. It runs on a 2 x Opeteron Dual Core 275 (so 4 CPU cores together) with 4 Gigs if ram. It’s got its own SQL server on the same machine.

We have been experiencing the same problems as described in this thread:

http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/111/threadid/99645/scope/posts/Default.aspx

When we change tab / module permissions, it doesn’t get reflected right away. Say when we make certain tabs / modules admin only, we don’t see red borders around the modules immediately.  This problem is not constant, if I restart the www publishing service and save web.config to force the application to restart. The problem goes away. But when it starts to happen again, it stays until another restart.

Then we decided to turn off caching (was on default - moderate).  As expected, the server got killed and became un-useble.

SQL profiler registered around 1100 SQL queries in every click.  500 of them being exactly the same query:

exec dbo.GetTabPermissionsByPortal @PortalID = 0

I understand, when caching is turned off, you would expect the system to get stuff from the database on every request.  But why would it do 500 of the same query in the same request? Wouldn’t it make more sense to declare the data static and make it carried through the entire request?

So my questions are:

1. Is caching fixed in version 4.4.0 ? Or are there anything I need to do to

2. Is the DNN core team going to change the way the system works and make sites usable when caching is turned off? Time it takes to load a page seems to be proportional to the number of tabs / users you have at the moment.