Clock moves backwards: big old 168817 > 168816 (for example)

On Windows systems (and sometimes seen on MACs and Linux systems), ascp will log the errors:

2010-07-04 09:48:17 [1f20-1c08] ERR getnstore_usec_since: big old 168817 > 168816
2010-07-04 09:48:18 [1f20-1c08] ERR getnstore_usec_since: big old 168818 > 168817

This indicates that when ascp requested the system for the CPU tick count, it received a value that was less than the last time it requested the count. This would indicate that the clock has moved backwards. This happens when the CPU clocks are not perfectly synchronized in a multicore system If this occurs more than just one or two times in a log, it can have a dramatic effect on the transfer rates. This is mostly a problem in Windows. The solution for Windows is to download and install the latest motherboard drivers from the manufacturer of the motherboard. Be sure to download the latest motherboard drivers, and not a BIOS upgrade, or firmware, which may be beneficial, but will not solve this problem. Attached are some test binaries for testing the clock synchronization on Windows, Linux-32bit and Linux-64bit. They should be run for at least five minutes. They will show the accuracy of the system clock, and will fail if the clock runs backwards.


Powered by Zendesk