News for hackers. Stuff that matters.

A comment on Go memory ballast: How I learnt to stop worrying and love the heap.

Re:Go memory ballast: How I learnt to stop worrying and love... by earthboundkid on Monday December 02, 2019 @08:59AM (#21682295)
A) This is from April. It's being resubmitted because the URL changed.

B) In a non-memory managed language, wouldn't you just run into the same problem except it's called "heap fragmentation" instead and malloc has to do an unreasonable amount of work to find free blocks to use?

[ Parent | on HN ]
Re:Go memory ballast: How I learnt to stop worrying and love... by bboreham on Monday December 02, 2019 @12:38PM (#21684641)
B. no, it’s quite subtle but this is just tweaking a housekeeping parameter inside the garbage collector.
[ Parent | on HN ]
Re:Go memory ballast: How I learnt to stop worrying and love... by masklinn on Tuesday December 03, 2019 @01:31AM (#21690428)
No, the issue here is not fragmentation or allocation itself, it’s that the GC heuristics make it way too aggressive to keep memory down (burning cpu the application could use for productive things) despite only a small fraction of the machine’s memory being used.
[ Parent | on HN ]