Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> GC pauses: very slow (until Go anyway)

If by "slow" you mean "high latency", then this isn't true. Plenty of GC algorithms provide guaranteed sub-millisecond pauses.



It wasn't the norm until Go focused on it though, and "sub milliseconds" is not a high bar. Malloc is much much faster than that.


> It wasn't the norm until Go focused on it though

It's still not the norm, but the point is that those were available

> and "sub milliseconds" is not a high bar. Malloc is much much faster than that.

Malloc is not guaranteed to return in that time frame. The sub-millisecond latency of these GCs is a real-time guarantee.


> Malloc is not guaranteed to return in that time frame

No but in practice it always does.


It doesn't though, which is why malloc is rarely used in embedded and realtime systems.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: