Volume Paging FIle (Z:
Volume size = 2,996 MB
Cluster size = 4 KB
Used space = 785 MB
Free space = 2,210 MB
Percent free space = 73 %
Fragmentation percentage
Volume fragmentation = 0 %
Data fragmentation = 0 %
File fragmentation
Total files = 7
Average file size = 20 KB
Total fragmented files = 0
Total excess fragments = 0
Average fragments per file = 1.00
Paging file fragmentation
Paging/Swap file size = 768 MB
Total fragments = 1
Directory fragmentation
Total directories = 5
Fragmented directories = 0
Excess directory fragments = 0
Master File Table (MFT) fragmentation
Total MFT size = 35 KB
MFT records In Use = 24
Percent MFT in use = 68 %
Total MFT fragments = 2
--------------------------------------------------------------------------------
Fragments File size Most fragmented files
None
Volume 60gb Striped (K:
Volume size = 58,642 MB
Cluster size = 4 KB
Used space = 35,473 MB
Free space = 23,169 MB
Percent free space = 39 %
Fragmentation percentage
Volume fragmentation = 0 %
Data fragmentation = 0 %
File fragmentation
Total files = 10,891
Average file size = 4,329 KB
Total fragmented files = 904
Total excess fragments = 1,290
Average fragments per file = 1.11
Paging file fragmentation
Paging/Swap file size = 768 MB
Total fragments = 1
Directory fragmentation
Total directories = 402
Fragmented directories = 25
Excess directory fragments = 414
Master File Table (MFT) fragmentation
Total MFT size = 17,968 KB
MFT records In Use = 11,307
Percent MFT in use = 62 %
Total MFT fragments = 14
before I go, this is the biggest pointGoNz0 said:sorry mate, this used to be a problem, not any more, and it was back in 512mb days
well, if your fixed pagefile is the same size as the expanded would have been maxed out, it's the same thing as having the benefit of expansionindyjones said:hmmm so from what your saying perris is that where I have 512 meg of ram my fixed pagefile of 1400meg is not right ???.....
indyjones said:hmmm so from what your saying perris is that where I have 512 meg of ram my fixed pagefile of 1400meg is not right ??? Also going back to what someone else said I have two HDDs and windows on one drive and the pagefile on the other I was under the impression this was the best performace situation not both on the same drive .....
Well, I've never touched the PF ever. Also, FYI Windows internal defrag program is a cut down version of diskeeper (i.e. it uses the same core instructions as diskeeper) (from what I've read).perris said:the pagefile will fragment in these situations;
if you adjust the minimum size, or if you change the amount of the memory and the os changes the initial size
ALSO
diskeeper will putt your pagefile on a differant area on your drive, and can fragment the pf also
use the system internals free program to monitor your pagefile extents, and you will see ONCE IT IS CONTIGUOUS it remains contiguous even after expansion, ( once you reboot)
all of this is explained in the paper that's posted in the thread xie sites, you guys should read that
once it's contiguous, it remains contiguous forever on a healthy drive
if expansion is invoked, the expanded extent is removed on reboot, and thre original pagefile HAS to be in the original condition
the issue is that you've mmade the initial minimum too small, and your operating system is expanding the pagefile
that's the point, you must not have a pagefile so small the os wants to expand it, when it does expand, the fragmentation IS ONLY FOR THE EXPNSION EPISODE and you have a pagefile that the initial minimum needs to be increased, which of course will ahve to be defragemnted ONE TIME and then it will always be defragmented
j79zlr said:not again, no it doesn't, the best placement is on a second drive on a seperate controller