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

Here it wasn't the problem, that the GC was lacking performance when collecting garbage, which a pool allocator would have helped with, but rather, that they didn't produce garbage (good), but the GC ran nevertheless to check whether memory could be returned to the OS. Probably supressing that would have removed the spikes.


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

Search: