Proactive compaction for the kernel

How much of this effect is from proactive operations vs arranging for more CPU to be deployed on the problem? For example, if you controlled for the CPU utilization for compaction being identical between proactive vs direct would the Java heap test still take 27 minutes in the direct case? Basically how to determine if the result is an argument to do proactive compaction vs more aggressive direct compaction?