Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Potential memory leak Potential memory leak
Previous
 
Next
New Post
6/18/2007 12:31 PM
 

I don't understand how more data retrievals causes more memory overhead in the worker process.  Maybe what you have noticed is that the SQL Server process will start to use more memory as it is used more, but that is normal for SQL Server as it does it's own caching.

One thing that may not be immediately obvious is that Light, Moderate, and Heavy caching only increases the duration of time that objects are cached.  
Changing this setting does not change the amount or size of items that are cached although there are small exceptions to this.

Changing this performance setting to Light or Heavy will not make a difference in the amount of memory used as long as the objects are kept from expiring which is easy to do if you have any continuous load / traffic.

Also keep in mind that the disk cache setting in Host Settings is only for modules.  There are lots of other objects that are only cached in memory.  Although, there is a slight exception to that rule also.  If you set EnableCachePersistance or if you enable WebFarm with the file based caching provider (the default caching provider) then you will get caching of these other objects both in memory and on disk.

 

 


DotNetNuke Modules from Snapsis.com
 
New Post
6/18/2007 2:20 PM
 

John,

In my previous tests the memory overhead was from the use of the CBO object to hydrate the data objects that are created in memory on the webserver to be used by the various modules.  This was from a previous version of DNN that I tested, but I did notice that more memory was used when less agressive caching was used due to the instantiation and manipulation of objects within memory...


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

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
 
New Post
6/20/2007 4:57 AM
 

Thanks for your input.

Although I agree that the cacheing model will impact memory usage it does not explain the excessive memory grabbing that I noted on the worker process. To put this into perspective here are some stats on the DNN installation:

DNN database size: 26MB (mdf file)
Number of portals: 3
    Portal 1: 17 users, 154 pages
    Portal 2: 13 users, 226 pages
    Portal 3: 13 users, 41 pages

Even if every user logs in and the entire database and every page is cached into memory, uncompressed, you're still not going to hit 1.5GB.

I am going to start removing modules and will provide feedback as soon as I know more.

 

 

 

 

 
New Post
6/20/2007 10:16 AM
 

I agree Richard.  That is a good idea.


DotNetNuke Modules from Snapsis.com
 
New Post
6/26/2007 5:16 PM
 

Really been struggling to reproduce this in my dev environment. The memory usage trends are consistent with .Net garbage collection cycles and permanently allocated memory can be attributed to loaded dlls. I have, however, spotted another user complaining of a similiar problem. Here's the link:

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/118/threadid/137082/scope/posts/Default.aspx

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Potential memory leak Potential memory leak


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out