Hacker News new | past | comments | ask | show | jobs | submit login

They tried it without going as far as bump-pointer allocation in the nursery, so I wouldn’t say that Go’s GC journey away from generational was due to measuring it and it not working. I don’t think anyone has high expectations for the performance of non-copying generational GC. IIRC the presentation just said they weren’t willing to try copying because they didn’t think it would be possible to maintain good latency. Which I think Azul and perhaps a future evolution of the new JVM collectors would have something the say about.



> Which I think Azul and perhaps a future evolution of the new JVM collectors would have something the say about.

That something is much higher memory requirement for same size workload as compared to Go.




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

Search: