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

Memory usage is a real problem once you have large amounts of data, of course Go is GC’d and so has a substantial memory hit anyway so I understand weighing that aspect less.

The real killer once that’s factored out is cache performance, and that really is a killer: for high performance code you can easily lose double digit %s of perf hit. You can do even worse in, but in the optimal case (a flat array) load predictors and prefetchers get you to only 10-20% hit from cache pressure.

This is my recollection from maybe 5 years ago (hell maybe even 10), so it could be worse now.



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

Search: