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 ...Site using lots of RAM on w3wp process - caching issues?Site using lots of RAM on w3wp process - caching issues?
Previous
 
Next
New Post
5/7/2007 12:05 PM
 

Hi,

Smart-Thinker.com is running DNN 4.5.1, and receives about 500 users a day (ie. not high traffic).  I've had a lot of downtime lately and it seems to be taking up a lot of RAM (800 megs)and I can't figure out why. I noticed when I restarted the process that it immediately bloated and jumped from 64megs to 250meg in a few minutes. The site frequently hits some limit and recycles (or freezes with a "Server Unavailable" error.

Site Settings

  • Page State Persistence - Page
  • Module Caching Method - Memory
  • Preformance Settings - Light Caching (was Moderate)
  • Using Compression and whitespace filter

So my questions:

  1. How can I tell what is using so much RAM?
  2. What does the PurgeCache schedule task do? Does it regularly check the expiry date on cache items and purge them? I had mine on 12 hours - does this mean that items in the cache would last at least 12 hours? I've changed this down to 5 minutes - anyone know what the recommended value is?
  3. I'm fairly sure this has just recently started happening, and I can't figure out why - any tips on RAM usage appreciated.
  4. How much RAM should an average DNN 4.5.1 consume (assume 500 visitors a day - not massively high traffic) with optimised performance settings (ie. memory and not disk)

 


Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
5/7/2007 12:12 PM
 

Well a few things from my point of view.

With module caching in memory you will notice some bloating in size of the worker process, especially if you have modules that are cached with large amounts of content. (Large HTML modules for example). 

If you are looking at more information about the actual objects that are in memory you can use a tools such as RedGates's ANTS Profiler to analyze the application and see if you can identity fht eroot cause.

Have you added any new modules to the site recently?


-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
5/7/2007 1:12 PM
 

What performance counter are you checking for the Ram size? Frequently I see people just use the windows task manager and misinterpret the counter i.e. use the "mem usage" column. FYI, this is the working set size i.e. It is the amount of physical memory which is directly (currently) allocated to the process. It can be accessed without causing a page fault. This includes pages shared with other processes. The OS can release areas of this memory that are not being used upon request.

The correct counter to use is "VM Size" which is the total private virtual memory allocated to the process.

TO view this in task manager, click view->select columns, and check the 'virtual memory size' checkbox (or alternatively, if using perfmon add the "Process Private Bytes" counter )

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
5/15/2007 2:22 PM
 

cathal wrote

What performance counter are you checking for the Ram size? Frequently I see people just use the windows task manager and misinterpret the counter i.e. use the "mem usage" column. FYI, this is the working set size i.e. It is the amount of physical memory which is directly (currently) allocated to the process. It can be accessed without causing a page fault. This includes pages shared with other processes. The OS can release areas of this memory that are not being used upon request.

The correct counter to use is "VM Size" which is the total private virtual memory allocated to the process.

TO view this in task manager, click view->select columns, and check the 'virtual memory size' checkbox (or alternatively, if using perfmon add the "Process Private Bytes" counter )

Cathal

Ok, thanks Cathal - I am using this now. It is slightly smaller than the RAM usage I was looking at but seems to be proportional, so the problem remains.

 


Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
5/15/2007 2:29 PM
 

mitchel.sellers@gmail.com wrote

With module caching in memory you will notice some bloating in size of the worker process, especially if you have modules that are cached with large amounts of content. (Large HTML modules for example). 

If you are looking at more information about the actual objects that are in memory you can use a tools such as RedGates's ANTS Profiler to analyze the application and see if you can identity fht eroot cause.

Have you added any new modules to the site recently?

No new modules, but I now perform module caching in my UserProfile, so whenever it loads a profile it bungs it into the cache for x seconds (setable) and then all my modules check the cache first. Before the SQL service was going balistic as it hits 4 different sps whenever you call GetUser(). So now my SQL traffic has dropped drastically but RAM is a problem - I just am not convinced that it is this that is causing it.

 

What is interesting is that traffic does not seem to affect it. Yesterday there were 302 people online at PokerDIY at one point and before and after the RAM remained almost constant. What is also interesting is that Smart-Thinker uses roughly the same amount as PokerDIY - and has 80% less traffic. As soon as I kill the worker process the RAM dips by 300 meg or so, and then RAPIDLY climbs back up to near where it was (maybe 200) - this is why I don't think it is the traffic or profile stuff.

 

So my other main question which still needs answering - SHOULD the PurgeCache schedule task be run often (ie. every 5 min or so)- is this the process that checks the DNN cache and clears it if it has expired (sorry, sounds obvious) but need it confirmed. I it is, then it seems to me that I have to schedule this to run at least every 5 minutes, but I did a test and turned it off, let the RAM get high, and then turned it on (to cause it to run and clear the cache) and the RAM did not dip at all. The scheduled history always says it ran successfuly but 0 files were affected... what is the 0 files it is refering to? Is that if it uses disk caching?

 

TIA


Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Site using lots of RAM on w3wp process - caching issues?Site using lots of RAM on w3wp process - caching issues?


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