Worst case Poco::Timestamp resolution

A general discussion forum.
dreamy
Posts: 6
Joined: 10 Apr 2012, 23:05

Worst case Poco::Timestamp resolution

Postby dreamy » 21 Mar 2013, 21:04

Hi fellows,

I would like to ask what's the worst known case of Poco::Timestamp precision and what platforms can it affect.
Also, it would be really nice if this this (important!) aspect was documented, instead of just saying "with (theoretical) microseconds resolution".

So far, I found that Timestamp::update is based on GetSystemTimeAsFileTime on Win32 systems, which should have:
  • 15.625ms or 10ms precision on Windows XP, Windows 2000 and NT depending on hardware
  • 1ms precision on Windows 7 and probably Windows Vista and Windows 8

Any observations? This might be (really!) important when someone tries to measure some execution time.

Return to “General Discussion”

Who is online

Users browsing this forum: No registered users and 1 guest

cron