Shenandoah in OpenJDK 17: Sub-millisecond GC pauses

Re:Shenandoah in OpenJDK 17: Sub-millisecond GC pauses by avianlyric on Friday September 17, 2021 @07:48AM (#28564307)

Erm something is managing your memory somewhere, even "the computer explodes before it runs out of memory" methodology used in guided missiles is a form of manual memory management, just a very unusual one.

Same applies to the "program terminates before it runs out of memory" approach.

[ Parent | on HN ]

Re:Shenandoah in OpenJDK 17: Sub-millisecond GC pauses by ncmncm on Friday September 17, 2021 @06:10PM (#28571470)

Yes, something is managing my memory. Just not GC, and not reference counting (which is also GC). As I said.

C++ has destructors, and owning pointers (called "unique_ptr"), and also arena allocators for when those are useful. Rust has its Drop trait and analogs of the other things. (Use of arenas with Rust standard library containers is approaching maturity.) They make memory management automatic and wholly painless. Both languages offer reference-counted GC for places where that is helpful, but such places are rare, and where used typically burn an unmeasurably small fraction of runtime, with no "pauses".

[ Parent | on HN ]

Re:Shenandoah in OpenJDK 17: Sub-millisecond GC pauses by avianlyric on Tuesday September 21, 2021 @01:02PM (#28607112)

Using destructors just reference counting done the hard way.

> burn an unmeasurably small fraction of runtime

That’s also known as a very short pause.

[ Parent | on HN ]