-
Notifications
You must be signed in to change notification settings - Fork 17.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
runtime: document gctrace output in relation to MemStats #46846
Comments
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only. For questions please refer to https://github.com/golang/go/wiki/Questions |
@seankhliao In that case, please re-open this as a documentation bug. It should be documented. |
I'm hoping to do something around documentation of how the GC views memory and the heap in the 1.18, so I've assigned it to myself. I'll leave it in the backlog just in case, but it's on my radar. |
Change https://go.dev/cl/504115 mentions this issue: |
There's more I could list here, but the mapping becomes more complicated and more fragile. I think this is sufficient to start with. Fixes golang#46846. Change-Id: I6803486a64888b2f38e244b8e2175ad064d648ed Reviewed-on: https://go-review.googlesource.com/c/go/+/504115 Reviewed-by: Michael Pratt <mpratt@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Michael Knyszek <mknyszek@google.com> Auto-Submit: Michael Knyszek <mknyszek@google.com>
How do the heap sizes output by gctrace map to the various values of MemStats? I assume that the heap values from gctrace roughly match one (or two?) of the MemStats fields, but I can't find anything that documents that.
I see in the code that the gctrace outputs are mostly based on
heap_live
and the MemStats values are not (directly) based on the the same thing... but I'm guessing there's an indirect or approximate link. Knowing such a mapping would help a lot in using gctrace, since it doesn't have heaps of documentation but MemStats has lots.The text was updated successfully, but these errors were encountered: