Paging File set at installation and contiguous. Paging file ends up fragmented.
Posted 05 January 2010 - 02:16 PM
Posted 11 January 2010 - 03:30 AM
1. Use the VBS the first time around to disable pagefile entirely, and reboot in 2 mins (you are using autologon, I guess).
2. Autologon a second time and run a defrag command, and set the next task to reboot.
3. Autologon a 3rd time and enable pagefile as per your preferences, then reboot automatically.
One other possibility, is to see if one of the defragging apps (DisKeeper, Raxco, O&O, Defraggler, Vopt, whatever) offers a command-line switch to auto-defrag C: drive and consolidate the pagefile at the same time. If you've nLite'd so much that the pagefile.vbs is removed, chances are you might as well have a defragmentation run to speedup your OS and maximize performance. On the other hand, if your C: drive is located on an SSD, then pagefile fragmentation isn't an issue (heck, pagefile is not even required with your 4GB RAM and an SSD!).
This post has been edited by prathapml: 11 January 2010 - 03:31 AM
Posted 11 January 2010 - 02:30 PM
Posted 11 January 2010 - 02:42 PM
A rather largish choice, if I may go slightly OT, the 1.5 Myth is still a die-hard one.
Posted 11 January 2010 - 02:49 PM
edit - may not as you want it to happen during Install...
edit2 re jaclaz above... very true! Pagefile is just that - a PAGE file (Mainframe, anyone?)!
This post has been edited by submix8c: 11 January 2010 - 02:52 PM
Posted 12 January 2010 - 04:31 PM
Posted 13 January 2010 - 08:02 AM
Posted 13 January 2010 - 12:56 PM
I am not convinced it's "small enough", but anyway sounds much better.
Let's see what happened in the years.
XP (32 bit) was "advertised" as having the need for a bare minimum of 64 Kb of memory, and usable with 128 Kb:
Using the usual 4x multiplying factor that is needed with MS requirements statements , you had in practice:
64x4=256 Kb "real" bare minimum to boot
128x4=512 Kb "real" minimum to have a usable system
In real world a working machine you would have a further 2x factor as in:
Now using the mythical 1.5x factor you have respectively:
256x1.5=384 pagefile +256 RAM=640 Mb TOTAL
512x1.5=768 pagefile +512 RAM=1280 Mb TOTAL
1.024x1.5=1.536 pagefile +1.024 RAM=2.560 Mb TOTAL
Now, you have x64 that can address a larger amount of RAM than x32, but I do not think that x64 needs that much amount of memory, I mean something like 4 time the actual RAM and (4.096+2048)=6,144/2.560=2.4 times the TOTAL.
- What happens if you try running your "Torture Test" on your machine after removing RAM as to remain with "only" 2 Gb of it?
- What becomes the usage of the pagefile?
Hints (not necessarily directly related to questions above):
- an OS tries to use as much resources as you have available
- "torture tests" (and in a minor way benchmarks) are - besides inhuman - largishly pointless, the only thing is to see how your paricular system bewhaves with the particular settings you chose with the particualr use you make for it.
Posted 13 January 2010 - 02:18 PM
What you could do is install your windows and start up every Microsoft Office program, open all your other programs, maybe pop in DVD, then check and see what kind of RAM usage you are getting. If you are still under 4GB at extreme usage, you can probably survive without a pagefile.
For any readers who want to test this out, here is the reg setting that disables your page-file.
Windows Registry Editor Version 5.00 ;----------------------------------- ;Disables The Paging File ;----------------------------------- [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management] "PagingFiles"=hex(7):00,00,00,00
Posted 13 January 2010 - 04:23 PM
Posted 13 January 2010 - 05:19 PM
Posted 14 January 2010 - 04:12 AM
But there can be "good" and "bad" compromises.
The whole point is that to reach a compromise, you have to carry on a negotiation with the other part.
Negotiating will take time, in order to reach a compromise good enough to have both parties reasonably happy.
As said, 1.5x is totally unjustified and a rule of thumbs that could only be used on completely different ranges of available RAM.
Your current 0.5x is only a hopefully better approximation.
If you can substantiate your decision and correlate the max value registered during a "torture test" 1,300 with the final value you used, 2,048, it would be a step ahead, after all 2,048/1,300=157%
Like when you choose a power supply, you calculate that your actual power need is in the 250÷300 W range and then, knowing that a power supply works better at 1/2 to 2/3 of it's "tag power" you go for a 450÷600 W one.
But pagefiles do not work like that.
Let's take another example, you have to buy a car for your wife.
From historical data you know:
- that you are a family of three
- that the car will never be used on a highway or for longish trips
- that it's main use will be commuting home/work, go to the supermarket and take your child to school
Now which car do you buy?:
- a sub-compact 4 seater (simply because three seaters are not available)
- a big 4x4, 7 seater
If you live in the US #2, if you live in Europe (and/or are cheap, like me ) #1.
In other words, let's say that you fancy having a 2,048 Mb pagefile and it's allright, but do not try "selling" us that it comes from a strictly technical reason, as we won't buy it.
This post has been edited by jaclaz: 18 January 2010 - 07:26 AM
Posted 14 January 2010 - 06:48 AM
Different strokes for different folks, and "johnhc" here might have his reasons for what he wants, and all of you that have commented definitely have strong technical reasons and experience to back their recommendation.
I might personally disable pagefile altogether, but everyone need not HAVE to share that view.
But at the end of the day, the question is (*or was, and has probably been abandoned) "how to set my pagefile AND not have it fragmented on disk".
Let us get back on topic, and let the thread die a natural death if there are no further solutions that we can thrash out.
Posted 20 January 2010 - 06:52 PM
pagefile.vbs = 1,,,,,,,2,0,0,pagefileconfig.vbs pagefile.vbs = 1,,222222,,,,,2,0,0,pagefileconfig.vbsEnjoy, John.