| Re: Current PHP implementation [message #180022 is a reply to message #180018] |
Thu, 27 December 2012 00:54   |
Thomas 'PointedEars'
Messages: 701
Registered: October 2010
Karma:
|
Senior Member |
|
|
Peter H. Coffin wrote:
> Fine. I'll do it. It will be correct, within the contexts of PHP.
And unsurprisingly, what you posted is not even close to being correct, the
PHP part included.
> 1. It depends on how the webserver processes things. Typically there
> will be ten processes spawned. Then processes will exist so long as they
> have work to do, then exit when they are done or the process timer
> expires.
No, typically (read: apache-mpm-prefork on a Linux-based system) there will
be two server processes that have 10 threads each, which will continue to
run until the server is shut down.
In any case, with PHP run by server module or FastCGI, the parent process
will like *never* exit as long as the server system is running uninterrupted
(i.e., without reboot and maintenance).
Started threads will likely exist until the Web server service is stopped.
New child processes will be created if the number of threads in a child
process exceed the specified maximum. Threads in a child process will be
created so as to meet the specified minimum and number of spare threads.
> Now, was that helpful?
No.
> Probably not.
So you figured. But you posted this utter nonsense anyway? You have way
too much time on your hands.
> […] You even made me look at a w3sc***ls page to make sure I didn't miss
> something,
There is nothing to be gained from reading a “w3sc***ls page” and much to be
lost. Most of all, clarity of thought and overall mental sanity. Of which
your posting is a good example.
> and now I feel like I need a shower.
Me too.
PointedEars
--
When all you know is jQuery, every problem looks $(olvable).
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]