The title says it all, or close. I had seen this issue with the first final release, and I see it persist with this beta. My virtual dynamically increasing HD uses +- 10,0 GB according to the XP installed on. The storage on Mac OS X is now around 15 GB. So was an appropriate time to run the compressor and test it for added performance (maybe) in the current beta. The step which takes forever (I couldn't admit to let it continue after 4 hours of playing with my hard-drive) is the final step, the one actually compacting the image on the Mac disk. CPU are overloaded during the process (activity monitor reports constantly 110 to 120% to Parallels), and the progress bar advance slower and slower. If I interrupt it, shutdown the virtual machine and then use the Compact action available from the Configuration Editor (disk subsection), then it finishes in a reasonable time (read: a bit less than 2 hours which is still a bit much, but well okay). During this run Activity Monitor reports from 10 to 30% CPU to Parallels Desktop. It is pretty much as if this last compacting stage when started automatically from within the VM (when it dims the VM screen) was slowed by some CPU over useage while when run with the VM really stopped from within the configuration editor it seems to work as designed, at least as expected. Am I the only one to see this ? When we were in the beta (around beta 4 to 6 if I remember well), I had no such time issue with the compacting process.
I just ran the compressor. I just started it and went to bed. Six hours later, it was all done and freed me about 3GB. Not sure how long it really took.
