Obviously, this question depends on volume and activity of specific applications. In general, high memory is when your ASP. In general terms, a comfortable level would be under MB in the default 2-GB user memory address space. Once the memory level is higher than that comfortable level, we're doing less than we should be. This behavior may affect other applications that are running on the system. The key is to understand some applications require more memory than others.
If you're exceeding these limits, you may add more memory or add another server to your Web farm or consider a Web farm. Profiling is also recommended in these cases. It can enable developers to create leaner applications. In this article, we're looking at a situation where you consistently see memory rise until the server stops performing.
One reason for high memory that we see here in Support a lot is when you have debugging, tracing, or both enabled for your application. Enabling debugging and tracing is a necessity when you develop your application. By default, when you create your application in Visual Studio. NET, you'll see the following attribute set in your Web. Also, when you do a final build of your application, make sure that you do it in Release mode, not Debug mode. Once you're in production, debugging should no longer be necessary.
It can really slow down your performance and eat up your memory. Setting this attribute means you change a few things about how you handle your application. First, batch compile will be disabled, even if it's set in this compilation element. It means that you create an assembly for every page in your application so that you can break into it. These assemblies can be scattered randomly across your memory space, making it more difficult to find the contiguous space to allocate memory.
It's fine when debugging, because you can't have the application time out while you patiently step through the code to find your blunders. However, it's a significant risk in production. It means that if you have a rogue request for whatever reason, it will hold on to a thread and continue any detrimental behavior for days rather than few minutes.
Finally, you'll be creating more files in your Temporary ASP. NET files folder. And the System. DebuggableAttribute System. Collectives on Stack Overflow. Learn more. Ask Question. Asked 9 years, 3 months ago. Active 9 years, 2 months ago. Viewed 2k times. When i running my application, i am getting the following error Server Application Unavailable The web application you are attempting to access on this web server is currently unavailable.
Please hit the "Refresh" button in your web browser to retry your request. Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur. I am also checked with EventViewer NET 4. Please guide me to get out of this issue Saravanan Saravanan See this article for an explanation of how to troubleshoot this problem.
Add a comment. Active Oldest Votes. Thanks buddy! You are absolutely right, but when i close the process tree from task manager i found that all the active db connections are closed.
So in my opinion this might be happening because of the connection spooling. Accept the answer if it worked : ty. There are also time outs associated with your connections and the IIS process will keep those open till the connection times out. You should be explicitly closing them when you are done with them anyway. Thanks J. So do you mean its the issue related with garbage collection or should i call GC explicitly? Don't call GC explicitly if you don't fully understand it.
Andrew Hare Andrew Hare k 68 68 gold badges silver badges bronze badges. Thanks Andrew! Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name.
0コメント