The rule of the thumb is 1.5 times the amount of system memory, unless you have too much load on your system.

[[url=http://[/URL]="http://support.micr…"]How to determine the appropriate page file size for 64-bit versions of Windows[/]="http://support.micr…"]How to determine the appropriate page file size for 64-bit versions of Windows[/]

Good one!

But its a bit confusing. 1.5 times of my 8 gig of RAM? is that the number I put in there and the same for each drive other than the C drive of course?

I must have done that right yes? approx 12000 is 1.5 x 8 gig.

1GB= 1024MB, 1.5GB = 1536MB

I swear I get better results by NOT having the page file on any audio drive.

When you have 8 gigs of ram you probably aren't going to utilize the page file as much as most of us.

And yes, if you have at least three drives keeping the temp folder and page file on their own drive is faster.

To JackAttack, I didn't realize they were similar, but this makes sense now. When setting up your drives and where to send your DAW files, do you also have your temp folder in another drive from your C drive?

To John Todd, have you followed the rules, what amount of RAM do you have? Did it just not make a difference or did your sessions stall etc when using it?

My ASIO meter on Cubase would max out and then dropout occurred. Moving the pagefile was one thing that helped. Windows doesn't use the pagefile only when RAM is full, it uses it all the time. So you can have only a little RAM filled and still be hitting the pagefile.

Hey John T, I had the same results as you and realized I never set the C drive to no page file and all the others to custom. My PC seems to be quit faster after trying this last night. I'm going to put it under load later today and I'll confirm my results either way.

Don't put the page file on any disk used to capture or playback audio. Multiply your ram by 1.5 and set both memory values to that number. That way when windows creates the page file it won't expand it, reducing the chance of fragmentation. Once the page file is created, run a full defrag on that drive.

You may also want to google up superfetch/readyboost and familiarize yourself with that technology. You could also experiment with putting the page file on a USB 3 connected flash drive, though you will have to trick windows into believing it's a fixed disk.

One other thing is that you could run with no page file, though it's not recommended or supported by msft -the option is available. I do it on all my heavy load SQL servers. YMMV.

Another little trick is to format your drives to a smaller block size. This helps access times (and disk space) in certain scenarios, one such scenario being streaming type data.

A final thought - if your running out of resources to the point where you need to toy with paging, you may want to think about upgrading your machine specs.