I got that, and thanks for the link. But I'm not convinced a pool would have more overhead. It is basically the same thing (not really, but then again, pretty m

I got that, and thanks for the link. But I'm not convinced a pool would have more overhead. It is basically the same thing (not really, but then again, pretty much) just you can encode more information about the usage than a general GC can possible do. For sure there are other tradeoffs, and whether it is worth it. But when we actually see many GB/s that is not cheap even if you are able to offload to other cores. The article also concludes: >It is funny to consider that having TLABs is the way to experience more frequent GC pauses, just because the allocation is so damn cheap! Sounds like a nightmare, the problem just snowballs, because now you'll be tempted to get into GC tuning.