I'm not 100% sure what you're talking about, to be honest. I think I'm in the second half of the people... :)

As far as I can tell, Apache runs as many processes (httpd) as needed on my local machine. As far as my server, I haven't seen this behavior, but I admit I don't sit there watching top all the time unless something is broken, and even then, I usually can't fix whatever is broken. I don't have root or other special access to the server - it's a shared machine, pretty lightly loaded most of the time. I do have SSH access.

I think you might be talking about scalability of PHP. What I'm looking for is the ability to take a single task that generates or is initiated by a single page - such as an extremely complex sort/ranking task or complex image resizing, thumbnail generation, compression, and storage.

If I'm way off base with my comments, please correct me. I am still seeking a solid way to get some sort of thread functionality working.

-Galen

On Jan 24, 2004, at 1:15 PM, Mark Charette wrote:


On Sat, 24 Jan 2004, Galen wrote:


Hi,

This may be completely crazy, but let me tell you what I want to do:
thread PHP.

Can you set processor affinity on your system? If so, you can "pseudo thread" by assigning processes to different CPUs; e.g., run your main Webserver on one processor and a slave Web server or helper processes assigned to the other processor. This is a very common way of dividing tasks on multi-processor systems where code-rewrites to make things thread-safe are not cost effective. -- "Half the people know what they're talking about, and the other half are writing code."

-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php



Reply via email to