Skip to content

runtime: recompute timer channel send delay at send time - #80894

Open
dniminenn wants to merge 1 commit into
golang:masterfrom
dniminenn:timer-send-delay
Open

runtime: recompute timer channel send delay at send time#80894
dniminenn wants to merge 1 commit into
golang:masterfrom
dniminenn:timer-send-delay

Conversation

@dniminenn

@dniminenn dniminenn commented Aug 16, 2026

Copy link
Copy Markdown

time.sendTime reconstructs the delivered value as Now().Add(-delta),
but unlockAndRun computes delta from a cached clock read, so the work
between that read and the send lands in the delivered value as
one-sided, load-dependent error. Recompute delta immediately before
the send, matching its documented definition, nanotime() - t.when, at
the moment of use.

Fixes #80893

The timer struct documents the delay argument as nanotime() - t.when.
time.sendTime uses it to reconstruct the delivered value as
Now().Add(-delta). unlockAndRun computes delta from the now cached by
the caller. The heap update, the sendLock acquisition, other timers
due in the same timers.run pass, and preemption of the timer-running M
all happen after that clock read. Their duration lands in the
delivered value as one-sided, load-dependent error. The common case is
a few hundred nanoseconds. Under scheduler or interrupt pressure the
error reaches several microseconds.

Consumers that bin ticker values against a wall-clock grid see the
outliers as phantom missed ticks. A value that crosses a period
boundary makes floor arithmetic count two elapsed periods where one
elapsed.

Recompute delta immediately before the send. This matches its
documented definition at the moment of use, and the reconstruction
then recovers the fire time to within two adjacent clock reads.
Measured on linux/amd64 (i5-8500, idle), the mean error of 1s ticker
values against the scheduled grid drops from ~600ns with one-sided
tails beyond 1.4us to 0ns +/- 0.5us with no observed tails. The cost
is one nanotime call per channel-timer firing. Synctest bubbles keep
their fake-clock delta.

Fixes golang#80893
@gopherbot

Copy link
Copy Markdown
Contributor

This PR (HEAD: 69e386c) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/815940.

Important tips:

  • Don't comment on this PR. All discussion takes place in Gerrit.
  • You need a Gmail or other Google account to log in to Gerrit.
  • To change your code in response to feedback:
    • Push a new commit to the branch used by your GitHub PR.
    • A new "patch set" will then appear in Gerrit.
    • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
    • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
    • Multiple commits in the PR will be squashed by GerritBot.
  • The title and description of the GitHub PR are used to construct the final commit message.
    • Edit these as needed via the GitHub web interface (not via Gerrit or git).
    • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
  • See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

@gopherbot

Copy link
Copy Markdown
Contributor

Message from Gopher Robot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
A maintainer will review your change and provide feedback. See
https://go.dev/doc/contribute#review for more info and tips to get your
patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11 or adds a tag like "wait-release", it means that this CL will be
reviewed as part of the next development cycle. See https://go.dev/s/release
for more details.


Please don’t reply on this GitHub thread. Visit golang.org/cl/815940.
After addressing review feedback, remember to publish your drafts!

@gopherbot

Copy link
Copy Markdown
Contributor

Message from Ian Lance Taylor:

Patch Set 1:

(1 comment)


Please don’t reply on this GitHub thread. Visit golang.org/cl/815940.
After addressing review feedback, remember to publish your drafts!

@gopherbot

Copy link
Copy Markdown
Contributor

Message from jl:

Patch Set 2:

(2 comments)


Please don’t reply on this GitHub thread. Visit golang.org/cl/815940.
After addressing review feedback, remember to publish your drafts!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

time: Ticker channel values deviate from the fire time by a one-sided, load-dependent error

2 participants