Setting the cache setting to "High" in the Host Settings

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

 I totally agree with zhaodengpan. DotNetNuke issues way too many of the same queries. The current caching mechanizms are only half of the solution. For instance i created a memcached provider to use instead of the default in memory cache. When you make the same call for GetTabs, GetTabPermissions, GetSkins etc... so many times per page load this adds up becuase serialization/deserialization must occur which takes reasonable CPU time. This is something you won't even notice using the default in memory cache because serialization/deserialization doesn't need to be done.

 

I Propose that the AppContext cache should be used way more often. This is a cache for each request so you can share data between user controls (i.e DNN modules). So the flow would now be.

1. Check AppContext Cache.

2. If exists in AppContext use it else go to caching provider

3. If exists in Caching Provider cache use it and store in AppContext else go to database 

4. If result returned from db store in caching provider cache and AppContext.