Has anyone noticed a substantial increase in the memory usage of the aspnet_wp process under Task Manager?

Ever since I upgraded to the 3.0.12 Release version I've noticed that memory has jumped from 20-30megs of consumption to 100-150megs of consumption. Also, the memory seems to fluctuate a lot, even without traffic to my web server.

DJ

I have 8 or so installs on one machine, they get moderate usage (150 visitors and 3000 view), they run about 35MB usage and 52MB peak usage.

Do you have any custom modules that may be leaking?

That's quite possible, I'm going to have to dig a little deeper to figure it out. I also noticed that the aspnet_wp.exe is causing my cpu to run at 99% in spurts, with no web traffic coming in or going out.

DJ

Found the leak, the DNN scheduler was the cause, it was making my memory and cpu fluctuate.

To turn this off I did the following:

1. Log in as host
2. Go to Host Menu
3. Choose Host Settings
4. Expand Advanced Settings
5. Expand Other Settings
6. Set "Scheduler Mode" to "Disabled"
7. Click "Update"

Now I'm off to read about the scheduler and what problems will occur with me turning this off.

DJ

I'm back again.

Setting the Scheduler to "Request" seems to be working without any memory/cpu fluctuation. It was originally set at "Timer" and that caused the high memory/cpu consumption.

DJ

What kind of hardware, OS are you running it on?

My CPU %'s idle at zero and spike to maybe 35% - 36%...

in my log files (windows event logs) I see some odd messages about a process having to be cycled due to it's use of memory.

I have not had time yet to check the details.

I'm running on Windows XP Pro Service Pack 1. I'll probably upgrade to Windows 2003 Server in the coming week.

Running the Scheduler in Request mode still seems to be causing the memory/cpu spikes. So I'll be shutting that off until I upgrade my OS.

DJ

I've been having the same problem with aspnet_wp as well. I've checked my schedulers and they're all set to "Request".
How did you go about finding the leak? What were you looking for? What did you monitor?

thanks,

There are a number of jobs in the scheduler that folks may or may not need, or may wish to change the frequency of.  For example, a scheduled job is used for the search architecture for periodic re-indexing of the site.  If a site is fairly static, it might want that indexing to occur only once a day rather than on a more frequent schedule.  Analyzing your particular needs for the available scheduled jobs is a good idea.