4.0b2: How slow is slow? (only 10% after > 24hrs...)

[XIII]

Hello,

I'm new here... Have been a happy JkDefrag user for quite some time and discovered MyDefrag yesterday. Downloaded 4.0 beta 2 and started the slow profile more than 24 hours ago and it still is only at 10% of the first partition on my drive!

How slow is slow?

Technical details: MyDefrag is defragmenting the first primary partition of my 640GB Samsung HD642JJ SATA2 drive. This is the first partition on the drive, NTFS, 32GB (of which about 50% is actually used and kept in to shape with JkDefrag), running Windows XP (SP3, fully up-to-date).

Is it normal to be this slow, or is there something wrong here? (doing the same on the remaining 600+ GB will take "forever" like this...)

[XIII]

Update: just noticed beta 3. Stopped beta 2 and ran beta 3. This one finished the C: drive within a few minutes...

Update 2: it finished the entire drive rather fast, but a second run with "Fast update" is very slow again!

[HolyMan]

MyDefrag works with scripts. The scripts you used are samples that you can adapt yourself.
Just open the *.myd files in the "C:\Program Files\MyDefrag v4.0b3\Scripts" directory with an editor (like notepad) and adapt them. Use help for further instruction
It looks like slowoptimize put all files on the begin of your disk in a certain order. If your files were shattered all over the disk this will probably mean write to empty space in most cases, which is relatively fast.
Fastoptimize is supposed to be faster, but because there is no space left between categories of files, there will be some swapping to make it happen. And that makes it slower.
Directories are in the front of the disk. A change in 1 would cause a chainreaction of swapping. And that takes time.

[XIII]

Maybe I read it wrong, but I thought "Fast update" was the one to use after a "Slow optimize"?

[CLRS530]

Yeah this was a useless post.
There absolutly is a bug in slow optimize.
It was far to fast also in my run.

EDIT:
After a second look it's maybe ok because it's my windows partition and I ran a slow optimize some days ago and there aren't many changes. But I thought slow optimize still would need a long time.

[HolyMan]

There absolutly is a bug in slow optimize.
It was far to fast also in my run.

Just open the files in notepad and see for yourself. The basic sequence for slowoptimize, fastoptimize and fastupdate is very similar. The differences are in the way files are placed in their sector. For instance:

Slowoptimize:

Code:

  FileSelect
    Directory(yes)
  FileActions
    SortByName(Ascending)
  FileEnd

Fastoptimize

Code:

  FileSelect
    Directory(yes)
  FileActions
    Defragment()
    FastFill()
  FileEnd

Fastupdate

Code:

  FileSelect
    Directory(yes)
  FileActions
    FastFill()
  FileEnd

Obviously, Fastfill() alone will be quicker than Defragment() and Fastfill() together.
Sortbyname() is supposed to be slower than fastfill.
That is because it places the files in the group in a certain order, replacing other files already there.
However my experience is that moving files to an empty diskspace with Sortbyname() is just as quick as Fastfill(), obviously because no other files have to be moved for it.
In fact, in that case Defragment() and Fastfill() together will be a lot slower than Sortbyname() alone, because they require 2 filemoves for fragmented files, where Sortbyname() only requires 1.

[HolyMan]

By the way. After install of 4.0b3 I noticed that some shortcuts in the menu still pointed to 4.0b2 scripts. Those scripts are slightly different from the new ones. Maybe that caused extra problems.

[XIII]

Any indication on "normal" times?

[poutnik]

What time gives you usage of JKDefrag 3.36 with similar operation ?
( -a 3 compared to FastOptimize or -a 7 (names) compared to SlowOptimize (if names) )

[XIII]

I've only run JkDefrag without parameters I'm afraid...

[jeroen]

How slow is slow?

That's impossible to answer. But 10% after 24 hours is slow, yes. For a bit more information see the What speed can I expect? question in the frequently asked questions.

Was the program still doing things, did you see files being moved? It's a beta and it's possible that the program got stuck. Do you have a virus scanner? Try turning it off. Virus scanners check all disk activity, making defragmentation and optimization very slow.

[XIII]

The program was still doing things and a virusscanner (NOD32 v4) was running...

I'll disconnect from the internet, close as many programs as possible, and try again.

[XIII]

Wow: now the entire drive (not just that 32GB partition) is finished within 1 hour! (slow optimize)