- Joined
- 24 Jan 2002
- Messages
- 12,388
ok, according to this white paper, (cudos to allan for showing this to me),microsoft says, that fragmentation can occur in your page file, if the page file is constantly resizing....now, for this white paper, I will again adjust my advice on the page file...preciously, I advocated the default, which is 1.5 of ram, with full expansion enabled...presently, I'm now recomending the page file be set to a minimum of 2x ram...you must leave expansion enabled, so if xp does need a bigger file, it will be available, but we are trying to avoid ecpansion by raising the standard.
you must not set the page to static, as your programs will freeze or crash if xp needs a bigger file, therefore, you are trying to set the page file to a value that will be big enough, that your os does not need to resize.
Let me state again...I have forced pf resizing in order to moniter fragmentation, it is not present on my box once I reboot, so I think the white paper is possibly wrong, however, in case it's not, make sure you set the page file to a high enough value...for most that's 1.5. but for me it's higher.
here's a qoute from the white paper...;
...The optimal solution is to create one paging file that is, by default, stored on the boot partition, and then create one paging file on another, less frequently accessed partition. Additionally, it is optimal to create the second paging file so that it exists on its own partition, with no data or operating-system-specific files. By design, Windows uses the paging file on the less frequently accessed partition over the paging file on the more heavily accessed boot partition. An internal algorithm is used to determine which paging file to use for virtual memory management.
When you place a paging file on its own partition, the paging file does not become fragmented, and this counts as another definite advantage. If a paging file resides on a partition that contains other data, it may experience fragmentation as it expands to satisfy the extra virtual memory that is required. An unfragmented paging file leads to faster virtual memory access and greater likelihood of a dump-file capture that is free of significant errors.
If you follow the preceding recommendations, you meet the following paging file configuration goals for optimization and recovery: ...
end qoute
obviously, you need to leave expansion enabled, but try to have the size of it large onough, where resizing does not occur.
further, when you do resize the file, make sure you use the proggy I posted on "free programs" to defrag the pf...then your set
you must not set the page to static, as your programs will freeze or crash if xp needs a bigger file, therefore, you are trying to set the page file to a value that will be big enough, that your os does not need to resize.
Let me state again...I have forced pf resizing in order to moniter fragmentation, it is not present on my box once I reboot, so I think the white paper is possibly wrong, however, in case it's not, make sure you set the page file to a high enough value...for most that's 1.5. but for me it's higher.
here's a qoute from the white paper...;
...The optimal solution is to create one paging file that is, by default, stored on the boot partition, and then create one paging file on another, less frequently accessed partition. Additionally, it is optimal to create the second paging file so that it exists on its own partition, with no data or operating-system-specific files. By design, Windows uses the paging file on the less frequently accessed partition over the paging file on the more heavily accessed boot partition. An internal algorithm is used to determine which paging file to use for virtual memory management.
When you place a paging file on its own partition, the paging file does not become fragmented, and this counts as another definite advantage. If a paging file resides on a partition that contains other data, it may experience fragmentation as it expands to satisfy the extra virtual memory that is required. An unfragmented paging file leads to faster virtual memory access and greater likelihood of a dump-file capture that is free of significant errors.
If you follow the preceding recommendations, you meet the following paging file configuration goals for optimization and recovery: ...
end qoute
obviously, you need to leave expansion enabled, but try to have the size of it large onough, where resizing does not occur.
further, when you do resize the file, make sure you use the proggy I posted on "free programs" to defrag the pf...then your set