in an old enough post I tried to extract some info about msecs of the game’s playback and answers had to do with FPS rather than msecs,
then it was obvious that a problem of msecs must refer to something too expert and only for Computing; so the sole useful outcome was to find out about an instruction of the BCDEDIT which solved a screen safety issue I had, quite important to settle at the time.
That problem consisted in choosing a fullscreen (Windowed) which could not bypass the safety setting in BCDEDIT as Borderless fullscreen was capable of.
As for msecs it was easy to deduce later, though not know for certain, that many apps bypass the hard layer of output distortion and then hit precision with allowing a little latency to make up for extra msecs.
But it comes now as another bummer to discover that even “windowed fullscreen” was not enough in order to not bypass another safety issue, this time one in winRegistry (namely, the ndu): it is hard to assess this one, being too stealthy in its effects, a default 2 necessitates to be set at 1. But it is a strong conviction of mine, So at last I chose strictly the “windowed” option in system settings.
Hey, I decided I should share this viewpoint because of being caught between two uncomfortable set-ups: one is that WoW always feel so extravagant a game as to not really care to request technical support for it,
the other uncomfortable set-up is to having to request Computing support which amounts to getting training actually (as seen from another’s side) and that is simply out of context if positioned like that.