News for hackers. Stuff that matters.

A comment on Memory Management Reference. Parent comment

Re:Memory Management Reference by tomp on Tuesday July 12, 2022 @03:27PM (#32074565)
All of the ones you mentioned above still involve a stop-the-world phase, however brief.

The keywords you’re looking for are “fullya-concurrent” or “on-the-fly” GC, but I’m not aware of any production runtime with those.

[ Parent | on HN ]
Re:Memory Management Reference by WJW on Tuesday July 12, 2022 @04:21PM (#32075138)
Doesn't the JVM ecosystem have fully concurrent GC with the Azul C4 collector? It's not my favorite set of languages but I don't think we can realistically claim the JVM is not a production-ready runtime.
[ Parent | on HN ]
Re:Memory Management Reference by tomp on Tuesday July 12, 2022 @05:39PM (#32076016)
Yes, "pauseless" is another keyword I forgot to mention.

Azul uses a read barrier which I guess makes it so slow that noone uses it (and the same ideas haven't made their way into JDK collectors). The previous version required hardware-supported read barrier, now AFAIK they only require a Linux kernel extension.

[ Parent | on HN ]