News for hackers. Stuff that matters.

A comment on Understanding the Go Runtime: The Scheduler. Parent comment

Re:Understanding the Go Runtime: The Scheduler by melodyogonna on Friday March 13, 2026 @05:15AM (#47362161)
> If you have a system that requires predictable latency, go is not the right language for it.

Having a garbage collector already make this the case, it is a known trade off.

[ Parent | on HN ]
Re:Understanding the Go Runtime: The Scheduler by gf000 on Friday March 13, 2026 @05:27AM (#47362230)
This may have been practically true for a long time, but as Java's ZGC garbage collector proves, this is not a hard truth.

You can have world pauses that are independent of heap size, and thus predictable latency (of course, trading off some throughput, but that is almost fundamental)

[ Parent | on HN ]
Re:Understanding the Go Runtime: The Scheduler by pjmlp on Friday March 13, 2026 @09:56AM (#47364535)
Not really, it is a matter of having the right implementation.

- https://www.ptc.com/en/products/developer-tools/perc

- https://www.aicas.com/products-services/jamaicavm

- https://www.azul.com/products/prime

Not all GCs are born alike.

[ Parent | on HN ]
Re:Understanding the Go Runtime: The Scheduler by kevin_thibedeau on Friday March 13, 2026 @10:43AM (#47365173)
Nim's GC is deterministic when you need it.
[ Parent | on HN ]
Re:Understanding the Go Runtime: The Scheduler by melodyogonna on Friday March 13, 2026 @08:28PM (#47371911)
How so?
[ Parent | on HN ]
Re:Understanding the Go Runtime: The Scheduler by kevin_thibedeau on Saturday March 14, 2026 @12:10AM (#47373253)
You can run it for fixed timeslices.
[ Parent | on HN ]