-
Posted to
Classic ASP
by
lkevinl
on
09-16-2008, 1:16 PM
I've created two classic ASP websites in IIS 6.0 that both point to the same physical directory but one responds to www requests while the other responds to www2 reques and each is set to use it's own application pool. These websites are identical but they should now have their own worker processes I believe. Is this ...
-
Posted to
Classic ASP
by
lkevinl
on
09-15-2008, 9:01 AM
Hmmm... not really sure I followed all of that. Are you saying I need to figure out which page requests are running slowly causing the queue to back up? If so, I can try that.
But again, it seems that on my system where I have quite a bit of spare memory and CPU cycles that things are getting choked off by some other limiting ...
-
Posted to
Classic ASP
by
lkevinl
on
09-14-2008, 9:03 PM
dear god man... what a horrendous day....
I read an article about AspProcessorThreadMax in IIS 6.0. It menation about increasing the number of worker threads from the default of 25 to 50. ...
-
Posted to
Classic ASP
by
lkevinl
on
09-14-2008, 12:45 PM
Clearly I'm not benefitting from the availability of the Quad Core Xeon and splitting up the processes helps in this case. But I'm not sure why this is an issue. Should the one pocess just use more of the resources?
Here are some numbers:
Busy w3wp.exe process - 227MB mem usage, 283MB peak mem usage.
Perfmon ...
-
Posted to
Classic ASP
by
lkevinl
on
09-14-2008, 12:08 PM
OK, I can say definitively that this problem seems to be with IIS. Both the localhost AND the www2 subdomain perform nicely while the www subdomain is very unresponsive to requests for the exact same page.
I created another website in IIS for the www2 subdomain pointing to the exact same directory that the default www site ...
-
Posted to
Classic ASP
by
lkevinl
on
09-14-2008, 11:59 AM
OK... I'm monitoring the busy traffic now. I have one browser with my site at the standard subdomain www, another browser at the subdomain www2 which should now get it's own IIS process, and a third browser which is opened to localhost with a copy of the website on it but connecting to the same, busy ...
-
Posted to
Classic ASP
by
lkevinl
on
09-09-2008, 6:27 PM
In reply to Rovastar:
Hmmm... I read articles about resource contention which made using several worker processes sound appealing, but I can't use web gardens anyway since this is Classic ASP... I found out the hard way!
It is just slow. Slow means several seconds, up to 10 seconds or more for a simple ASP page. I have one page ...
-
Posted to
Classic ASP
by
lkevinl
on
09-09-2008, 6:04 PM
[quote user="tomkmvp"]
What does the application do? Are you following good ASP coding practices (i.e. not putting db objects into session vars)? Any chance you could offload SQl to another box, at least for testing?
[/quote]
Well, the application is a website... I call it an application because that's the way I ...
-
Posted to
Classic ASP
by
lkevinl
on
09-09-2008, 4:09 AM
OS is 32 bit but it's a quad core xeon and motherboard supports visibility of full 4GB of RAM.
I checked disk utilization and didn't look like it would be limiting. Network bandwidth was very high but I my hosting provider provides good bandwidth and the server isn't throttled in anyway. Also, as I mentioned, when I ...
-
Posted to
Classic ASP
by
lkevinl
on
09-09-2008, 1:09 AM
OK, here is the configuration: Quad Core Xeon, 4GB RAM, 500GB sata running Win2K3 R2 / IIS 6.0. This server is also running a mail server and SQL Server 2000 is running as the backend for the ASP app.
During a high traffic time I started to notice the browser requests were being serviced very slowly. I did some investigating and ...