System Paging File/Virtual Memory

Should there be a limit as to how much memory I should use for this? I am
using 10,000 MB, but not sure if that is too much or not? What is the
recomended?

On Sat, 7 Jun 2008 20:31:01 -0700, UnknownTBeast
<> wrote:

>Should there be a limit as to how much memory I should use for this? I am
>using 10,000 MB, but not sure if that is too much or not? What is the
>recomended?

For most letting Windows decide for itself is the best choice. Virtual
Memory is actually space on your hard drive, not real RAM. The purpose
of the Paging File, often called the Swap File in earlier versions of
Windows, is to shuffle bits of applications, data and Windows code in
and out of memory. Generally 1.5 times your RAM is a good size for the
Paging File. Less, and your system might be sluggish. More is just
wasted space on your hard drive that could be used for other things.

You can use Task Manager (Ctrl-Alt-Delete) all pressed at once to see
how well Windows is doing with memory and CPU management under the
Performance Tab. Watching the two vertical bar graphs gives you a idea
how things are running. For most people if there system is idle,
meaning you aren't really doing much if anything the CPU Usage should
be under 4%. Mine typically shows 1-2%. Memory at idle should be
roughly be half your total RAM or less. More once you do something
more intensive. A sign you don't have enough RAM to do what you
typical use your computer for is you hear your hard drive grinding
away a lot. This is Windows swapping out to the Paging File
excessively because it is starved for memory. No matter how big you
make your Page File whatever you do with your computer code has to be
brought into physical memory before anything happens.

Either 1.5 x installed memory or let Windows manage it should be fine.

"UnknownTBeast" <> wrote in message
news:1A5CAF11-88F9-4078-9C79-...
> Should there be a limit as to how much memory I should use for this? I am
> using 10,000 MB, but not sure if that is too much or not? What is the
> recomended?

I generally let Windows manage the size of the virtual memory file.
Some say 1.5 or 2X the amount of RAM you have; but it depends on what you
run.
Every user is different and a system managed size will make it
larger/smaller depending on how YOU are using it.
Unless you have a very small HDD, it shouldn't be an issue.
On some of my systems, I have a separate HDD just for the swap file.
I have a lot of computers, so I also have many older, relatively small HDDS
laying around.
I just take one that is 10-30GB, pop it in and allow Windows to use it ONLY
for the swap file.
It may give a marginal speed increase because the main drive does not have
to move around the read heads to access the swap file then go back to the
program it is using.
Not everyone will benefit from that configuration, but if you have unused
drives laying around...it's better than tossing them in the trash.

"UnknownTBeast" <> wrote in message
news:1A5CAF11-88F9-4078-9C79-...
> Should there be a limit as to how much memory I should use for this? I am
> using 10,000 MB, but not sure if that is too much or not? What is the
> recomended?

On Sat, 7 Jun 2008 20:31:01 -0700, UnknownTBeast
<> wrote:

> Should there be a limit as to how much memory I should use for this? I am
> using 10,000 MB, but not sure if that is too much or not? What is the
> recomended?



In general there is very little point to doing anything but letting
Windows manage the size. The only improvement you could possibly make
is saving a little disk space, but in these days of very cheap hard
drives, the value of that is tiny.


--
Ken Blake, Microsoft MVP - Windows Desktop Experience
Please Reply to the Newsgroup