mirror of
https://github.com/golang/go.git
synced 2025-12-08 06:10:04 +00:00
runtime: add scavtrace debug flag and remove scavenge info from gctrace
Currently, scavenging information is printed if the gctrace debug variable is >0. Scavenging information is also printed naively, for every page scavenged, resulting in a lot of noise when the typical expectation for GC trace is one line per GC. This change adds a new GODEBUG flag called scavtrace which prints scavenge information roughly once per GC cycle and removes any scavenge information from gctrace. The exception is debug.FreeOSMemory, which may force an additional line to be printed. Fixes #32952. Change-Id: I4177dcb85fe3f9653fd74297ea93c97c389c1811 Reviewed-on: https://go-review.googlesource.com/c/go/+/212640 Run-TryBot: Michael Knyszek <mknyszek@google.com> Reviewed-by: Austin Clements <austin@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
This commit is contained in:
parent
509592d188
commit
8ac98e7b3f
5 changed files with 51 additions and 28 deletions
|
|
@ -240,6 +240,11 @@ type pageAlloc struct {
|
|||
// The address to start a scavenge candidate search with.
|
||||
scavAddr uintptr
|
||||
|
||||
// The amount of memory scavenged since the last scavtrace print.
|
||||
//
|
||||
// Read and updated atomically.
|
||||
scavReleased uintptr
|
||||
|
||||
// start and end represent the chunk indices
|
||||
// which pageAlloc knows about. It assumes
|
||||
// chunks in the range [start, end) are
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue