问题描述
调用 GetSystemTimePreciseAsFileTime
与使用GPS的本地PC相比。我们将在Azure和PC上运行部分模拟,并且需要UTC时间同步/精确。
What is the expected (or worse case) between call to GetSystemTimePreciseAsFileTimeon Azure vs a local PC with a GPS. We will be running part of our simulation on Azure and on pc and need the UTC time to be synchronize / precise.
关注https://docs.microsoft.com/en中的文档-us / azure / virtual-machines / windows / time-sync似乎预计会有1 ms的偏移量。有没有办法在Azure VM中接近UTC时间的100us最大偏移量?
Following the doc in https://docs.microsoft.com/en-us/azure/virtual-machines/windows/time-sync it seem that 1 ms offset is to be expected. Is there any way to get closer to 100us maximum offset in UTC time in Azure VM ?
谢谢
RéjeanS。
Réjean S.
推荐答案
根据更糟糕的情况,我会指出你的概述部分
As per worse case scenario, I would point you to the Overview section
虚拟机与主机的交互也会影响时钟。在 期间 ,虚拟机暂停最多30秒。例如,在维护开始之前,VM时钟显示10:00:00 AM
并持续28秒。 VM恢复后,VM上的时钟仍将显示上午10:00:00,这将是28秒关闭。为了解决这个问题,VMICTimeSync服务监视主机上发生的情况,并提示在VM上发生更改,以
补偿。
在此更新期间,每个应用程序的行为都不同。从客户的角度来看,这些更新发生了,用户永远不会有任何想法。它们发生得非常快,并且不会中断VM上运行的服务。平台
将更正暂停的时间,但在使用GPS时这可能是一件有趣的事情。
Each application would act differently during this update. From a customer perspective, these updates happen and the users never have any idea. They happen very quickly and without disruption of the services running on the VM. The platform will correct the time it was paused for but that could be an interesting thing to have when working with GPS.
这篇关于UTC VM与本地GPS之间的UTC时间偏移的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!