Sequential one request at a time processing

B

Bruce W.1

ASP.NET processes one request at a time, sequentially. If one process
blocks or sleeps then it brings down the entire application for all
users.

This fact is hidden under the rug by Microsoft. It would clearly be a
problem for any website that has tons of traffic.

On this I seek specifics.

Is it sequential per DLL or per page? If one page blocks, on say a big
database query, will other pages process and respond?

On a multi-processor server, say with four processors, is this still a
problem? Or will each processor be independent of eachother?

How does this sequential processing scale to a web farm or garden?

Thanks for your help.
 
B

bruce barker

asp.net does not process pages sequential, it can currenlty process as many
requests as the thread pool size. if your pages are processing sequentialy,
then you have put code on your pages that blocks.

-- bruce (sqlwork.com)
 
B

Bruce W.1

bruce said:
asp.net does not process pages sequential, it can currenlty process as many
requests as the thread pool size. if your pages are processing sequentialy,
then you have put code on your pages that blocks.

-- bruce (sqlwork.com)
========================================================

Wrong. Test it yourself.

When a page blocks, for whatever reason, other requests to the page are
not processed.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,731
Messages
2,569,432
Members
44,832
Latest member
GlennSmall

Latest Threads

Top