Circle back on this. The forced GC turned out to be triggered by a module
injected to the application code through the LD_PRELOAD. It was not the go
library's internal 2 minutes GC that triggered it. It was hard to figure
this out because the module was a total blackbox :) Thank you for trying to
h
On Fri, Nov 1, 2024 at 9:15 PM Siyuan Liu wrote:
>
> There is this strange behavior on a Golang service we are running.
>
> On some instances, there is a forced GC that gets triggered every 4 minutes.
> This can be observed when the `GODEBUG=gctrace=1` is turned on. There is a
> log line with `g
There is this strange behavior on a Golang service we are running.
On some instances, there is a forced GC that gets triggered every 4
minutes. This can be observed when the `GODEBUG=gctrace=1` is turned on.
There is a log line with `gc ... (forced)` every 4 minutes consistently on
selected ins
