Windows 8 Benchmark Records No Longer Accepted
1–10 of 31 posts
Re: Windows 8 Benchmark Records No Longer Accepted
#2Isn't this a problem on any os with cpu "speed stepping" ?
We lose seconds each day on our linux servers and have to use ntpd to stay in sync.
Re: Windows 8 Benchmark Records No Longer Accepted
#3Isn't this a problem on any os with cpu "speed stepping" ? We lose seconds each day on our linux servers and have to use ntpd to stay in sync.
Even 10 seconds a day only amounts to ~0.01% discrepancy. In this article they're reporting up to 7% if I'm reading it correctly.
EDIT: 7% of a day is just over 1h40m.
Re: Windows 8 Benchmark Records No Longer Accepted
#4Isn't this a problem on any os with cpu "speed stepping" ? We lose seconds each day on our linux servers and have to use ntpd to stay in sync.
The real-time clock on the motherboard should correct for this.
Re: Windows 8 Benchmark Records No Longer Accepted
#5Re: Windows 8 Benchmark Records No Longer Accepted
#6This has been a significant issue on the windows 8 machines I've handled. It's mitigated somewhat by creating your own scheduled task to more frequently do ntp updates.
I like this guide:
Re: Windows 8 Benchmark Records No Longer Accepted
#7Earlier quoted context omitted.
The real-time clock on the motherboard should correct for this.
Windows only reads clock at startup and writes it shutdown.
And so does my Fedora install (let's not blame Redmond unnecessarily).
My Android phone is even worse - it drifts by about 5-10s a day. Not a nightmare but it's still a lot more than my (probably unrealistic) expectations of 21st century hardware.
Re: Windows 8 Benchmark Records No Longer Accepted
#8Earlier quoted context omitted.
Windows only reads clock at startup and writes it shutdown.
And so does my Fedora install (let's not blame Redmond unnecessarily). My Android phone is even worse - it drifts by about 5-10s a day. Not a nightmare but it's still a lot more than my (probably unrealistic) expectations of 21st century hardware.
My car also has a drifting clock without a dynamic CPU, losing two minutes every three months. It also doesn't have the ability to sync with NTP so it can't correct itself.
Apparently clocks are hard.
Re: Windows 8 Benchmark Records No Longer Accepted
#9I'm a little confused. Does Windows 8 initially use the real time clock and the MHz as reference without checking if the MHz does change over time?
Re: Windows 8 Benchmark Records No Longer Accepted
#10Earlier quoted context omitted.
And so does my Fedora install (let's not blame Redmond unnecessarily). My Android phone is even worse - it drifts by about 5-10s a day. Not a nightmare but it's still a lot more than my (probably unrealistic) expectations of 21st century hardware.
My car also has a drifting clock without a dynamic CPU, losing two minutes every three months. It also doesn't have the ability to sync with NTP so it can't correct itself. Apparently clocks are hard.
Clocks are easy. Even accurate clocks are easy. However, accurate clocks are expensive which is where the problem is