![]() ![]() I'd imagine that is probably true for Raxco and O&O as well. The overwhelming majority of Diskeeper Corp business is working with IT Professionals at other companies/organizations, not selling to users. The only caveat is that the usage of the computer in the experiment should be fairly equal for both of those weeks. And, remember the amount of free space fragments is irrelevant unless it translates to file fragmentation and therefore performance loss. Or, if you have the defragmenter turned on (to do background/scheduled defrags), note how many less file fragments it has to remove in the week that IntelliWrite is active. Use any defrag tool to measure the number of file fragments that accumulate in each week. with Diskeeper 2010 30-day trialware) is to clean up most of the pre-existing fragmentation on your PC. One quick real-world test anyone can run (i.e. Also note that Diskeeper will consolidate free spaces, to the degree it is valuable.Īn isolated case on an inactive and unused volume is not much of a real-world test. Therefore free space fragmentation is relatively moot, unless it gets severe. IntelliWrite addresses that at the "source". It's only an issue to the degree that it precipitates NTFS file write fragmentation. The I-FAAST feature (first released in 2005 - Diskeeper 10.0) places key files in the faster regions of an HDD(s).įree Space fragmentation is not, in and of itself an issue. You can also visit OCZforums where users and, kudos to them, OCZ staff actually did tests: Most SSDs do benefit from free space consolidation. They are rubber-meets-the road info that gets past theories, inferences and opinions. Whatever "resources" are used, are more than returned performance-wise (a net gain). PCMark), you'll see that scores are higher when InvisiTasking and IntelliWrite are active. If you run performance tests and/or benchmarks (e.g. ![]() To infer that it's activity empirically impacts system performance would be misleading. I/O Other bytes is simply a statistic that may be noteworthy, nothing more. Poorly timed defrag-related Disk I/O can and will impact the computer - what InvisiTasking is designed to avoid. ![]() RDP), but for Diskeeper I/O Other bytes largely represents InvisiTasking, using idle resources, determining whether Diskeeper is allowed to do any actual DISK reads or writes. Yes, I/O Other bytes can represent impact (e.g. The fact that I/O Other bytes accumulate for the DKservice.exe process is irrelevant it does not impact the system. The benefits of IntelliWrite far outweigh the requirements. IntelliWrite's use of resources, in doing a better job of preventing fragmentation than the native NTFS functionality, is negligible. I'll be more careful with my wording in future.Īs for resource usage, InvisiTasking and IntelliWrite DO NOT impact the system. It is unfortunate that the article has been misinterpreted by readers and competitors. The purpose was to distinguish, for users, between file placement algorithms designed to slow file re-fragmentation and proactive technology that prevents file fragmentation. Note that I did not name anyone (nor do we ever). The purpose of the Diskeeper Blog post, of which I am the author, was not to criticize anyone or, LOL, incite some "blog war". I'd like to make a few clarifications, and am dumping multiple answers (from questions/comments in this thread) into one post. So all I will say there is potential for intelliwrite to improve on NTFS's file placement algorithms.Ĭlick to expand.As a vendor (Diskeeper Corporation), I certainly appreciate everyone taking your time to discuss these products. Some of the linux file systems are better by grouping together related files (could be by folder, age) and leaving some but large chunks of freespace so that changes to existing files and new related files can be located nearby. Relative to this test, maybe Intelliwrite appears to have bad free space fragmentation, but if it does not affect performance and does not get any worse with use and time compared to NTFS (which we know does gradually get worse and worse) then its actually superior to the vanilla NTFS drivers.Īll I will directly comment on intelliwrite is that there are many Linux filesystems with superior fragmentation and performance loss resistance to NTFS, so there is room for improvement in the NTFS allocation algorithms. That is after 1 day, 1 week, 1 month of real world use how do different defragmentation tools compare in terms of fragment elimination, refragmentation and efficency of defrag and more importantly measurements of performance losses. Like many tests they are not very helpful without any measurements taken over time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |