EDIT - See my Nov06 addition to this thread.
Now that I am regularly using gbpvr, I've notice how frag'd my partition is becoming. Some of the suggestions in the forum focus on independent partitions, etc. but I'm trying an alternate route by using contig.exe (http://www.sysinternals.com) to defrag JUST the recorded file and not the whole partition. By putting it in PostProcessing.bat (mypath\contig.exe -v %1 >>postprocessing.log) I find that the partition is staying relatively defrag'd and well-behaved -- since my recorded programs tend to cluster around similar sizes I notice that the partition starts to show fairly regular allocation patterns. My questions are
a) Anyone have any +/- experience with this approach -- what might I be missing?
b) I currently invoke contig AFTER running comskip... is reason to think it would make comskip performance any better/worse if I schedule contig to run BEFORE?
Now that I am regularly using gbpvr, I've notice how frag'd my partition is becoming. Some of the suggestions in the forum focus on independent partitions, etc. but I'm trying an alternate route by using contig.exe (http://www.sysinternals.com) to defrag JUST the recorded file and not the whole partition. By putting it in PostProcessing.bat (mypath\contig.exe -v %1 >>postprocessing.log) I find that the partition is staying relatively defrag'd and well-behaved -- since my recorded programs tend to cluster around similar sizes I notice that the partition starts to show fairly regular allocation patterns. My questions are
a) Anyone have any +/- experience with this approach -- what might I be missing?
b) I currently invoke contig AFTER running comskip... is reason to think it would make comskip performance any better/worse if I schedule contig to run BEFORE?