/ go Public
runtime: document gctrace output in relation to MemStats #46846
Issues related to the Go compiler and/or runtime.
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
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_liveand 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: