As I said I am getting about 700 prints of the same time, and then the next set of lines is time+0.06Actually, it should be closer to 0.055.
Windows' internal click gets updated 18 times a second, or once every 55ms, via a timer interrupt. The API call GetTickCount() exhibits the same behaviour as you describe here. The docs for this API call mention:
It is limited to the resolution of the system timer.So yes, even though I haven't seen any evidence that the two phenomenons are indeed related, their symptoms are so strikingly alike, that I'm quite convinced they share the same origin. So yes, it's a Windows Thing™.
Update: I don't mean to say it cannot be fixed/patched, only that this is behaviour you'll typically only see in Windows, for this particular case.
In reply to Re: Re: Re: Time::Hires Granularity
by bart
in thread Time::Hires Granularity
by pseudosocrates
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |