On Tue, Oct 24, 2017 at 12:38 PM, Juliusz Chroboczek wrote:
>
>> It depends entirely on your program. The simplest way to think about
>> it is that the runtime imposes an overhead on the memory that your
>> program allocates for its own data structures. If you think of that
>> overhead as 10%, y
> It depends entirely on your program. The simplest way to think about
> it is that the runtime imposes an overhead on the memory that your
> program allocates for its own data structures. If you think of that
> overhead as 10%, you won't be very far wrong.
How does that fit with GOGC being 100%
> It depends entirely on your program. The simplest way to think about
> it is that the runtime imposes an overhead on the memory that your
> program allocates for its own data structures. If you think of that
> overhead as 10%, you won't be very far wrong.
How does that fit with GOGC being 100%
Hey Ben,
You can use the pprof and trace tools to find answers to those questions
yourself. Some links:
https://blog.golang.org/profiling-go-programs
https://golang.org/pkg/runtime/trace/
https://github.com/pkg/profile
justforfunc #22 also talks about using those tools
(https://www.youtube.co
