News for hackers. Stuff that matters.

A comment on A 40ms Go garbage collector pause caused by swap. Parent comment

Re:A 40ms Go garbage collector pause caused by swap by rwmj on Monday October 05, 2026 @04:32AM (#49962163)
Only in very bad implementations of GC.
[ Parent | on HN ]
Re:A 40ms Go garbage collector pause caused by swap by delamon on Monday October 05, 2026 @09:58AM (#49965005)
By that definition, Go has very bad GC. Many (myself included) would strongly disagree with this.
[ Parent | on HN ]
Re:A 40ms Go garbage collector pause caused by swap by rwmj on Monday October 05, 2026 @11:44AM (#49966367)
Every memory management scheme makes trade-offs (even manual ones), and golang's is no different. It seems to work well in many scenarios.
[ Parent | on HN ]
Re:A 40ms Go garbage collector pause caused by swap by pebal on Monday October 05, 2026 @10:48AM (#49965621)
It is better to scan everything than to copy it.
[ Parent | on HN ]
Re:A 40ms Go garbage collector pause caused by swap by delamon on Monday October 05, 2026 @12:19PM (#49966867)
The op, most likely, was referring to generational GCs. Golang notably doesn't have one.
[ Parent | on HN ]