FileName("$mft") : SortByName(Ascending) OR Defragment() and FastFill() ?

[andublin]

FileName("$mft")   : SortByName(Ascending) OR  Defragment() and FastFill() ?
I'm wondering if there is any particular benefit to having the MFT sorted by any particular sequence, whether Name, lastAccess, lastChange?
Not for relative placement within the MFT, because it's a relatively small area,
but in terms of Window file operations, Opening, Closing, Changing, getting to the right MFT entry with the smallest underlying number of disk accesses.
I notice both FastOptimize and SlowOptimize use SortByName(Ascending) , why is that?
Any views?

And I have the same question as well in relation to the Directory area!

Many thanks.

[jonib]

FileName("$mft")   : SortByName(Ascending) OR  Defragment() and FastFill() ?

I might be wrong but here goes, I believe the default scripts use SortByName with $MFT not to sort it but to but it in the right place potentially breaking it in fragments if there are files in the way, where as Defragment or FastFill needs a gap big enough for the whole file.

And I have the same question as well in relation to the Directory area!

I think directories do get sorted, but what sorting method is best I can't say.

jonib

[jeroen]

I'm wondering if there is any particular benefit to having the MFT sorted by any particular sequence, whether Name, lastAccess, lastChange?

Jonib is right, the SortByName() action is only there to place the MFT. It does not do any sorting, because there is only 1 file in that zone (the MFT). The other sorting methods would produce the exact same result.

And I have the same question as well in relation to the Directory area!

The directories are really sorted, every directory is a separate entity. Directories are often accessed in alphabetical order, for example when you open a folder with Windows Explorer.