G
Guest
==============
Better place for pagefile, or is there any sense to keep it fragmented?
A HD is in million times slower than electronics, and CPU often stops and
waits information form HD. pagefile.sys is very frequently used file, and its
location is important for PC productivity.
In typical 160 Gb EIDE HD: Read Seek Time (average): 8.9 ms; Latency
(seeking on the same Cylinder): 4.2 ms; Full Stroke Seek (through all HD):
21.0 ms; Track-To-Track Seek: 2.0 ms; Transfer Rate: 750 Mbites/s ==> /8 ==>
93.75 Mbytes/s
By the way, it's vendors cheating and their 160 Gb HD really has:
160,000,000,000 Bytes \1024 ==> 156,250,000 KB \1024 ==> 152,587.89 MB \1024
==> 149.0 GB. The same situation is with DVD 4.7 Gb ==> 4,383 GBytes.
OK, the best place for pagefile is the second physical storage, when one can
read and the second can write simultaneously. From this point, USB is the
best choice, if your system supports this. Next, the beginning (the first
partition) of the second fast HD, where speed may be up to 2.5 times higher
than at the HD end, thanks to bigger outer diameter - more information are
treated for one disk circle_Cylinder.
But many PC has only one HD.
Think a little bit before using a utility for pagefile defragmentation.
Pagefile may be collected in one fragment, but placed at the disk_partition
end. Thus, each time to access pagefile; computer will waste "Full Stroke
Seek" time.
It’s clear than pagefile should be located in position(s) provided
“average-minimum†access time. More frequently used files are located in
/Windows and /Program_Files directories.
I made *.bat file and it performs the follow trick.
Set %SystemDrive%\pagefile.sys == 0, and reboot, remove
%SystemDrive%\pagefile.sys which become not system file after rebooting.
Create temporary directories and file(s) (empty file system images) with
names to locate them in places I want.
Next, sort (really on magnetic disk, not as you see on the screen) all
%SystemDrive%\Directories\Files in alphabetical order, using OO.Defrag or
Ultimate Defrag programs (from *.bat file, only OO.Defrag works).
These programs can also optimize files layout according to layout.ini, and
exclude some directories or files from sorting. At first sorting I place
%SystemDrive%\zz_Archive far from system files, and exclude it from further
sorting until big size changing.
After sorting, my temporary files are located on the disk in position(s)
(not exactly in clusters, but in relative sizes and in alphabetical orders)
I’ve chosen.
Windows starts to place pagefile.sys from filling the biggest continued free
space available. To avoid placing pagefile.sys at the disk end, after files
sorting, all (free space) %SystemDrive% is filled up by additional file_image
(vmware-vdiskmanager.exe creates empty images (quickly) from 100 MB to 39
GB).
Next, remove (some) temporary file(s) with total size a little bit bigger
than pagefile.sys, and set %SystemDrive%\pagefile.sys on the gap occupied
before by temporary file (or pagefile.sys fragments on file gaps). Remove all
rest temporary directories\files.
I such a way, pagefile.sys may be set (located) in any place(s), with any
fragments and fragments sizes.
I name temporary directories to place them (pagefile fragments) on the
middle of the sizes of my %ProgramFiles% and before %Windir%\system32\.
You can perform all operations manually, but files deleting and pagefile
setting should be done without a time gap. Otherwise, changed and new service
files may be placed on restricted space, and pagefile will be heavily
fragmented.
*.bat file does all quickly and automatically; OO.Defrag consumes very
little PC resource and sorts files in ~10-20 minutes. I sort files and reset
free spaces inside system directories weekly (of course, files relocating is
the best defragmentation), and relocate pagefile only after big size changing
in the system directories.
Directories\Files alignment in alphabetical order decreases files searching
and reading times. 2 pagefile fragments are located among more frequently
used files. In my naive, I think that Windows is “clever†and magnetic head
rushes from the current location to closest pagefile fragment.
“Mathematically†it should be the "average-minimum" access time from all
files. Thus, together with regular file sorting, reserving free spaces inside
system directories for changed and new service files, should provide the best
available HD productivity.
Is there any sense in placing 3 or 4 pagefile fragments? What are the
really more frequently used files, and where is the best pagefile location(s)?
Directory names are also files with information about files. I've red that
it’s better to keep directory_name_files near MFT, which decrease file access
time. Are there any differences: CPU send request ==> MFT ==> close to
directory_name_file ==> far to file; or MFT ==> far to directory_name_file
==> close to file. Total way is the same. What are real differences?
May be somebody know how to move or create a file to place it from the
certain cluster exactly?
I’ll appreciate any information that helps to “squeeze†all possible
productivity from “turtle†HD.
Best, Alex
=============
P.S. Explanations from my *.bat file
echo ==== This *.bat file creates temporary files in directories:
echo DocFree=%Documents%\AA_free
echo ProgFree=%Programs%\LZ_pagefile
echo WinFree=%Windows%\SX_pagefile
echo DiskFree=%SystemDrive%\zfree_before_archives
echo.
echo ==== File sizes and places (names) for each directory are set above
manually, and should be corrected for each PC, or after big data size
changing on the %SystemDrive%\. I name temporary directories to place them on
the middle of the sizes of my %ProgramFiles% and before %Windir%\system32\.
echo.
echo ==== Next, sort (really on magnetic disk, not as you see on the screen)
all %SystemDrive%\Directories\Files in alphabetical order; add additional
file_image to fill up all free %SystemDrive%\ place; remove some temporary
files and set %SystemDrive%\pagefile.sys of %pagefile_size%MB (or its
fragments) on the gap(s) occupied before by temporary file(s). Windows starts
to place pagefile.sys from filling the biggest continued free space available.
echo.
echo ==== Free places of sys_free==%sys_free%MB each for system files,
created in the future OS operation, may be additionally reserved on the space
of %DocFree% and parts of the mentioned above directories. Otherwise, new
system files will be placed at the disk end, decreasing PC productivity.
echo.
echo ==== Free place of disk_free==%disk_free%MB for future using, may be
reserved on %SystemDrive%\ after system directories (the last is %Tmp%), but
before archive directory %SystemDrive%\zz_Archive, on the space of
%DiskFree%\
rem On disk directories and files are sorted by absolute names (file \a.img
is before dir \a.z\) accordingly with:
rem On disk: ! # $ % & ' ( ) + , - . 0 1 10 100 11 111 2 200 22 9 99
999 ; = @ a ce f z [ ] ^ _ ` { } ~ а ÑÑ€ Ñ â„–
rem TotalComander: ! # $ % & ' ( ) + , - . 0 1 2 9 10 11 22 99 100 111 200
999 ; = @ [ ] ^ _ ` a ce f z { } ~ â„– а ÑÑ€ Ñ
rem mkdir run with: ! # $ ( + , - . 0 1 2 9 10 11 22 99 100 111 200
999 ; = @ [ ] ^ _ ` a ce f z { } ~ â„– а ÑÑ€ Ñ
rem mkdir corectly: ! # $ ( + - . 0 1 2 9 10 11 22 99 100 111 200
999 @ [ ] _ ` a ce f z { } ~
rem does not used: * ? / " | \ > < .a a. not, but a.z is OK.
Better place for pagefile, or is there any sense to keep it fragmented?
A HD is in million times slower than electronics, and CPU often stops and
waits information form HD. pagefile.sys is very frequently used file, and its
location is important for PC productivity.
In typical 160 Gb EIDE HD: Read Seek Time (average): 8.9 ms; Latency
(seeking on the same Cylinder): 4.2 ms; Full Stroke Seek (through all HD):
21.0 ms; Track-To-Track Seek: 2.0 ms; Transfer Rate: 750 Mbites/s ==> /8 ==>
93.75 Mbytes/s
By the way, it's vendors cheating and their 160 Gb HD really has:
160,000,000,000 Bytes \1024 ==> 156,250,000 KB \1024 ==> 152,587.89 MB \1024
==> 149.0 GB. The same situation is with DVD 4.7 Gb ==> 4,383 GBytes.
OK, the best place for pagefile is the second physical storage, when one can
read and the second can write simultaneously. From this point, USB is the
best choice, if your system supports this. Next, the beginning (the first
partition) of the second fast HD, where speed may be up to 2.5 times higher
than at the HD end, thanks to bigger outer diameter - more information are
treated for one disk circle_Cylinder.
But many PC has only one HD.
Think a little bit before using a utility for pagefile defragmentation.
Pagefile may be collected in one fragment, but placed at the disk_partition
end. Thus, each time to access pagefile; computer will waste "Full Stroke
Seek" time.
It’s clear than pagefile should be located in position(s) provided
“average-minimum†access time. More frequently used files are located in
/Windows and /Program_Files directories.
I made *.bat file and it performs the follow trick.
Set %SystemDrive%\pagefile.sys == 0, and reboot, remove
%SystemDrive%\pagefile.sys which become not system file after rebooting.
Create temporary directories and file(s) (empty file system images) with
names to locate them in places I want.
Next, sort (really on magnetic disk, not as you see on the screen) all
%SystemDrive%\Directories\Files in alphabetical order, using OO.Defrag or
Ultimate Defrag programs (from *.bat file, only OO.Defrag works).
These programs can also optimize files layout according to layout.ini, and
exclude some directories or files from sorting. At first sorting I place
%SystemDrive%\zz_Archive far from system files, and exclude it from further
sorting until big size changing.
After sorting, my temporary files are located on the disk in position(s)
(not exactly in clusters, but in relative sizes and in alphabetical orders)
I’ve chosen.
Windows starts to place pagefile.sys from filling the biggest continued free
space available. To avoid placing pagefile.sys at the disk end, after files
sorting, all (free space) %SystemDrive% is filled up by additional file_image
(vmware-vdiskmanager.exe creates empty images (quickly) from 100 MB to 39
GB).
Next, remove (some) temporary file(s) with total size a little bit bigger
than pagefile.sys, and set %SystemDrive%\pagefile.sys on the gap occupied
before by temporary file (or pagefile.sys fragments on file gaps). Remove all
rest temporary directories\files.
I such a way, pagefile.sys may be set (located) in any place(s), with any
fragments and fragments sizes.
I name temporary directories to place them (pagefile fragments) on the
middle of the sizes of my %ProgramFiles% and before %Windir%\system32\.
You can perform all operations manually, but files deleting and pagefile
setting should be done without a time gap. Otherwise, changed and new service
files may be placed on restricted space, and pagefile will be heavily
fragmented.
*.bat file does all quickly and automatically; OO.Defrag consumes very
little PC resource and sorts files in ~10-20 minutes. I sort files and reset
free spaces inside system directories weekly (of course, files relocating is
the best defragmentation), and relocate pagefile only after big size changing
in the system directories.
Directories\Files alignment in alphabetical order decreases files searching
and reading times. 2 pagefile fragments are located among more frequently
used files. In my naive, I think that Windows is “clever†and magnetic head
rushes from the current location to closest pagefile fragment.
“Mathematically†it should be the "average-minimum" access time from all
files. Thus, together with regular file sorting, reserving free spaces inside
system directories for changed and new service files, should provide the best
available HD productivity.
Is there any sense in placing 3 or 4 pagefile fragments? What are the
really more frequently used files, and where is the best pagefile location(s)?
Directory names are also files with information about files. I've red that
it’s better to keep directory_name_files near MFT, which decrease file access
time. Are there any differences: CPU send request ==> MFT ==> close to
directory_name_file ==> far to file; or MFT ==> far to directory_name_file
==> close to file. Total way is the same. What are real differences?
May be somebody know how to move or create a file to place it from the
certain cluster exactly?
I’ll appreciate any information that helps to “squeeze†all possible
productivity from “turtle†HD.
Best, Alex
=============
P.S. Explanations from my *.bat file
echo ==== This *.bat file creates temporary files in directories:
echo DocFree=%Documents%\AA_free
echo ProgFree=%Programs%\LZ_pagefile
echo WinFree=%Windows%\SX_pagefile
echo DiskFree=%SystemDrive%\zfree_before_archives
echo.
echo ==== File sizes and places (names) for each directory are set above
manually, and should be corrected for each PC, or after big data size
changing on the %SystemDrive%\. I name temporary directories to place them on
the middle of the sizes of my %ProgramFiles% and before %Windir%\system32\.
echo.
echo ==== Next, sort (really on magnetic disk, not as you see on the screen)
all %SystemDrive%\Directories\Files in alphabetical order; add additional
file_image to fill up all free %SystemDrive%\ place; remove some temporary
files and set %SystemDrive%\pagefile.sys of %pagefile_size%MB (or its
fragments) on the gap(s) occupied before by temporary file(s). Windows starts
to place pagefile.sys from filling the biggest continued free space available.
echo.
echo ==== Free places of sys_free==%sys_free%MB each for system files,
created in the future OS operation, may be additionally reserved on the space
of %DocFree% and parts of the mentioned above directories. Otherwise, new
system files will be placed at the disk end, decreasing PC productivity.
echo.
echo ==== Free place of disk_free==%disk_free%MB for future using, may be
reserved on %SystemDrive%\ after system directories (the last is %Tmp%), but
before archive directory %SystemDrive%\zz_Archive, on the space of
%DiskFree%\
rem On disk directories and files are sorted by absolute names (file \a.img
is before dir \a.z\) accordingly with:
rem On disk: ! # $ % & ' ( ) + , - . 0 1 10 100 11 111 2 200 22 9 99
999 ; = @ a ce f z [ ] ^ _ ` { } ~ а ÑÑ€ Ñ â„–
rem TotalComander: ! # $ % & ' ( ) + , - . 0 1 2 9 10 11 22 99 100 111 200
999 ; = @ [ ] ^ _ ` a ce f z { } ~ â„– а ÑÑ€ Ñ
rem mkdir run with: ! # $ ( + , - . 0 1 2 9 10 11 22 99 100 111 200
999 ; = @ [ ] ^ _ ` a ce f z { } ~ â„– а ÑÑ€ Ñ
rem mkdir corectly: ! # $ ( + - . 0 1 2 9 10 11 22 99 100 111 200
999 @ [ ] _ ` a ce f z { } ~
rem does not used: * ? / " | \ > < .a a. not, but a.z is OK.