-
Posted to
Classic ASP
by
jgdean14
on
08-25-2008, 1:11 PM
ma_khan:
Thanks for your reply. From what I understand from our Operations group, the servers still respond after the w3p3 process is above 1.3GB, but there could be other factors inolved. I appreciate your stated distinction fragmentation/leak. I thought that too and we are NOT seeing any OOM errors, only a slow build up of memory until a ...
-
Posted to
Classic ASP
by
jgdean14
on
08-21-2008, 6:21 PM
Thanks for your insight and response. I have a question: Do you notice any performance hit when navigating from page to page since the pages have been cached to disk?
-jdean
-
Posted to
Classic ASP
by
jgdean14
on
08-21-2008, 5:54 PM
HI All
We have what appears to be a memory leak and/or fragmentation problem with our ASP classic/IIS6/Win2003Server application. We have 1000's of ASP pages and about a dozen COM+ objects in use. The site is geared for data-driven analysis and does not get high usage. It is not a public site. We started to notice the w3p3.exe ...