We've had a few reports from customers who are running InstantForum.NET in a multi-processor enviroment that the ASP.NET memory usage would continue to grow and not be released. We repilcated this locally. This could grow to around 200mb and only release after the process is recycled.

This only occurrs on mutli-processor servers (dual-quad etc).

After investigation during the v4.1.4 update we tracked this down to the garbage collector. This behavior occurs because the CLR uses the "Server" garbage collector on a multi-processor computer, which creates one heap per processor, consuming lots of memory.

To workaround this behavior, configure the CLR to use the "Workstation" garbage collector:

1. Open the Aspnet.config file in Notepad.exe. The file is located at %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\Aspnet.config for .NET Framework 2.0 and at %SystemRoot%\Microsoft.NET\Framework\v1.1.4322\Aspnet.config for .NET Framework 1.1.

2. In the <runtine> section, add <gcServer enabled="false"/>.

3. Save the Aspnet.config file.

This should greatly reduce the memory used by the ASP.NET process. I hope this helps a few customers.

If you have any questions please don't hesitate to respond to this thread.


Kindest Regards,

Ryan Healey
Director / Developer

Explore our products...
http://demos.instantasp.co.uk/