I won't be worried about the speed of a Garbage collector. Rather focus on its efficiency. Actual work done per cycle per byte. Collectors can run on a separat

I won't be worried about the speed of a Garbage collector. Rather focus on its efficiency. Actual work done per cycle per byte. Collectors can run on a separate core and show double the speed, but then you have to halve the total number of working processes on your machine. Thus total work done per cycle remains the same. Or it can just be lazy and run collection half the time, and thus show half processor use. But RAM use will then double for the same work load. At the end actual work done per byte of memory remains the same. So focus on efficiency. The user can utilize the spare cores and RAMs for paralyzing their work, or for more work.