ASP.NET memory problem

[Anders K. Jacobsen [DK]]

Hi,

We are running a intranet application (.net 1.1 asp.net) on a windows 2003
server. We are having some issues that causes extreem slowdowns (like 1 min
to show one page)

This happens usally when the (W3P..something) process reaches aprox 300 MB.
The server has 515 mb ram (2.4 Ghz) and is running a mssql server 2000.
While this is not a perfekt windows 2003 shouldnt be ok for a small user
group?

Anyway. If we kill the worker process everything runs perfectly for a couple
of hours again. The system is used by aprox 2-3 person on and off. So the
server is always doing something but not at all heavy loaded.

Can we eg set the worker process to be recycled on 250 mb? Or the is memory
just the bottleneck?

Thanks for you advise
Anders Jacobsen

 

[=?iso-8859-9?Q?Yunus_Emre_ALP=D6ZEN_=5BMCSD.NET=5D]

515*0,6 = 309MB...

It is not a magic.. It is .NET Framework default configuration. You may change this configuration which is defined in %windir%\Microsoft.NET\Framework\%Version%\CONFIG\machine.config. Take a look at processModel element:

<processModel enable="true" timeout="Infinite" idleTimeout="Infinite" shutdownTimeout="0:00:05" requestLimit="Infinite" requestQueueLimit="5000" restartQueueLimit="10" memoryLimit="60" webGarden="false" cpuMask="0xffffffff" userName="machine" password="AutoGenerate" logLevel="Errors" clientConnectedCheck="0:00:05" comAuthenticationLevel="Connect" comImpersonationLevel="Impersonate" responseDeadlockInterval="00:03:00" maxWorkerThreads="20" maxIoThreads="20"/>

But be careful when u are modifying this configuration...

And I think u ve some problems about optimization. My advice u to refactor your code and find out why it is requiring too much memory. There are too much essays ion the net about optimizing your code. Be careful using strings and session, cache objects. Monitor your application when your objects are removed from memory..... And lots of things u can do...