Hello, I recently posted on the whole sleep() issue with max execution time thing but now I'm past that and actually concerned about webserver ability.
Here's what I'm doing in a nutshell: Loop infinitely, checking for changes to a database, flushing the data, sleep, and repeat the loop. It all goes well and I'm getting it to work correctly. However, I'm not sure on the impact on my webserver. I've been running tests, monitoring my server's CPU and memory usage and there is very little difference between before, during, and after I run the infinite loop. However, what has me concerned is that I can't go to any other page on my web server while the loop is in progress. For example, if my loop is running, and I try opening phpMyAdmin for instance, it'll just sit and wait to load and never actually do anything. I pretty much know it's the infinite loop's issue since it only happens when I'm running it. Is this a bad thing such that I can't work around it or is it some sort of configuration issue in my Apache or PHP config? I would test it on my publication server but I don't want to annoy my fellow shared server people if this does indeed cause issues. Any help here would be appreciated... ------------------------------------ Stephen Craton IM: [EMAIL PROTECTED] http://www.melchior.us ------------------------------------ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
