4 ms·
Of course, but it's treatable. Large applications deployed on traditional heap implementations do not, as a general rule, suffer from the kind of GC tuning voo
by ajross 8y ago
Of course, but it's treatable. Large applications deployed on traditional heap implementations do not, as a general rule, suffer from the kind of GC tuning voodoo that plagues the JVM and which inspired ZGC and Shenandoah (and two decades of their ancestors!).
There's no free lunch, but if you know heap behavior is a performance issue in a giant C++ app or whatever, you have a big list of tools with which to address it in software. And in practice this works. Large deployments of, say, PostgreSQL don't require that the admins tune the allocation strategy of the process or carefully size the heap memory internal to the process (obviously there is external tuning at the OS level, though).
- mcguire 8y agoIt's treatable, but not while maintaining deterministic behavior. And I'm a little unclear what the difference in practice is between "GC tuning voodoo" and "a big list of tools". ("external tuning at the OS level" ?= that's not one of your big list of tools)
- spullara 8y agoIf you haven't measured the difference between different allocators for your C++ programs you are probably using the wrong one. The system allocator can be 2-5x slower than an allocator that more closely matches your workload.
- pron 8y agoThere are always tools that help you improve performance, be it with code changes or tuning. The question is how much effort is required to achieve the required performance. I think that the past twenty years have shown that for a huge portion of server applications, GCs are the approach most developers prefer.