aboutsummaryrefslogtreecommitdiff
path: root/src/runtime/debug.go
diff options
context:
space:
mode:
authorMichael Pratt <mpratt@google.com>2023-10-10 15:28:32 -0400
committerGopher Robot <gobot@golang.org>2023-11-15 16:49:45 +0000
commit6ef98ac87c8a4185c0bace496d84cb3b68f069e3 (patch)
tree055a940a2beb55ca09c411bdf9accb49f054f7aa /src/runtime/debug.go
parenta0df23888fb30c82d8c54c24212442bf56211769 (diff)
downloadgo-6ef98ac87c8a4185c0bace496d84cb3b68f069e3.tar.xz
runtime/metrics: add STW stopping and total time metrics
This CL adds four new time histogram metrics: /sched/pauses/stopping/gc:seconds /sched/pauses/stopping/other:seconds /sched/pauses/total/gc:seconds /sched/pauses/total/other:seconds The "stopping" metrics measure the time taken to start a stop-the-world pause. i.e., how long it takes stopTheWorldWithSema to stop all Ps. This can be used to detect STW struggling to preempt Ps. The "total" metrics measure the total duration of a stop-the-world pause, from starting to stop-the-world until the world is started again. This includes the time spent in the "start" phase. The "gc" metrics are used for GC-related STW pauses. The "other" metrics are used for all other STW pauses. All of these metrics start timing in stopTheWorldWithSema only after successfully acquiring sched.lock, thus excluding lock contention on sched.lock. The reasoning behind this is that while waiting on sched.lock the world is not stopped at all (all other Ps can run), so the impact of this contention is primarily limited to the goroutine attempting to stop-the-world. Additionally, we already have some visibility into sched.lock contention via contention profiles (#57071). /sched/pauses/total/gc:seconds is conceptually equivalent to /gc/pauses:seconds, so the latter is marked as deprecated and returns the same histogram as the former. In the implementation, there are a few minor differences: * For both mark and sweep termination stops, /gc/pauses:seconds started timing prior to calling startTheWorldWithSema, thus including lock contention. These details are minor enough, that I do not believe the slight change in reporting will matter. For mark termination stops, moving timing stop into startTheWorldWithSema does have the side effect of requiring moving other GC metric calculations outside of the STW, as they depend on the same end time. Fixes #63340 Change-Id: Iacd0bab11bedab85d3dcfb982361413a7d9c0d05 Reviewed-on: https://go-review.googlesource.com/c/go/+/534161 Reviewed-by: Michael Knyszek <mknyszek@google.com> Auto-Submit: Michael Pratt <mpratt@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Diffstat (limited to 'src/runtime/debug.go')
-rw-r--r--src/runtime/debug.go4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/runtime/debug.go b/src/runtime/debug.go
index 1cd9189ed5..0e61692f3d 100644
--- a/src/runtime/debug.go
+++ b/src/runtime/debug.go
@@ -25,12 +25,12 @@ func GOMAXPROCS(n int) int {
return ret
}
- stopTheWorldGC(stwGOMAXPROCS)
+ stw := stopTheWorldGC(stwGOMAXPROCS)
// newprocs will be processed by startTheWorld
newprocs = int32(n)
- startTheWorldGC()
+ startTheWorldGC(stw)
return ret
}