Does PHP process requests sequentially on one CPU?

[Bruce W.1]

With ASP.NET I've found that request are processed sequentially, one at
a time, at least on a server with one CPU. If one request blocks for
some reason, maybe on a long database query, then all users must wait
until it completes, for their request to process.

This leaves me wondering about PHP running on IIS and Window. Does this
hold true for PHP also?

What about PHP on Unix? Does this allow true simultaneous processing of
all requests when the server has a single CPU?

Thanks for your help.

[CountScubula]

"Bruce W.1" <[e-mail]> wrote in message
news:40***************@direct.email...

With ASP.NET I've found that request are processed sequentially, one at
a time, at least on a server with one CPU. If one request blocks for
some reason, maybe on a long database query, then all users must wait
until it completes, for their request to process.

This leaves me wondering about PHP running on IIS and Window. Does this
hold true for PHP also?

What about PHP on Unix? Does this allow true simultaneous processing of
all requests when the server has a single CPU?

Thanks for your help.

This is a Windows/IIS issue, I forget where, but you can change the
threading model I believe.

--
Mike Bradley
http://www.gzentools.com -- free online php tools

[Andy Hassall]

On Fri, 06 Feb 2004 11:28:41 -0500, "Bruce W.1" <[e-mail]> wrote:

With ASP.NET I've found that request are processed sequentially, one at
a time, at least on a server with one CPU. If one request blocks for
some reason, maybe on a long database query, then all users must wait
until it completes, for their request to process.

This leaves me wondering about PHP running on IIS and Window. Does this
hold true for PHP also?

What about PHP on Unix? Does this allow true simultaneous processing of
all requests when the server has a single CPU?

This almost certainly depends on your host webserver. Apache on Unix spawns
multiple processes to serve requests, and so they would timeshare as usual on a
single CPU. On Windows it spawns multiple threads - which are also timeshared
simultanously. In both cases, anything blocking would almost certainly be
yielded by the OS scheduler to another process/thread.

I have no idea about the IIS process/thread model - is it documented?

I don't think it's a PHP issue, though.

--
Andy Hassall <an**@andyh.co.uk> / Space: disk usage analysis tool
<http://www.andyh.co.uk> / <http://www.andyhsoftware.co.uk/space>

[Chung Leong]

Sounds more like a locking issue, or perhaps a lisencing issue.

Uzytkownik "Bruce W.1" <[e-mail]> napisal w wiadomosci
news:40***************@direct.email...

With ASP.NET I've found that request are processed sequentially, one at
a time, at least on a server with one CPU. If one request blocks for
some reason, maybe on a long database query, then all users must wait
until it completes, for their request to process.

This leaves me wondering about PHP running on IIS and Window. Does this
hold true for PHP also?

What about PHP on Unix? Does this allow true simultaneous processing of
all requests when the server has a single CPU?

Thanks for your help.