so whatever process was in the way held onto the CPU for 17 timeslots past what the script was expecting, right?
Make sense to me. Though it doesn't have to be a single process. It could be a mix of 2 more higher (or equal) priority tasks, that between them prevent yours getting back for 17 slots.
If you run it at standard priority and play some music or video at the same time you may see the frequency of the misses increase.
What is it that you are trying to time?
In reply to Re^7: Unexpected Timing spikes using Time::HiRes
by BrowserUk
in thread Unexpected Timing spikes using Time::HiRes
by desemondo
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |