Documentation states that "seconds" must be positive. This is not correct, 0 is possible.
Rather, "seconds" must be non-negative.
(PHP 5, PHP 7, PHP 8)
time_nanosleep — Atrasa por um número de segundos e nanossegundos
Atrasa a execução do programa pelo número de segundos informado em
seconds e de nanossegundos informado em nanoseconds.
secondsDeve ser um inteiro não negativo.
nanosecondsDeve ser um inteiro não negativo menor que um 1 bilhão.
Nota: No Windows, o sistema pode atrasar mais que o número de nanossegundos informado, dependendo do equipamento.
Retorna true em caso de sucesso ou false em caso de falha.
Se o atraso foi interrompido por um sinal, um array associativo será retornado com os componentes:
seconds - número de segundos remanescentes
no atraso
nanoseconds - número de nanossegundos
remanescentes no atraso
Exemplo #1 Exemplo de time_nanosleep()
<?php
// Cuidado! Não vai funcionar como esperado se um array for retornado
if (time_nanosleep(0, 500000000)) {
echo "Dormi por meio segundo.\n";
}
// Assim é melhor:
if (time_nanosleep(0, 500000000) === true) {
echo "Dormi por meio segundo.\n";
}
// E assim é o melhor:
$nano = time_nanosleep(2, 100000);
if ($nano === true) {
echo "Dormi por 2 segundos, 100 microssegundos.\n";
} elseif ($nano === false) {
echo "Pausa falhou.\n";
} elseif (is_array($nano)) {
$seconds = $nano['seconds'];
$nanoseconds = $nano['nanoseconds'];
echo "Interrompido por um sinal.\n";
echo "Tempo remanescente: $seconds segundos, $nanoseconds nanossegundos.";
}
?>
Documentation states that "seconds" must be positive. This is not correct, 0 is possible.
Rather, "seconds" must be non-negative.You should take into account, if you use the function replacement down here, the CPU will be in use of 99% for the time of execution...
(A little bit better in this situation is to let the 'full seconds' go by a normal sleep command (makes the thread sleep!, and uses minimum cpu))
<?php
//THIS IS THE FUNCTION WE ARE TALKIN ABOUT
function timeWait($microtime)
{
//optimizations added by me [start]
//sleep the full seconds
sleep(intval($microtime));
//set the microtime to only resleep the last part of the nanos
$microtime = $microtime - intval($microtime);
//optimizations added by me [end]
$timeLimit = $microtime + array_sum(explode(" ",microtime()));
while(array_sum(explode(" ",microtime())) < $timeLimit)
{/*DO NOTHING*/}
return(true);
}
//THIS IS HOW WE CAN USE IT
echo "Process started at " . date("H:i:s") . " and " . current(explode(" ",microtime())) . " nanoseconds.<br>";
timeWait(5.5); //With this call the system will wait 5 seconds and a half. You can use either integer or float.
echo "Process completed at " . date("H:i:s") . " and " . current(explode(" ",microtime())) . " nanoseconds.";
?>Just glancing at this - and the note from over a year ago with a implementation for windows.. with 5.0.0 and higher it would be simplier to just do something like......
<?php
if (!function_exists('time_nanosleep')) {
function time_nanosleep($seconds, $nanoseconds) {
sleep($seconds);
usleep(round($nanoseconds/100));
return true;
}
}
?>
....off the top of my head - obviously simple enough there should be no mistakes.. but those are the ones that always seem to get ya :( .....A response to the note below:
Your function is also useless, as the WinNT 32 kernel only functions at a minimum of about 10+ ms (1,000 us), rendering usleep() useless, because usleep uses the C function which is provided by the system (in this case, kernel32.dll).
You'll want to use a function that does not rely on the kernel, but rather something made for precise measurement:
<?php
function usleep_win( $micro_seconds )
{
if ( @function_exists( "socket_create" ) && @function_exists( "socket_select" ) )
{
$false = NULL;
$socket = array( socket_create( AF_INET, SOCK_RAW, $false ) );
socket_select( $false, $false, $socket, 0, $micro_seconds );
return true;
}
else
{
return false;
}
}
?>
This function will allow to you sleep for a specified microsecond, although I have measured it to be off by ~5 us.
Again, most of this depends on the hardware in your system. If you _REALLY_ need to be precise to < 10 us, you shouldn't be using WinNT anyways!