> That's true for copying generational garbage collectors. You only need to copy the live stuff and forget everything else. But in e.g. a mark-sweep collector,

> That's true for copying generational garbage collectors. You only need to copy the live stuff and forget everything else. But in e.g. a mark-sweep collector, sweeping dead stuff takes time. In particular, e.g. Chromium's Oilpan can take a long time in the sweeping phase, when there are lot of dead objects. Sure. I got confused why people do these designs which seem to me to be an awkward compromise, but yes they exist. > But when there are a lot of microallocations, you also have a lot of live objects, which could otherwise be just a single object in the case of e.g. big arrays. Not necessary in general. Sure with the array, and I agree that is a bit silly. But there is no general law that more microallocations means more live data. > Hmm, seems I highlighted the wrong aspect.... Sure those things sound sensible. I don't mean to disagree with any of that.