Hi Guys,

I have quite a serious problem with DNN using excessive amounts of memory on one of my servers.  Essentially with a fresh DNN 6 blank website install if I load it up in a browser and hit F5 or refresh a few times the memory increases by about 5-10K a pop. 25 refreshes = 474,004K. The memory doesn't seem to release for at least 30 minutes.

When I installed the exact same copy of DNN on my other server and repeat the same test with the same number of refreshes the memory increases slightly but then recycles. 25 refreshes = 140,000K

The same problem occurs on my development laptop.  No other .net applications or IIS 7.5 websites that I run experience this problem or anything similar.  I will try and out line the server set ups below.

I have spent a bit of time on google and as a short term stop gap I have set IIS to recycle when it hits 300K memory but this is NOT a solution, its a band aid.  Two of the systems we are currently developing will have tens of thousands of hits per month and this is going to cause the server to crash.

The main difference I can see is that the windows 2003 Server uses an older version of IIS and that its 32 bit but due to the nature of what we are developing we cant just use windows server 2003.  

Server That Works

Windows Server 2003 32 Bit - SQL express 2005 - .net 3.5 installed.  2gb Ram.

Image of taskmgr showing IIS memory usage after 25 refreshes

Server That Doesnt Work

Windows Server 2008 64 Bit - SQL 2008 For Workgroups - .net 3.5 installed. 4gb Ram.

Image of taskmgr showing IIS memory usage after 25 refreshes

Laptop That Doesnt Work

Windows 7 64 Bit - Sql 2008 enterprise - .net 4 installed (App pool running .net 2) 8gb ram

Hi Sebastian,

Thanks for replying to my post.  The info is above but to clarify, both the server that works and the server that doesnt are running .net 3.5. My laptop which is also symptomatic is running .net v4.0.30319 but the application pool which holds DNN is set to run on .net 2.0 (3.5)

On the server without the problem the App Pool / Site is running using the login "Network Service" as this is an IIS requirement of windows server 2003.

On the server with the problem I have sites running using both custom users and also "Network Service" however this has made no difference.  

It does feel very much like a memory release issue which I feel must be related to IIS 7.5 or SQL server 2008 R2 as these are the only real differences between the servers.  

I have now tried this on 2 more windows 2008 R2 servers with the exact same result :( Does anyone have this running on a windows 2008 R2 server and can take a few screen shots of their IIS settigns for me please.

The settings for both IIS and DNN are the standard install settings.  I have created fresh DNN installs and tried modifying the DNN host / IIS app pool settings but everything I have done has made it horifically worse, when I stared modifying the cache settings I ended up using around 100K per page refresh.

http://www.acumenconsulting.co.nz/ima...
http://www.acumenconsulting.co.nz/ima...

How does the DNN Elite support work? there is no pricing or contact info. Were happy to pay someone to get onto our servers and fix it ive been playing with it for a week now and am ready to pass it off.