understanding garbage collection logging

[Doug Whitfield]

Hi folks,

I come from java-land, and am having some trouble figuring out gc logging in go. I have been asked to contribute to a memory leak issue in Minio, which is written in Go.

I found https://www.ardanlabs.com/blog/2019/05/garbage-collection-in-go-part2-gctraces.html but I cannot tell if go is calling gc tracing what java calls logging, or if this is something different.

If it is the same, then does it work like in java where the JVM settings are separate from the app setting (and thus will work in any application)? This is my assumption, but since I was here I figured I would ask.

Basically, I want to see if gc activity is behaving as it should. Obviously, I have a lot to learn to be able to make anything out of the gc logging I am seeing since I won't be able to use my normal java tooling, but I figure before I spend a lot of time looking into this, I should find out from the experts if I am even going down the same path.

For the curious, I am suspicious of this: https://github.com/minio/minio/issues/19079

I think it should have been re-opened Feb 19. There isn't a merge or anything definitive that it should be closed...but that's a minio thing, not a go thing. Just some backstory for folks that see it has been "closed"

[Ian Lance Taylor]

On Thu, May 2, 2024 at 12:48 PM Doug Whitfield <dougl...@gmail.com> wrote:
>
> I come from java-land, and am having some trouble figuring out gc logging in go. I have been asked to contribute to a memory leak issue in Minio, which is written in Go.

The first way to try to rack down a memory leak is heap profiling.
For example see https://go.dev/blog/pprof, the section on -memprofile.

Ian

[Alexander Pavlov]

Please note the https://pkg.go.dev/runtime/trace package, its documentation and following article (https://go.dev/blog/execution-traces-2024) provide good examples to start logging the GC.

[Douglas A. Whitfield]

On Fri, 3 May 2024 at 13:05, Alexander Pavlov <pavale...@gmail.com> wrote:

Please note the https://pkg.go.dev/runtime/trace package, its documentation and following article (https://go.dev/blog/execution-traces-2024) provide good examples to start logging the GC.

Thank you! This is exactly what I needed!