For skeptics who are versed in disk drives and NTFSThe program determines the speed approximately, the fight against fragmentation is also about. If you start the scan several times, the results will be slightly different. Nevertheless, in practice, accuracy is quite enough! And I strongly doubt that increasing the accuracy will give a tangible effect. I'd rather give up the power of the new version, which will have direct reading of sectors without pre-writing, blocking sectors with ntfs proprietary tools, as well as completely blocking the broken sectors. But the current version copes with its duties. Caching files when writing / reading is taken into account in the program. I'm aware of a heap of speed measurement errors by the current method:
Working with fragmentation goes about because:
The error in measuring speed, causes blockage of excess count of good sectors. But this is not critical, especially given that there is simply no other option for speeding up the disk. Once again, the current accuracy is enough, it effectively speeds up slow disks . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
Gratitude to the heroes, who actively participated in the testing of the program.
Add to group
To monitor changes in the program and to help it advance.
|