PerfectDisk SMARTPlacement mishap or am I backwards?

kppanic

Limp Gawd
Joined
May 14, 2008
Messages
164
Hello all,

I was defragging my 200GB OS Partition today,
and I noticed something strange;

I thought the fastest part of the drive is the beginning part of a hard drive,
therefore a smart defragger like PerfectDisk should be placing
recently modified files in the "starting" part of the drive,
as in, when viewed graphically, all the "red" blocks that represent
recently modified files should be placed in the beginning
and all the "blue" blocks that represent Rarely modified
should be at the end?

PerfectDisk is doing the exact opposite, moving all the "blues"
to the beginning and all the "red" in the end.

Or am I backwards?

Thanks,
 
Hello all,

I was defragging my 200GB OS Partition today,
and I noticed something strange;

I thought the fastest part of the drive is the beginning part of a hard drive,
therefore a smart defragger like PerfectDisk should be placing
recently modified files in the "starting" part of the drive,
as in, when viewed graphically, all the "red" blocks that represent
recently modified files should be placed in the beginning
and all the "blue" blocks that represent Rarely modified
should be at the end?

PerfectDisk is doing the exact opposite, moving all the "blues"
to the beginning and all the "red" in the end.

Or am I backwards?

Thanks,

First, don't confused most accessed with most modified. I'd want my most accessed files at the front of the disk.

The most modified files go to the back as it's faster for access for them. It's also faster to defragment them again in the future.

If a file that gets modified frequently is put to the front, then whatever gets added to it gets sent to the back. Access times from the front to the back are much slower than access times from one part of the back to another part of the back.

Also, if files are frequently modified, some might grow in size, some might shrink. under this scenario, if a file at the front keeps shrinking, but shrinking not in the same timeframe as the one that's growing, it is very possible for a file at the front that is growing to have one sector at the front, the next at the back, the next at the front (after the file that shrunk had that sector de-allocated...), the next at the back, the next at the front.

That would absolutely kill performance.

So, frequently modified files stay at the back nearest the free space.

It's not perfect, but access times are a real killer, not raw data throughput...
 
If a file that gets modified frequently is put to the front, then whatever gets added to it gets sent to the back.

I think I am thinking the opposite here and confused to hell,

but I would think if a frequently modified file is put in the front,
and it gets modified,
it would try to write the content nearest to it, which still means relatively to the front..?

Why would something get added be place in the back?
 
Why would something get added be place in the back?

To re-quote myself:

So, frequently modified files stay at the back nearest the free space.

Your free space is after all of your files, so the back of your files. If your HD is full, it's the back of the disk.

You want to keep your frequently modified (especial expanding) file near your free space, so when it writes the next part of the file, it's already near the other parts of the file.

Defragmentation has to do also with keeping files relatively close together.

Heavily-modified files probably rely more on pure IOs than raw throughput. If you need high IOs, you don't want the head moving all over the place to access them.

random read all over the place in a file at the back of the disk but defragmented is faster than random access of a file that's all over the place, even if part of it's at the very front.
 
Cause after you defrag the only empty space left is at the back of all the defraged data. The file would then be slip in 2 wide apart. One part at the front one part at the back.

Place the often modified file at the back and the data might still be splited but the 2 parts will be closer to each other near the back for faster access.
 
Your free space is after all of your files, so the back of your files. If your HD is full, it's the back of the disk.

You want to keep your frequently modified (especial expanding) file near your free space, so when it writes the next part of the file, it's already near the other parts of the file.

Defragmentation has to do also with keeping files relatively close together.

Heavily-modified files probably rely more on pure IOs than raw throughput. If you need high IOs, you don't want the head moving all over the place to access them.

random read all over the place in a file at the back of the disk but defragmented is faster than random access of a file that's all over the place, even if part of it's at the very front.

But that's what I am saying, I see big chunk of BLUE blocks in the beginning of the disk (which I believe is the fastest part of the drive), and big chunk of FREE SPACE, and then a big chunk of RED blocks (frequently modified files)

Wouldn't it be better to have RED block in the beginning for:
1. faster access times
2. there is an abundant amount of freespace right after the red blocks, so why don't they get written there?

Even if I wanted high I/O throughput, all the RED blocks are in the beginning, rather than at the end, so the head won't move much. no?
 
Alright, look at it this way. Frequently ACCESSED files are typically programs and OS, which tend to be larger files and benefit most from data transfer speed.

Frequently MODIFIED files are typically log files or user data files, and tend to be much smaller in size which won't benefit as much from data transfer speed.
 
Wouldn't it be better to have RED block in the beginning for:
1. faster access times

Even if I wanted high I/O throughput, all the RED blocks are in the beginning, rather than at the end, so the head won't move much. no?

You are conveniently ignoring my previous explanation, or just didn't read it.

Please re-read what I've said regarding freq mod files...

It's the very reason why defrag software do not put freq mod files at the front.
 
Back
Top