ASP.NET High memory usage

Hi,

We have a web application based on DotNetNuke 2.x.
1. We host several portals (sites)
2. Some relatively big clients have their own application pool and they have
a lot of hits (in average between 7K - 21K per day). (1600 per hour)
3. We also grouped low level sites into 2 application pool. (some hundred
hits per day)
4. Due to the nature of the requirements we use several threads that process
tiny to huge XML parsing and updating a main object that has list of sub
objects in an arraylist.
5. The main object is kept in session, and we also have some more tiny
objects values kept in session, but our session usage besides the main
object is very limited.

Now our problem is our worker processes are consuming a lot of
memory.(Especially for those high traffic sites)
Current consumption is like:
1. 330Mb
2. 255Mb
3. 234Mb
4. 214Mb
......
In average there is not worker process that uses less than 100Mb RAM.
(We recycle app. pools every early morning and it makes like 1Gb difference
just after recycling)

And the processor usage rarely comes upto 20% on that single CPU machine. So
processing is fast but memory consumption is high.

Questions:
---------------------------------
1. How can we optimize this high memory usage?
2. How can we measure the total session memory consumption for a worker
process and per a single transaction?
3. Will it help us to have a session state server & web gardening? Will we
loose a lot in performance by using state server (like delays etc)? We do
not have crazy super machines, the machines we have are Dell PowerEdge
Servers.
4. Will the caching application block help us if we cache commonly used data
on a cache server (We cache like list of airports in the world)? If we do
that, will we loose on performance significantly?
5. Basically what can we do?
Please help & advise.

Best regards,

--

SevDer
http://www.sevder.com
A new .NET Source For .NET Developers



.

Relevant Pages

  • Re: Session Timeout Problem
    ... Juan T. Llibre, asp.net MVP ... and select the Application Pool in which your app runs. ... You don't say whether you tried using State Server. ... the loss of session variables due to Application/App Pool recycling. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Win2003 SP1 BSOD - STOP 0xab - DIAGNOSIS
    ... session unload. ... rdpdd.dll or a video driver. ... number of paged pool bytes that are leaking ... total number of paged and nonpaged allocations that are ...
    (microsoft.public.windows.server.general)
  • Re: Slow Response for ASP.NET page
    ... the application pool level. ... application went down any session state was lost. ... On the Recycling tab, ... That causes the JITted assemblies to unload ...
    (microsoft.public.dotnet.framework.aspnet)
  • Win2003 SP1 BSOD - STOP 0xab - more info
    ... by a session pool leak. ... regardless of which printer driver is used*, ... In this case the leaking pool ...
    (microsoft.public.windows.server.general)
  • Re: Session Timeout Problem
    ... You don't say whether you tried using State Server. ... the loss of session variables due to Application/App Pool recycling. ...
    (microsoft.public.dotnet.framework.aspnet)
Loading