Sorting options - newer from created and modified

[poutnik]

Hello,

I thing JKD could add a new sorting option - newer(created,modified).

As many of you know,
created timestamp  is when a file is created as an item in local filesystem.
modified timestamp is when file *content* is created/last modified.

AS far as I have realized by watching,
Perfectdisk file ordering seems to use newer(created,modified) criterium.
i.e. put old files by BOTH created and modified criteria to beginning of the disk.
Files either created ( copied ) either modified ( saved ) recently are last.

Both timestamps can be significantly different in both time directions.
DOC can have been
created 2005
modified 2008
and should be treated as new.
 
Copied/extracted file can have been
created 2008
modified 2005
and should be treated as new too.

IMHO it is a good idea to put
NEWLY CREATED files with an OLD CONTENT and
OLD FILES created long time ago, but MODIFIED RECENTLY
on the same side of the disk.

In case one use sorting option 10 last change last
and than copy to disk some old files,
in next sorting defrag all files will be reordered,
but would not if newer(created,modified) is used.

Poutnik

[jeroen]

I thing JKD could add a new sorting option - newer(created,modified).

Wauw, that is a new one for me! I thought that the modified date would never be older than the creation date, but a quick check shows me that files extracted from an archive can indeed have an older modified date than creation date. I'll put it on the list for v4 of JkDefrag. Thanks for sharing your idea, I appreciate it!

[Lundholm]

Optimizing a disk is like a game of chess. What happened to the files in the past is unimportant. The only thing that matters is how those files will be used in the future. 

[poutnik]

What happened to the files in the past is unimportant. The only thing that matters is how those files will be used in the future. 

Well, future prediction. based on past experience, is one of very few methods we have, spoken very generally. 

[Lundholm]

Well, future prediction. based on past experience, is one of very few methods we have, spoken very generally. 

Exactly. Experience is usage count or last access time. Not creation or modification time. How many times did I say this?

[poutnik]

You are both right and wrong.
What piece of experience to use depends on what is the goal.

A wise man could say Mine goal is best for me,
but hardly Mine goal is best, because it is mine.

[Lundholm]

One wise man would say: "Use some scientific criteria to determine the best optimization."

Another wise man would say: "Who cares?"

[poutnik]

And some others claim the word BEST as a taboo in some web forums  :-)

The best for one need not to be the best for others.

I have my own personal definition of "THE BEST":
"The best solution is the one that starts the smallest flame war, claiming it is the best."

Edit: I miss my one comment :

Access optimization
is better in later performance, especially read one ( write one will be worse, but less frequent),
is worse in defrag optimization cost, speed and fragmentation rate.

Creation/Modified optimization is the opposite.
All has its sense and value.

BTW, nice to meet such a discuss partner.

[trev]

I thing JKD could add a new sorting option - newer(created,modified).

I totally agree, great suggestion!  thanks for sharing it.

Jeroen, good to hear that you will consider it for jk 4.0, i really hope you have the time and work out how to do it!

[jeroen]

Jeroen, good to hear that you will consider it for jk 4.0, i really hope you have the time and work out how to do it!

It's already there and working in my development version.