E
Ethan Chan
I have recently been deploying a asp.net extranet application.
The asp.net worker process starts off with 30MB virtual memory and then upon
serving a few pages, the memory usage increases to a WHOOPIN! 200MB and
eventully the asp.net process restarts at 300MB and my application becomes
"unavailable" with my sessions being destroyed.
Is there an explanation why the asp.net process uses that much memory?
After i have logged out of my application and closed the browser, the memory
usage does not decrease?
Is this due to the Compiler keeping the cache of the application?
Is there anyway i tune the performance and find the memory leak?
Tel : [65] 6225 1308 Fax : [65] 6225 1931 www.active8.com.sg
The asp.net worker process starts off with 30MB virtual memory and then upon
serving a few pages, the memory usage increases to a WHOOPIN! 200MB and
eventully the asp.net process restarts at 300MB and my application becomes
"unavailable" with my sessions being destroyed.
Is there an explanation why the asp.net process uses that much memory?
After i have logged out of my application and closed the browser, the memory
usage does not decrease?
Is this due to the Compiler keeping the cache of the application?
Is there anyway i tune the performance and find the memory leak?
Tel : [65] 6225 1308 Fax : [65] 6225 1931 www.active8.com.sg