![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Performance and Maintainance of Windows Vista A forum for performance and maintenance tasks in Windows Vista. (microsoft.public.windows.vista.performance_maintainance) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
I've got Diskeeper installed now on my Vista Ultimate machine, and notice
that Diskeeper is working in the background on defragmenting some newly-written files... you can see the name of the file it's working on. Question is, since there is plenty of space on my disk, and this file is new, why does it need defragmenting at all? My guess is that the file is perhaps not being defragmented as such, just moved... maybe diskeeper is trying to keep all the files in a single block and doesn't like where the OS put the file in the first place, so is merely moving it. Is there any way that Vista would actually write a new file that is already fragmented (when there is plenty of room to write it as a single block)? Mike |
|
|||
|
In message Mike B
wrote: I've got Diskeeper installed now on my Vista Ultimate machine, and notice that Diskeeper is working in the background on defragmenting some newly-written files... you can see the name of the file it's working on. Question is, since there is plenty of space on my disk, and this file is new, why does it need defragmenting at all? It likely doesn't need defragmenting. My guess is that the file is perhaps not being defragmented as such, just moved... maybe diskeeper is trying to keep all the files in a single block and doesn't like where the OS put the file in the first place, so is merely moving it. This is likely correct, Diskeeper may be "defragmenting directories" (grouping files within a directory together on the drive) Whether this is an ideal configuration depends on your environment and installed software. Is there any way that Vista would actually write a new file that is already fragmented (when there is plenty of room to write it as a single block)? In general, no. |
|
|||
|
Just because there is a block of space large enough to accomodate the file contiguously doesn't guarantee that Vista/XP will put it there. If there are gaps (fragments of free space) in between other files but ahead of the large block of free space, then NTFS may start writing the file there, causing it to be fragmented. If you look at even a clean XP Pro install followed by updates, drivers and Office XP, (no other programs installed) you can see a badly fragmented system depsite the vast amount of free space available. -- Benjamin |