Consider running with GOGC=25 (not 100)

[Al2Klimov]

To GC earlier and reduce memory spikes.

[Al2Klimov]

The GOGC variable sets the initial garbage collection target percentage. A collection is triggered when the ratio of freshly allocated data to live data remaining after the previous collection reaches this percentage. The default is GOGC=100.

– https://pkg.go.dev/runtime

[julianbrost]

This is a classic tradeoff between memory and CPU usage. Given that syncing data shouldn't be CPU-bound in the Go process, I think we can afford using a bit more CPU to keep memory usage lower. But before doing this, we should evaluate this a bit and play around with different values.

[oxzi]

I would suggest closing this issue. Unless there are exact reasons being identified as major GC cost factors, I would strongly advertise against messing with it.