cockroachdb / cockroachdb/cockroach

observability: increase Go runtime scheduling latency histogram max

Open
#121,729 0 comments 0 reactions 0 assignees View on GitHub
A-cluster-observability C-enhancement T-supportability
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

The Go runtime scheduling latency histogram has a max bucket threshold of 100ms. We frequently see histogram values in the max bucket, which suggests there are Go scheduling latency events >100ms. These high latency events can be disruptive depending on the goroutine that goes unscheduled. We should consider lifting the max bucket threshold to capture more data about the tail of scheduling latencies.

Relevant internal slack thread: https://cockroachlabs.slack.com/archives/C063CP41TG9/p1707946050906159

Jira issue: CRDB-37471

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.