- Joined
- May 22, 2005
- Location
- NY
As long as you keep an exact page file size AFTER defragmenting, performance is fine. If you use a page file range, it gets fragmented. No problems with using an exact size like 1 or 2GB.
Pagefile fragmentation doesn't effect performance in any tangible way. Also, setting the pagefile a "static" size is not a good solution to prevent fragmentation. The initial size should be at least 4x the observed PF usage while the mx should be 2x that. With a high enough initial size the pagefile will not resize, thus it will not become fragmented.
The ONLY time it makes sense to use a static size is if the pagefile is in its own partition. However, even that is a bad idea.
i use 1.5gb....
should i change that to 1 or 2, or is the 1.5 ok?
Like I said, the optimal PF size should be determined by your workload. Run your most intensive applications and then observe your PF usage through perfmon. The PF should be set like this:
Let X = Observed PF Usage
Initial = 4x
Max = 2(4x)