The problem with GC isn't the "spikey 1%", it's the fact that GC implies the "everything is a pointer to an object" programming model, which in turn fragments your memory and destroys your cache.
Performance-oriented code implies everything is on the stack and/or packed into large arrays, at which point you don't need a GC after all.
Performance-oriented code implies everything is on the stack and/or packed into large arrays, at which point you don't need a GC after all.