|
System Demands of ClockWatch
The demands of ClockWatch, when used in most modes are minimal.
Sequence of Events when making a setting:
ClockWatch requests a Windows socket (Winsock) type connection to the NIST timeserver
ClockWatch receives the time string from the NIST
ClockWatch converts and compares the NIST time to local time.
A setting is made if there is a difference in times.
Internet Traffic: Since the communication over the Internet is minimal ClockWatch should not have any significant impact on Internet communications traffic since only one packet is received for each setting request.
System Resources: ClockWatch spends most of its time in the sleep mode, waiting for a scheduled setting to occur or waiting for user input. ClockWatch uses one of the native operating system timers, which are finite in number.
Testing has shown that most users experience approximately a 1% increase in system utilization when viewed by the NT System Monitor when in the sleep mode with less than 5% increase when actually making a setting.
|
|
