Unless you are running 64 bit version of the o/s or running the 3g switch,
2gb is the max memory size.
You need to determine if you have memory leaks (common if you use any com
objects). You also need to determine if you are using manged or unmanged
memory. see:
http://msdn2.microsoft.com/en-us/library/ms954591.aspx
If your memory usage is just session, then switch to sqlserver sessions
(should not use inproc with production sites anyway).
-- bruce (sqlwork.com)
On 1/8/07 4:11 AM, in article
11**********************@s80g2000cwa.googlegroups. com, "san"
<sh*******@gmail.comwrote:
>
we cannot stop the application from increasingly use memory. The CRM
Worker process will continually consume memory but not release it back
to the system. Please research into how to make the application consume
less memory or at least release the memory when it is done processing a
request.
It seem like you can be logged in for any amount of time without an
issue, I've been told you shouldn't be logged out until idle for 2
hours but people are having this issue of timeout.
We have added a more robust server to our web farm. This server has 4GB
of memory and is faster. With this additional server, our users are
experiencing timeouts much less frequently.
We are seeing new behavior with the addition of the new server. On the
new server we have set Machine.config as well as IIS to recycle the
worker process after 80% memory usage (3.2GB). However, the application
itself is failing to respond after 1.2 GB of usage. We see that the
worker process is still running but users report that the system is
slow and unresponsive at best.
We are having to recycle the worker process ourselves once it hits this
limit. This happens roughly every 3-3.5 hours.
Can you please help me how to minimize memory usage by application.
(may be due to our appplication is using many session variables )
Looking for your support/suggestions to comeout form this critical
issue.
Regards,
San D.
