That makes sense, but I'm not sure I really want to do this, since
it's fairly important that Listener continue listening without
interruption.
I also don't think it's probably necessary, since from what I read,
I'm not really pushing the envelope in terms of real load. Right now,
I might have max ~250 clients connected, each sending 5-20 kb / day
of data. It's not much data, nor many concurrent connections. If
Jim's Listener handles 80-85k connections per day, then mine should
be able to do 250 concurrently easily, and 2000 cumulative per day
without a hitch.
Did I mention, I'm on Mac OS X Server 10.4.11? Shouldn't matter, but
anyway.
On 10-Dec-07, at 5:48 PM, Jochem Maas wrote:
Jim Lucas wrote:
Tom Rogers wrote:
Hi,
...
Also, make sure you are not using an array that you are not re-
initializing through each iteration
of the loop. If the array keeps getting bigger, PHP might $*%& on
itself. Always re-initialize
arrays to clean them up.
even then he may still have creeping memory ... in which it might
be possible to have a mother process that
spawns and watchs a child process .. the child process is the
actual deamon, the child could then keep a track
of it's own memory usage and then kill itself when it gets too
big ... the mother in turn would automatically
spawn a new child deamon process upon seeing it's child has
committed suicide.
does that make sense?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
