Something's probably wrong with your program that checks disk reads and disk writes. Here's a test you can try:
Set DriveSpace 6 to maximum threads, for example 8 threads on a 4 core (2 without hyper-threading) CPU, on an already compressed disk. Notice how quickly DriveSpace 6 works, compressing only the new additional files available/unlocked since your last run.
Normally this would crush performance with LZX compression because it is very CPU intensive; on a system with 4 cores (including HT), DriveSpace 6 defaults to only 2 CPU cores and still achieves about 100% CPU utilization with LZX compression. So definitely don't do this when you're compressing your disk for the first time, but it can be shown to prove that DriveSpace 6 isn't re-compressing anything.
I've already shared that compact /c /s /i /f /a /exe:lzx * is substantially worse than DriveSpace 6 here:http://forum.tabletpcreview.com/threads ... ion.67306/compact.exe lost an additional 17 GB, corresponding to 13% worse compression that DriveSpace 6, for reasons unknown as previously discussed on this thread.
In addition to being single-threaded, which is going to at least halve performance compared to DriveSpace 6, and worse on CPUs with more than 2 real cores; it loses significant space on a disk already compressed with DriveSpace 6, or it will fail to free up that additional space if it was not previously compressed with DriveSpace 6. Again, this could be due to any number of the optimizations below:http://zipmagic.co/drive-space.html
From wasting gigabytes of space
, to being very slow (single threaded)
, to disabling automatic folder NTFS (LZNT1) compression
, it doesn't make sense by your own stated priorities to keep using compact.exe over DriveSpace 6.
It can be hard for customers to hear that their research is wrong, but again, I remind you that:
1) Yes, DriveSpace 6 does set folders to use NTFS (LZNT1) compression, even when you are compressing your disk with the new Windows 10 compression methods.
2) No, DriveSpace 6 does NOT recompress and re-write to disk all pre-compressed data, when all that data was compressed using the exact same previous compression algorithm as before before (proof as described above on this thread).
I'll also repeat what I posted earlier:
3) If you need to absolutely maximize your compression, DoubleSpace 2 substantially outperforms DriveSpace 6, even when DriveSpace 6 is using the new Windows 10 compression methods, as highlighted here:http://forum.tabletpcreview.com/threads ... ics.67414/
Hope that helps.