News for hackers. Stuff that matters.

A comment on Go GC: Solving the Latency Problem in Go 1.5. Parent comment

Re:Go GC: Solving the Latency Problem in Go 1.5 by fauigerzigerk on Thursday July 09, 2015 @10:41AM (#9858077)
>Memory overhead: A non-copying GC has none

Do you have any idea what could make the Go folks ask for "in-memory heap sizes twice as large as reachable memory"? This seems to be completely at odds with what you are saying.

[ Parent | on HN ]
Re:Go GC: Solving the Latency Problem in Go 1.5 by rurban on Thursday July 09, 2015 @11:59AM (#9858676)
Why? Reserving virtual memory has nothing to do with actual memory usage.
[ Parent | on HN ]
Re:Go GC: Solving the Latency Problem in Go 1.5 by fauigerzigerk on Thursday July 09, 2015 @01:28PM (#9859361)
It would be great if they really mean virtual memory, but I very much doubt it as it makes no sense as a goal and is inconsistent with mentioning "Hardware provisioning".
[ Parent | on HN ]