Re: [go-nuts] Interpretting the pprof memory profile

2019-06-01 Thread Patrik Iselind
The reason I think there are 0: 0 entries is because the profile is fresh but the memory is from the previous GC, which are most likely not the same point in time. Does this make sense? It seem strange to me that the GC would leave garbage around at random. I don't think it does. Den onsdag 23

Re: [go-nuts] Interpretting the pprof memory profile

2019-01-22 Thread Patrik Iselind
Den tisdag 22 januari 2019 kl. 22:14:20 UTC+1 skrev Ian Lance Taylor: > > On Tue, Jan 22, 2019 at 11:21 AM Patrik Iselind > wrote: > > > > I'm looking at memory profiles and have a hard time interpreting what I > see. I'm trying to better understand what I am looking at in `go tools > pprof`

Re: [go-nuts] Interpretting the pprof memory profile

2019-01-22 Thread Ian Lance Taylor
On Tue, Jan 22, 2019 at 11:21 AM Patrik Iselind wrote: > > I'm looking at memory profiles and have a hard time interpreting what I see. > I'm trying to better understand what I am looking at in `go tools pprof` why > looking at the raw data. All 'groups' at the end of output from > /debug/pprof

[go-nuts] Interpretting the pprof memory profile

2019-01-22 Thread Patrik Iselind
Hi, I'm looking at memory profiles and have a hard time interpreting what I see. I'm trying to better understand what I am looking at in `go tools pprof` why looking at the raw data. All 'groups' at the end of output from /debug/pprof/heap have lines that begin with "0: 0 [0: 0] @0x...". It