Dated: July 2, 2004
We will be taking Win6 down for a RAM upgrade today at 6pm EDT. Server will be down for 5 minutes at the most.
Win6 has been experiencing occasional ASP.NET out of memory errors. Although we now believe we have solved this issue, we are adding another gigabyte of RAM to this server as a precaution.
The ASP.NET error seems to be occuring whenever the asp.net worker process hits 1GB of RAM usage (even when there is plenty of more availabe RAM). This happening is highly abnormal as ASP.NET ram usage on other servers hovers around 400MB. This indicates to us that a few customers maybe be running highly intensive asp.net applications with memory leaks. We request customers to check their code if they believe they may be responsible
As a temporary solution, we have configured ASP.NET to automatically recycle when it comes close to the 1GB treshhold. We will be monitoring ASP.NET closely on Win6 to track down any program with memory leaks on Win6 and will inform customers to correct their code
We will be taking Win6 down for a RAM upgrade today at 6pm EDT. Server will be down for 5 minutes at the most.
Win6 has been experiencing occasional ASP.NET out of memory errors. Although we now believe we have solved this issue, we are adding another gigabyte of RAM to this server as a precaution.
The ASP.NET error seems to be occuring whenever the asp.net worker process hits 1GB of RAM usage (even when there is plenty of more availabe RAM). This happening is highly abnormal as ASP.NET ram usage on other servers hovers around 400MB. This indicates to us that a few customers maybe be running highly intensive asp.net applications with memory leaks. We request customers to check their code if they believe they may be responsible
As a temporary solution, we have configured ASP.NET to automatically recycle when it comes close to the 1GB treshhold. We will be monitoring ASP.NET closely on Win6 to track down any program with memory leaks on Win6 and will inform customers to correct their code