• 0

Definitive Best Defragmenter 2008


Definitive Best Defragmenter  

866 members have voted

  1. 1. Your choice?

    • Auslogics
      54
    • DirMS/Buzzsaw
      1
    • Diskeeper
      184
    • JKDefrag
      101
    • Norton Speed Disk
      5
    • O&O Defrag
      119
    • PageDefrag
      1
    • PerfectDisk
      224
    • Vopt
      5
    • Windows Defrag
      97
    • Other (please specify below)
      75


Question

Recommended Posts

  • 0

Diskeeper for me. All other defragmenters have below par intelligent, automatic background defrgmentation. PerfectDisk comes close, but it isn't efficient in the sense, it uses too much resources over too little time, thus making performance dips quite obvious. With Diskeeper, you won't notice a preformance drop while a defrag is going on, even on very low end PCs. (I've been running Diskeeper for years on my old 450 Mhz box quite comfortably)

Sure, if you do a manual run, you may find PerfectDisk / O&O / UltimateDefrag to be better, but Diskeeper isn't designed to be run manually.

All those benchmarks that are available at present only tests the defragmenters for a single or atmost two sessions or runs. Those tests only show which defragmenter works the best on manual defrags.

Automatic, background defragmentation tests should be conducted over a period of time, like a week or a month; only then can we know which automatic defragmenter is the most efficient. Note that the keyword here is efficient - meaning delivering maximum performance while using the least amount of resources.

Although, fragmentation is highly overrated these days. With large harddrives becoming cheaper and large media files occupying the maximum space, fragmentation isn't much of a problem once your system is well setup. Again, this is highly subject to your enviromnent and your requirements. Database servers might benefit from Diskeeper w.r.t the performance aspect, but home users might find Diskeeper to be overpriced for their general needs.

Personally, I use UltimateDefrag immediately after a fresh format+install. I manually edit the layout.ini to add ntldr, boot.ini and ntdetect.com at the top of the list. (Why doesn't windows add it in the first place?!) Then I go on about adding files that I don't use frequently to the bottom of the drive (driver.cab, sp2.cab, help files, dllcache, and so on), while I move programs that autostart with windows to the top of the drive. Sometimes, I take the assistance of bootvis to figure out the program loading sequence.

Once the manual drive layout optimization is done UltimateDefrag finishes all tasks, I quit it for good and enable Diskeeper. And that's the last time I'll be opening a defragmenter again, untill the next format cycle comes along :)

My personal advice to all readers: Please don't go blindly by the results of this poll. First, asses your situation and decide whether you would *really* benefit from a dedicated third-party defragmenter. Vista users have their work cut out thanks to the builtin automatic defragmenter, but first asses whether it's working well for *you*. Check your fragmentation levels. Are they low on an average or tend to shoot up every time you install something? Do the drives you use frequently have more than sufficient free space? (If so, fragmentation won't be a problem for you.) Fragmentation of audio/video files isn't a big deal since they're always read (played) at a constant speed. 3 or 4 fragments of a 700 MB movie file wont affect your playback experience. Unless of course, you have some other files, like programs installed in the same partition. Then again, it's never a good idea to keep your programs and media on the same partition, for the above and many other reasons. If program loading time is your main concern, then invest in a good flash drive and make use of ReadyBoost. (eBoostr, for Windows XP users.) If low startup time is what you seek, then disable unnecessary startup programs/services and make use of the Sleep / Hibernate features.

Defragmenters can only take you a certain distance in the journey to optimizing your computer.

Don't just jump to conclusions based on some xyz benchmark or personal opinions. Decide for yourself what would suit your scenario the best. On that note, I'd like to say that there is no such thing as a "Definitive Best Defragmenter", just as there is no "Definitive Best Car".

Edited by [deXter]
  • 0

Normally I would choose PerfectDisk but I chose "Other" this year. I'll explain, even though it won't quite make sense...

PerfectDisk from a safety and reliability standpoint has been the best defragger I've ever used, bar-none. Everything I do with it is a cake-walk and the interface is great. BUT, I don't notice performance gains that are that significant.

People tend to look for that defragger that makes things feel faster. That's where my "Other" choice comes in: Ultimate Defrag from DiskTrix

Now, let me be the first to say that I didn't go through all the normal BS with making an image, running PD, then measuring performance, reimaging, running UD, measuring performance, etc. So basically people who are looking for that proof can just stop reading because I have no real benchmarks to measure anything. I'm being honest here...

BUT, from a performance standpoint, I can feel the system respond faster. Things open quicker, WoW loads much faster, programs open quicker. With PD I don't feel like it's any quicker, but with UD I do notice it, and that's what attracts me to the app. It's small, very very fast and defrags and gives me a nice performance boost.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      599
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      77
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!