Quote: Originally Posted by pacaveli420
Quote: Originally Posted by MilesAhead
Superfetch set to only cache boot files: Attachment 103716
interesting. is that just with windows running? or with your usual stuff open?
as someone else was saying though....free ram is kinda useless.
and I never really run out (except when something leaks a bunch or indexing allocates 2GB to itself =P)
The point is not the free ram so much as Superfetch will run my HD gathering stats to try to predict what I'm going to do. It will not do so in any useful fashion that's worth the trade-off of running my HD incessantly. By caching only boot files, one slow boot does the stat taking, I get rapid boots, and my HD doesn't run on. As a side effect I happen to get free ram. If you just have to reign in an unruly program, then the thread has been solved and I see no reason why you plow on.
edit: I used this setting originally because Vista ran my HD on so badly. Since I originally posted this I have changed Superfetch setting back to default and use a defragged page file. Seems to run smooth. And if any apps just have to have a page file, well it's there. Windows 7 handles it much better than Vista.
Quote: Originally Posted by craney5
Thanks for that mate, When you set your own page file size in windows is there a "general rule of thumb" to how big this page file should be compared to how much RAM you have installed?
What works is what works for you. There is no "one answer." That's why the number is adjustable in the first place. If one number worked way better than any other, they'd just hard wire it in the code like Avagadro's constant.