window uses virtual memory which is a mix of ram and hardive
The information on your pagefile usage is reflected in the "commit charge" section, which shows your total allocated memory, both physical and paged.
.. for some silly reason the more ram u have the bigger the swopfile is that gets created..
XP seems to decide on one to one.. so with 4 gigs of ram it sets aside 4 gigs of hardrive space.. it then refers to this as available memory.. 8 gigs..
You can easily control the behavior of your swapfile, and set whatever limits on it that you please, both minimum and maximum. You can even disable it completely if you so wish, though I don't really recommend it.
my swopfile now called pagefile.sys is set to default at 2 gig.. when task manager say memory available it includes this 2 gig hardrive file
Not exactly. I'm referring to the "Physical Memory" section, which doesn't include pagefile usage. To get the complete picture you have to look at both the Physical Memory section and at your Commit Charge, which reflects virtual memory (your physical memory combined with your pagefile(s)). To help with the picture I'll use the current numbers from my own Task Manager:
Commit Charge (K)
Total: 973344 (this is the current total of allocated virtual memory(pagefile+physical))
Limit: 4034876 (this is the total amount of virtual memory (pagefile+physical))
Peak: 994400 (this is the highest amount of virtual memory that has been allocated this session)
Physical Memory (K)
Total: 2096492 (total usable physical RAM. pretty straightforward)
Available: 1024272 (physical RAM currently available,
can include some of the space in the system cache, this is not necessarily fallow memory)
System Cache: 407488 (this is the amount of physical RAM currently used by the system cache)
I have two gigabytes of RAM installed, this is reflected in the total under Physical Memory. My pagefile is currently configured to occupy between a minimum of 2046 MB and a maximum 4092 MB. At the time these numbers were polled it was sitting at the bottom end of that range. The sum of my pagefile and my physical memory (less some nonpageable areas) is shown under Limit in the Commit Charge section. Since the pagefile can grow up to nearly four gigabytes if needed, the Limit is subject to change.
simply leave (or preload) oft used apps in memory ready for instant use.. waiting for the hardrive should rarely happen..
This describes Vista's SuperFetch feature. But here's the catch. TANSTAAFL (there ain't no such thing as a free lunch). It's true in thermodynamics and it's definitely true in computing. One way or another, you WILL be waiting for the hard drive to load that data. It's just a matter of timing. A SuperFetch enabled system will have more disk activity at startup, and that's where the loading cost is paid. You can interrupt that process of course, but then the benefit offered by SuperFetch is offset.
XP just just leaves spare ram standing idle.. which is my only gripe with it..
Except that it doesn't really. Although XP doesn't proactively load the cache (except for standard read-ahead), it won't purge the cache needlessly, either.
So relax. You may not have SuperFetch, but your system cache is doing you some good.