Microsoft → [W2K] Recommended paging file size. Trust Win2k?

Ever since I did a clean install of Windows 2000 (after upgrading from Celeron 466/512MB RAM to PIII 750/768MB RAM), the performance has been rather weird. Whenevr I try to select a large file from Windows Explorer (merely highlighting it), there is a pause before the item is selected. Whenever I try to right-click on something to get to properties, I get the same "pause". It seems like everytime I try to perform an action, there is a "hesitation" before the computer acts. What's causing this?

I went to check on my Virtual Memory and noticed that the recommended amount they suggested is 1150 MB. Isn't that a bit excessive? I currently have it set to 960.

Any help is appreciated, thanks.

The best thing to do is fire up the Task Manager and monitor the usage of Memory and Virtual Memory during your slowdowns. You might also want to watch CPU utilization.

I would surprised if your pagefile was too small, because you should get a warning message.

It could be that your pagefile is terribly fragmented, but who knows even if you are getting into it without monitoring your usage a little.

How much virtual memory you need depends on what and and how many applications you are running.

As your physical memory increases, your need for virtual mempoy decreases. This is kind of paradoxical, and against M$ recommendations, nut nevertheless true.

Rule of thumb - page file should be approximately 1.5 times the size of your actual RAM. Hence, 1150 suggested by Win2K is correct.
What you've done is set back the swap file, giving Win2K less room to work.
Also, W2K uses RAM and virtual memory more efficiently than the older WIn9X OS's.

There's no point in having more swap file than you need; probably 512 MB - 1 GB in your case would be more than adequate.

I on the other hand have a XP 3000 with 1GB of ram and only use a 256MB swap file.(well its a trial just switched it) On my PIII 800 I do use 1150MB as suggested for Win2K or XP

[text was edited by author 2003-09-09 00:06:39]

Let windows do whatever it wants, for 2 reasons, 1) you can't stop it 2) if you do stop it, it will error you into submission:)

»Microsoft Application Tips and Tweaks »Tell me about virtual memory