I'm running a PHP loop that 'scans' a directory, every 60 seconds, until a file with a given name is found:
<?php
do {
if (file_exists("../path/file.txt)) {
//Do Stuff
$status = "File Found";
echo $status;
} else {
$status = "File Not Found";
sleep(60);
}
} while ($status == "File Not Found");
?>
In this example, would removing sleep() require more server resources?
Thank you,
In a nutshell, yes, but don't worry about it.
While sleep is executing, CPU processing of your script virtually stops. So yes, it will alleviate processing resources. (The script is still in memory, so those resources are still used, but that shouldn't be a problem on a modern machine.)
If your goal is to do this every 60 seconds, the best practice would be make your PHP a cron script, and run it at low priority.
nano crontab -e
Add the following:
* * * * * /usr/bin/nice -n 12 php -q /path/file.php
And replace the /path/file.php with the full path to your PHP script.
Edit your script's file permissions to allow execution.
chmod ug+rwx /path/file.php
(Again replacing /path/file.php with your actual PHP script's full path.)
Lastly, it's a good idea to make these the very first 2 lines in your PHP script, if you intend to run it this way:
#!/usr/bin/php5
<?php
Yep, every instruction run costs resources whether it be register space, memory, or disk IO.
In this case DO NOT REMOVE your sleep() -- polling constantly without rest is a great way to needlessly crush your resources.
In this case, until the file shows up you'll be looping like mad wasting processor cycles and possibly some disk IO on the conditional check file_exists("../path/file.txt).
By waiting a minute between loop that's tremendously less costly that constant as-fast-as-you-can conditional checks.