3 ms·
Meanwhile on servers running Windows, keeping sync to within a few seconds is a mighty challenge, esp. with Hyper-V. (Linux guests have no issue with ms or sub-
by MichaelGG 13y ago
Meanwhile on servers running Windows, keeping sync to within a few seconds is a mighty challenge, esp. with Hyper-V. (Linux guests have no issue with ms or sub-ms accuracy.)
Microsoft's Win32 time is only meant to prevent Kerberos error, so under 5 minutes is "fine".
- grecy 13y agoIf you're using win32 time for anything that needs accuracy greater than a few seconds, I think you're doing it wrong.
- MichaelGG 13y agoDo you know of anything more accurate, especially under Hyper-V? I've tried installing ntpd and even using the most aggressive settings and host time sync off, they drift like mad and the system log is filled with kernel warnings about time changes.
- grecy 13y agoIf I have something that needs that level of accuracy, and the implied up time to go with it, I don't use Windows. Neither should you.
- MichaelGG 13y agoI guess I find it sort of amazing that Windows can ship in 2014 and not have close to ms accuracy.
- grecy 13y agoNot at all. I think that kind of thing highlights where Microsoft's priorities are with Windows, and therefore the kinds of things you should be doing with it. If you buy a civic to take to the racetrack, you shouldn't be amazed it doesn't come with a roll cage. Civics are supposed to be on racetracks, and windows isn't supposed to be a serious-workload OS. It's no problem though, you have plenty of alternatives for both.