From 913874367959f4f18a0299c91593c841e91b6808 Mon Sep 17 00:00:00 2001 From: qmuntal Date: Mon, 31 Jul 2023 11:00:40 +0200 Subject: [PATCH] time: mention time resolution in docs Updates #44343 Updates #53824 Change-Id: Ia7234fac4b1b88b3c331328aaa98dc85205e09ba Reviewed-on: https://go-review.googlesource.com/c/go/+/514275 Reviewed-by: David Chase TryBot-Result: Gopher Robot Reviewed-by: Ian Lance Taylor Run-TryBot: Quim Muntal --- src/time/time.go | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/src/time/time.go b/src/time/time.go index e8aac5999a..26872b1c05 100644 --- a/src/time/time.go +++ b/src/time/time.go @@ -76,6 +76,16 @@ // For debugging, the result of t.String does include the monotonic // clock reading if present. If t != u because of different monotonic clock readings, // that difference will be visible when printing t.String() and u.String(). +// +// # Timer Resolution +// +// Timer resolution varies depending on the Go runtime, the operating system +// and the underlying hardware. +// On Unix, the resolution is approximately 1ms. +// On Windows, the default resolution is approximately 16ms, but +// a lower resolution may be requested using [timeBeginPeriod]. +// +// [timeBeginPeriod]: https://learn.microsoft.com/en-us/windows/win32/api/timeapi/nf-timeapi-timebeginperiod package time import ( -- 2.50.0