[go-nuts] documentation for dlog output

At the end of dlog trace, we get the following. These seem like basic assembly instructions with addresses but I have no idea what any of it means, and I can't find any documentation for it. Can someone take the time to go through the significance of each one by one, and that way at least if

[go-nuts] Re: discrepancy between goal heap size and NextGC

number of completed GC cycles, where a GC // cycle is sweep termination, mark, mark termination, and // sweep. This differs from memstats.numgc, which is // incremented at mark termination. cycles uint32 On Monday, January 29, 2024 at 7:12:53 AM UTC-5 Michael Mitchell wrote: > In the twelfth garb

[go-nuts] discrepancy between goal heap size and NextGC

In the twelfth garbage collection of a short program I ran, GC trace reports the goal heap size as 735 MB (see below for gc11, gc12 and gc13 from GC trace) I also checked runtime Memstats (see attached image), and it says the nextGC target after 12 GCs have run is 838103616. Should goal Heap

[go-nuts] pauseEnd times in runtime.Memstats

In runtime.Memstates, one of the stats given is the timestamps for the last 256 garbage collections in the PauseEnd array, i.e. when those garbage collections took place. So if you subtract one timestamp from another, you can find out how much time took place between garbage collections. Is th

[go-nuts] garbage collections on Windows and Mac

Hi, I have noticed on my macbook pro that HeapInUse is always slightly above NextGC when the garbage collection occurs. According to mstats.go, the "garbage collector's goal is to keep HeapAlloc less than NextGC" and also according to mstats.go, "HeapInUse minus HeapAlloc estimates the amou