System time is measured by a system clock, which is typically implemented as a simple count of the number of ticks that have transpired since some arbitrary starting date, called the epoch. For example, Unix and POSIX-compliant systems encode system time ("Unix time") as the number of seconds elapsed since the start of the Unix epoch at 1 January 1970 00:00:00 UT, with exceptions for leap seconds. Systems that implement the 32-bit and 64-bit versions of the Windows API, such as Windows 9x and Windows NT, provide the system time as both SYSTEMTIME, represented as a year/month/day/hour/minute/second/milliseconds value, and FILETIME, represented as a count of the number of 100-nanosecond ticks since 1 January 1601 00:00:00 UT as reckoned in the proleptic Gregorian calendar.
System time can be converted into calendar time, which is a form more suitable for human comprehension. For example, the Unix system time 1000000000 seconds since the beginning of the epoch translates into the calendar time 9 September 2001 01:46:40 UT. Library subroutines that handle such conversions may also deal with adjustments for timezones, daylight saving time (DST), leap seconds, and the user's locale settings. Library routines are also generally provided that convert calendar times into system times.
Closely related to system time is process time, which is a count of the total CPU time consumed by an executing process. It may be split into user and system CPU time, representing the time spent executing user code and system kernel code, respectively. Process times are a tally of CPU instructions or clock cycles and generally have no direct correlation to wall time.
Most first-generation PCs did not keep track of dates and times. These included systems that ran the CP/M operating system, early models of the Apple II, and the Commodore PET, among others. The IBM PC was the first widely available personal computer that came equipped with date/time hardware built into the motherboard, and subsequent add-on peripheral boards included real-time clock chips with on-board battery back-up. Prior to the widespread availability of computer networks, most personal computer systems that did track system time did so only with respect to local time and did not make allowances for other time zones.
With current technology, all modern computers keep track of local civil time, as do many other household and personal devices such as VCRs, DVRs, cable TV receivers, PDAs, pagers, cell phones, fax machines, telephone answering machines, cameras, camcorders, central air conditioners, and microwave ovens.
The system clock is typically implemented as a programmable interval timer that periodically interrupts the CPU, which then starts executing a timer interrupt service routine. That routine typically adds one tick to the system clock (a simple counter) and handles other periodic housekeeping tasks (preemption, etc.) before returning to whatever the CPU was doing before the interruption.
The following tables illustrate methods for retrieving the system time in various operating systems, programming languages, and applications. Values marked by (*) are system-dependent and may differ across implementations. All dates are given as Gregorian or proleptic Gregorian calendar dates.
Note that the resolution of an implementation's measurement of time does not imply the same accuracy of such measurements. For example, a system might return the current time as a value measured in microseconds, but actually be capable of discerning individual clock ticks with a frequency of only 100 Hz (10 ms).
|Operating system||Command or function||Resolution||Epoch or range|
|1 ms||1 January 1970|
|BIOS (IBM PC)||INT 1Ah,AH=00h1||54.931 ms
|Midnight of the current day|
|INT 1Ah,AH=02h2||1 s||Midnight of the current day|
|INT 1Ah,AH=04h3||1 day||1 January 1980 to (system dependent)|
|10 ms||1 January 1980 to 31 December 2099|
|Mac OS (Apple)||CFAbsoluteTimeGetCurrent()5||< 1 ms 6note 1||1 January 2001 ±10,000 years6note 1|
|OpenVMS (HP)||SYS$GETTIM()||100 ns||17 November 1858 to AD 31,086|
|z/OS (IBM)||STCK7||2−12 μs
|1 January 1900 to 17 September 2042 UT9|
|Unix, POSIX (see also C date and time functions)||date
1 January 1970 to 19 January 2038
1 January 1970 to AD 292,277,026,596
|Windows (Microsoft)||GetSystemTime()||1 ms||1 January 1601 to AD 30,828|
|Language/Application||Function or variable||Resolution||Epoch or range|
|Ada||Ada.Calendar.Clock||100 μs to
20 ms (*)
|1 January 1901 to 31 December 2099 (*)|
|BASIC, True BASIC||DATE, DATE$
|Business BASIC||DAY, TIM||0.1 s||(*)|
|C (see C date and time functions)||time()||1 s (*)note 2||(*)note 2|
|C++||std::time()||1 s (*)note 2||(*)note 2|
|100 ns 12||1 January 0001 to 31 December 9999|
|CICS (IBM)||ASKTIME||1 ms||1 January 1900|
|COBOL||FUNCTION CURRENT-DATE||1 s||1 January 1601|
|Common Lisp||(get-universal-time)||1 s||1 January 1900|
|1 January 1900|
|Emacs Lisp||(current-time)||1 μs (*)||1 January 1970|
|Excel (Microsoft)||date()||?||0 January 190013|
|(*)14||1 January 1970|
|Go||time.Now()||1 ns||1 January 0001|
|Haskell||Time.getClockTime||1 ps (*)||1 January 1970 (*)|
|Data.Time.getCurrentTime||1 ps (*)||17 November 1858 (*)|
|1 ms||1 January 1970|
|System.nanoTime()16||1 ns||arbitrary 16|
|1 ms||1 January 1970|
|Matlab||now||1 s||0 January 000017|
|MUMPS||$H (short for $HOROLOG)||1 s||31 December 1840|
|Objective-C||[NSDate timeIntervalSinceReferenceDate]||< 1 ms18||1 January 2001 ±10,000 Years18|
|OCaml||Unix.time()||1 s||1 January 1970|
|Extended Pascal||GetTimeStamp()||1 s||(*)|
|Perl||time()||1 s||1 January 1970|
|1 s||1 January 1970|
|Python||time.time()||1 μs (*)||1 January 1970|
|1 s||1 January 0001 to 31 December 9999|
|CURRENT(TIMESTAMP), %TIMESTAMP||1 μs|
|Ruby||Time.now()20||1 μs (*)||1 January 1970 (to 19 January 2038 prior to Ruby 1.9.221)|
|1 s (ANSI)
1 μs (VisualWorks)
1 s (Squeak)
|1 January 1901 (*)|
|3 ms||1 January 1753 to 31 December 9999 (*)|
|60 s||1 January 1900 to 6 June 2079|
|Standard ML||Time.now()||1 μs (*)||1 January 1970 (*)|
|TCL||[clock seconds]||1 s||1 January 1970|
|[clock milliseconds]||1 ms|
|[clock microseconds]||1 μs|
|[clock clicks]||1 μs (*)||(*)|
|Windows PowerShell||Get-Date22||100 ns 12||1 January 0001 to 31 December 9999|
|Visual Basic .NET (Microsoft)||System.DateTime.Now10
|100 ns 12||1 January 0001 to 31 December 9999|
- The Apple Developer Documentation is not clear on the precision & range of CFAbsoluteTime/CFTimeInterval, except in the CFRunLoopTimerCreate documentation which refers to 'sub-millisecond at most' precision. However, the similar type NSTimeInterval appears to be interchangeable, and has the precision and range listed.
- The C standard library does not specify any specific resolution, epoch, range, or datatype for system time values. The C++ library encompasses the C library, so it uses the same system time implementation as C.
- Ralf Brown, "Int 0x1A, AH=0x00" in Ralf Brown's Interrupt List, 2000, http://www.delorie.com/djgpp/doc/rbinter/ix/1A/00.html
- Ralf Brown, "Int 0x1A, AH=0x02" in Ralf Brown's Interrupt List, 2000, http://www.delorie.com/djgpp/doc/rbinter/ix/1A/02.html
- Ralf Brown, "Int 0x1A, AH=0x04" in Ralf Brown's Interrupt List, 2000, http://www.delorie.com/djgpp/doc/rbinter/ix/1A/04.html
- Ralf Brown, "Int 0x21, AH=0x2c" in Ralf Brown's Interrupt List, 2000, http://www.delorie.com/djgpp/doc/rbinter/ix/21/2C.html
- "Time Utilities Reference" in Mac OS X Developer Library (Apple, 2007).
- "CFRunLoopTimer Reference" in Mac OS X Developer Library (Apple, 2007).
- z/Architecture Principles of Operation (Poughkeepsie, New York:International Business Machines, 2007) 7-187.
- z/Architecture Principles of Operation, (Poughkeepsie, New York:International Business Machines, 2000) 4-45, 4-46.
- IBM intends to extend the date range on future systems beyond 2042. z/Architecture Principles of Operation, (Poughkeepsie, New York:International Business Machines, 2007) 1-15, 4-45 to 4-47.
- "DateTime.Now Property" in MSDN (Microsoft, 2010) last updated July 2010.
- "DateTime.UtcNow Property" in MSDN (Microsoft, 2011)
- "DateTime.Ticks Property in MSDN (Microsoft, 2010) last updated May 2010.
- "In the Microsoft Office Spreadsheet Component, the value 0 evaluates to the date December 30, 1899 and the value 1 evaluates to December 31, 1899. ... In Excel, the value 0 evaluates to January 0, 1900 and the value 1 evaluates to January 1, 1900." XL2000: Early Dates on Office Spreadsheet Component Differ from Excel in (Microsoft Support, 2003).
- "SYSTEM_CLOCK", documentation for FORTRAN compiler, Intel Corp., accessed 27 October 2011.
- SYSTEM_CLOCK — Time function" in The GNU Fortran Compiler (Free Software Foundation) accessed 27 October 2011.
- System.nanoTime() method in Java Platform, Standard Edition 6: API Specification (Oracle, 2011) accessed 27 October 2011.
-  Matlab Help
- "Foundation Data Types Reference" in Mac OS X Developer Library (Apple, 2011) last modified 6 July 2011, section NSTimeInterval.
- Douglas Wegscheild, R. Schertler, and Jarkko Hietaniemi, "Time::HiRes" (CPAN Comprehensive Perl Archive Network, 2011) accessed 27 October 2011.
- Time class in Ruby-Doc.org: Help and documentation for the Ruby programming language (Scottsdale, AZ: James Britt and Neurogami) accessed 27 October 2011.
- Ruby 1.9.2 Release Notes in Ruby-Doc.org: Help and documentation for the Ruby programming language (Scottsdale, AZ: James Britt and Neurogami) accessed 27 October 2011.
- "Get-Date" in Microsoft TechNet,dead link.
- Critical and Significant Dates, J. R. Stockton (retrieved 1 September 2006)
- The Boost Date/Time Library (C++)
- The Boost Chrono Library (C++)
- The Chronos Date/Time Library (Smalltalk)
- Joda Time, The Joda Date/Time Library (Java)
- The Perl DateTime Project (Perl)
- The Ruby Date/Time Library (Ruby)
Return to Fuhz Home - This article covering System time is enhanced for the visually impaired.
The text of this Fuhz article is released under the GNU Free Documentation License