Problems? Is your data what you think it is? | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
You do not explain, why the script has to be run exactly every second.
Anyways, you should probably keep in mind, that you're about to write a fork bomb. When the server for whatever reason get's busy, and the spawned script already takes longer than a second for execution, as you write, -> the script will take even longer -> more and more scripts are spawned, burden the server even more -> voila, k'boom. Beside of this, I guess, best way for really exact timing would be spawning the script, which now wait's within a spinlock for the current second to change. -> the delay of spawning the script is gone, it's already in action, cpu scaling won't matter, and so on. You also don't write, which platform you're on. So which timer you are able to use is another question. afaik, without looking it up, the most exact "timer" is the cpu tick counter. So you probably have to write the spinlock in C. In reply to Re: The most precise second (timer)
by misc
|
|