Thank you for your answer, I now understand a bit better what is going on.
On Sun, Oct 16, 2016 at 7:56 PM, andrey mirtchovski
wrote:
> > Here some pprof result using go 1.7.1 first and tip later:
>
> If I understand you correctly, you still have questions about memory
> management, but the natu
> Here some pprof result using go 1.7.1 first and tip later:
If I understand you correctly, you still have questions about memory
management, but the nature of the question has changed from "why does
this function keep increasing memory consumption" to "why does my
program consume so much memory"?
Here some pprof result using go 1.7.1 first and tip later:
go tool pprof -alloc_space lushan-server https:
//localhost:8083/debug/pprof/heap
Fetching profile from https://localhost:8083/debug/pprof/heap
Saved profile in /Users/rdifazio/pprof/pprof.lushan-server.localhost:
8083.alloc_objects.all
I haven't tried tip yet, but I saw this patch yesterday. It looks like this
might help as I'm not using these pools directly. Over time though, I would
expect the GC to free the memory allocated. It's true that I see much lower
values in the profiler for the in_use memory, but I wonder why my ma
Does this happens on tip too? There was a recent CL that
modified the code of the nat pool; see
https://go-review.googlesource.com/#/c/30613/
exp. the "Eliminate allocation in divLarge nat pool" part.
Il giorno sabato 15 ottobre 2016 16:28:01 UTC+2, Raffaele Di Fazio ha
scritto:
>
> Hi,
> I h
