Hi,

I'm trying to configure our shared hosting environment so that we can offer DotNetNuke hosting, but I can't seem to get it's memory usage to tally with what other people have said it should use.

Basically from a fresh installation, I'm seeing it allocate 56MB of private memory - if I click Login, it jumps to 65MB (a hell of a lot of memory for a login page). If I actually login, it jumps again to 74MB on displaying the dashboard (and creaps up to 80MB without doing anything), and if I click on something like Host Settings, it jumps to 95MB.

I've seen this as high as 244MB - what's going on here, DNN is doing very little, and it's using more memory than our own ASP-based CMS/eCommerce system that we're hoping to replace.

I read about hosting accounts that tend to pin max memory usage to 180MB or something - it doesn't make sense, my blank DNN wouldn't even run in 180MB.

My server is Windows 2008 Server, running IIS7 - this installation is running in a 64-bit app pool on Framework 4.0.

Could someone give me some pointers as to why so much memory is being allocated for such small operations, and how I change configuration to fix, or is it possibly the case that the behaviour changes somewhat when there are many application pools running?

Thanks for your help with this.

Best Regards,

Mark

I agree, DNN is consuming much RAM, especially if a number of modules are installed. We have a couple of sites with up to 600 MB. If you want to sell hosting with low resources, you may consider using a shared DNN instead.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN