Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Was looking into DiskTrix Ultimate Defrag.
What? What do you even mean? It's arguably the best? It's probably the best, arguably? It's the "best" arguably, probably? It's probably arguably the "best"? Why is best in quotes? Why is your post so full of weasel words?For a commercial product, the "best" would probably be Perfect Disk 2008, arguably
Problem is, that's not what "arguably" means.I meant I would argue that it's the best, most definitely.![]()
mikeblas ---
Perhaps you should use a dictionary. Joe Average used the word in a correct manner.
While syntactically correct, "arguably probably the best" is nonsense semantically.Perhaps you should use a dictionary. Joe Average used the word in a correct manner.
Do you have specific reasons for that opinion? Will you share them with us?I do not believe they did the test right.
Do you have specific reasons for that opinion? Will you share them with us?
And what is it that you've heard?No evidence, just that the results do not jive with what I've heard.
The proper way to use Perfectdisk is to do an offline defrag., reboot and let it run, then do a smartplace defrag. Did they do that?
Diskeeper 2008
Inexpensive, effective, and no overhead.
I haven´t tried the other apps mentioned here, but I am extremely happy with PerfectDisk 8.0 (there might be a never version out). The performance improvements are easily noticable. In my current setup I´ve set it to auto defrag system files at bootup. This works great and has improved responsiveness and smoothness of operation a fair bit. Comparing it to winXPs own defragger, I´d say it about 800 times better in every respect (thats a lose number and should not be taken too seriously..might actually be 754).
and worse than JKDefrag which is free.
a little off topic, but does anyone know if its necessary to even defrag SSD's?
My initial instinct was that it's a negligible impact, but I did some reading while writing this response, and now I don't know what to expect from performance tests on this issue.Really? Is one two-sector transfer really not at all slower than two one-sector transfers? Or is it that it's only slower by a negligible amount?
What is it that you're measuring? The time for the CF card to respond to the request at its electrical interface, or the time for the application to see the response through the drivers to the CF card?The best data I can find (if you've got better or more modern spec sheets, please let me know!) says that reading a single page at random from a particular flash chip takes about 10 microseconds, while reading the next page takes about 50 nanoseconds. That means, to read the eight pages for a filesystem block takes about 10.35 microseconds, so if one's filesystem were completely fragmented (no reads are sequential) one would expect to see 790 MB/s or so from this chip.
Make things worse for longeivty? Sure, I guess; if that's a real cost in the long run. But even if the data is stored on non-consecutive pages in the device, I'm thinking more about the logical ordering. That's what defragmenting is meant to fix, and spinning hard drives can remap, too.So trying to optimize the order in which the device is accessed could actually make things worse.
That spec sheet is for a single flash chip; its specs are for the electrical level only.What is it that you're measuring? The time for the CF card to respond to the request at its electrical interface, or the time for the application to see the response through the drivers to the CF card?
No, I was thinking of latency. If the blocks are non-sequential on the actual media behind the mapping layer, it will hurt performance just as much as if they were non-sequential from the OS perspective---but there's less you can do to correct that.Make things worse for longeivty?
That's true, but they do it less often, and there remapped sectors are an indicator of a failing disk rather than an everyday happening.But even if the data is stored on non-consecutive pages in the device, I'm thinking more about the logical ordering. That's what defragmenting is meant to fix, and spinning hard drives can remap, too.
Agreed. Any measurements I make would be affected by that translation layer, but the devices I have are new enough that they probably still have large contiguous blocks. That would allow for reasonable intra- and inter-block measurements. I'd do read-only tests to try to prevent the sectors from being remapped as I tested.If the device has, under the covers, re-mapped the clusters to different physical locations (for wear leveling, for example), then that's fine. You're still doing one single request for three clusters in a row, and letting the implementation of the medium sort it out. There's probably some overhead in that, but it seems you're paying the overhead anyway because all requests, even continuous ones, are going to have to go through that same mapping layer.
True enough.Meanwhile, the fundamental problem with defragmenters exists, anyway. They make files continuous based on the presumed access pattern, which is always sequential and continuous. In real life, most files are read in small blocks, inconsistently. It turns out that fragmented and interleaved file storage might be faster because of that.