"not enough storage" is generally a memory problem which sounds about right looking at your memory usage. It sounds like part of your site has a memory leak (i.e. failing to release resources).
What you can try is switching the application protection on content directories you think -may- have problem content over to high. (IIS Management console, right click directory, properties, Home/Virtual Directory, "Application Protection").
This will set each of the directories up in separate memory spaces and each will show up as a separate component in component services. The other benefit is that one "application" crashing should not cause the whole site to fall over.
Identify the problem dllhost.exe thread in task manager or use performance monitor logging to track memory use over time.
Get the process id (pid) of the problem dllhost.exe and then open the component services
snapin for mmc.
Drill down to "com+ applications" and switch your view on the right hand side over to "status view" to show the process id's of each thread. Match up the name column to the pid you identified earlier and you've found your problem site.
Then you need to look at your code and pinpoint the problem. The best place to start is making your code more efficient, if you need some ideas let me know.
No comments:
Post a Comment