bump.....
er, I'm a "set a static size at the beginning that is in one block" kinda guy. As an FYI, I have had exchange unmount the volume and refuse to remount it. Had an old exchange admin right there, and he said "Pagefile, bet you lunch"...needless to say, with a heavily fragmented page file, and a few hours to truely fix it, and I was buying him a steak for lunch. No other thing fixed it, it was the pagefile that cause it to start working again. Needless to say, on my SERVERS at least (not usually on my home box) I set a static page file. And to all the people who say to move it to a different drive/partition, you should leave some on the C:\ partition, otherwise windows doesn't dump correctly, and it makes fixing problems that much harder.
er, I'm a "set a static size at the beginning that is in one block" kinda guy. As an FYI, I have had exchange unmount the volume and refuse to remount it. Had an old exchange admin right there, and he said "Pagefile, bet you lunch"...needless to say, with a heavily fragmented page file, and a few hours to truely fix it, and I was buying him a steak for lunch. No other thing fixed it, it was the pagefile that cause it to start working again. Needless to say, on my SERVERS at least (not usually on my home box) I set a static page file. And to all the people who say to move it to a different drive/partition, you should leave some on the C:\ partition, otherwise windows doesn't dump correctly, and it makes fixing problems that much harder.
So what ratio do you use for RAM to PF, and what's your ratio of amount of PF on one HD, to the next?
Nothinman
Elite Member
- Sep 14, 2001
- 30,672
- 0
- 0
I can see how having a really, really heavily fragmented pagefile could cause problems because it would take extra resources to manage those extents but I imagine it would only have any real affect on a box that's really tight for resources, like an Exchange box.
And you should have one one the system drive as well as one on another physical partition, Windows will use the one on the less busy drive.
Phoenix86
Lifer
- May 21, 2003
- 14,644
- 10
- 81
No, windows will adjust for you.
The idea of a RAM-PF ratio is BS. Your memory requirements determine your size.
Run your system for a while, give it a workout. Then look at commit charge peak in task manager. This is your maximum memory requirements. You don't want to cut yourself short, so your RAM+PF must be over this value, say by at least 25%.
PF size should=(commit charge peak)(1.25)-RAM
That's what forums are for, just because the question keeps coming up doesn't mean that you should be annoyed with it. Now if everytime the question is asked it's by a jr. member then it may get a little annoying because there just using us for one quick question but other then that that's what this is here for right. Also if it's annoying don't read any posts that have the words page or file in them. Just my 2 cents, page files are hard to understand completely if you want to configure them for specific uses, I have been told and tought probably 3 different ways to implement a page file, each unique in it's own way or contradicting the other.
Yes, but it's the same question, the same arguments, and the same boring crap each time.
I swear, I could probably match selected quotes from this thread with other pagefile threads.
What is nef philly? That's a good one, I can't for the life of me figure out what nef is, National Environment Foundation?
flexy
Diamond Member
- Sep 28, 2001
- 8,464
- 155
- 106
why should "let windows manage..." be good ?
IT'S NOT !
I always look in the properties, check what it says under "recommended" and then set this value under "custom" as minimal and maximal size.
Eg. with 1Gig ram it says "recommended 1534MB"....enter both values in the custom fields. Thus windows does NOT have to deal with
resizing etc. and the pagefile can be easily de-fragmented (eg. with diskkeeper or perfectdisk).
I have a static (fixed size) pagefile ever since i started with PCs since i always was told its best compared to "let windows manage"....and yes, 1.5x memory is usually right.
IT'S NOT !
I always look in the properties, check what it says under "recommended" and then set this value under "custom" as minimal and maximal size.
Eg. with 1Gig ram it says "recommended 1534MB"....enter both values in the custom fields. Thus windows does NOT have to deal with
resizing etc. and the pagefile can be easily de-fragmented (eg. with diskkeeper or perfectdisk).
I have a static (fixed size) pagefile ever since i started with PCs since i always was told its best compared to "let windows manage"....and yes, 1.5x memory is usually right.
Nothinman
Elite Member
- Sep 14, 2001
- 30,672
- 0
- 0
If it wasn't good why would they make it the default?
A) Pagefile fragmentation is largely irrelevant.
B) The pagefile only grows, it can't shrink so there's no "constant resizing".
Then you're wasting disk space for no good reason and you're removing a safety need by limiting how big your pagefile can be. You must not stress your memory usage very much.
Everyone knows Micro$oft engineers are all n00bs and u can do mad hax to make Winblows uber quick!!!1111
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 21K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter