How does ASP process requests?

[danielml22]

I have noticed that when my ASP application is loading a page, it doesn't load anotherone, anywhere else in my Intranet until that page is done. This is particularly visible when it's loading large reports. Even if I try to sumiltaneously open up another page that doesn't load a heavy report, the second page wont load until the first one is done. Now this happens, within the same computer, and even if I'm loading something in one computer, and another one requests an ASP page, the same thing happens.

Now basically, my question is: Is this the way ASP works, period? or is there something I'm doing wrong, either when loading pages, or when accessing a database, or what is it?

Is it a way that I can make ASP pages on the same application process independently, or will I always have to wait for one to load until the next one can start loading.

I've looked up this over the web, but I don't seem to find documentation on that particular subject. I really hope someone around here can help me out.

Thanks :)

[markrawlingson]

This is particularly visible when it's loading large reports.

I'm thinking that this could be a resource issue. It sounds like when the first page loads, it eats up an enormous amount of resources and there aren't enough resources left over to serve the next page, so the worker process queues it, and serves it when it's able to locate the required resources for that page.

The company I work for recently had a similar issue, I was able to fix it by recoding a portion of the most resource heavy page being served on the site. It was coded poorly, and on average created over 50 recordset objects every time the page was loaded due to a bad loop, I recoded it more efficiently and I haven't seen the problem since.

You may want to check the processes running in your server's task manager. Primarily look for a process called w3wp.exe - and check to see how much memory it is using and how much CPU usage it's taking up while these pages are being loaded.

In our case, the worker process serving the site that holds the page i recoded was maxing out CPU usage, between 89-100% and the memory usage was between 110 - 120 mb during our peak usage times. Just by this ONE worker process, we have 6 worker processes handling several groups of websites and many other processes running on the box in addition.

Btw, our box is a p4 2.4gighz - 1gig DDR-2 RAM.

Anyway, Hope this helps you out!

[danielml22]

Hmm, the server proccess w3wp.exe doesn't go over 30% cpu usage, and even like that, when one page is loading nothing else loads until that's done.

:(