I am using Windows Server 2008 Enterprise. I heard it is better to store page file on the same disk as OS (normally disk C), is that correct? If so, any document about this point?

thanks in advance, George

  • 1
    George2: You've asked this question 3 times here now, haven't you? – joeqwerty Jul 1 '10 at 2:21
  • 1
    @joeqwerty: Hrmph... looks like he has. I wish I'd looked before answering. It sure looks like he's really, really worried about his pagefile. – Evan Anderson Jul 1 '10 at 2:36
  • 1
    @Evan: I'd say so... – joeqwerty Jul 1 '10 at 2:53
  • I asked, but I think I am not asking in the correct words (sorry English is not my native language). And I have not got any documents for this topic. This is why I want to re-write and ask. Thank you! – George2 Jul 1 '10 at 3:28
  • 1
    from the sounds of it I'd think you should get familiar with both support.microsoft.com and technet.com. This question has been asked an answered a million times. Both of these links will provide any answer that your looking for. To me Serverfault is for when you don't have time and or don't care to fully understand the technology that you are using. I don't put you in the later category, I'm pretty sure your trying to understand things. Serverfault.com is nice but the advice pertaining to the entire Microsoft stack is worth what you are paying for it, in other words not much! – tony roth Jul 1 '10 at 5:43

The best place to store the paging file is on a volume that allows for fast, random access. If your server's workload is such that there's not a lot of random IO occurring on the volume where the OS is located then putting the pagefile there is fine. Ideally, you'll have enough physical RAM that you're not paging a lot so it won't matter than much anyway.

If you're planning a workload that will involve any quantity of paging and random IO on the OS volume then you might want to consider a paging volume on a dedicated spindle.

In several documents re: application performance improvement Microsoft makes statements re: putting the pagefile on a dedicated volume. In Operating System Optimizations for BizTalk Server, just as an example, they state:

Isolate the paging file onto one or more dedicated physical drives that are configured as either RAID-0 (striping) or RAID-1 (mirroring) arrays, or on single disks without RAID - By using a dedicated disk or drive array where PAGEFILE.SYS is the only file on the entire volume, the paging file will not become fragmented, which will also improve performance.

You'll find statements like that in documents relating to SQL Server, Exchange, and general OS performance. The pagefile, assuming paging is occurring, is a sink for random IO capacity.

Be warned, though, that if you don't have a pagefile on the OS volume at least the size of physical memory + 1MB the OS won't be able to write complete physical memory dumps in the event of a crash. If full memory dumps aren't important to you then you can get away with a smaller pagefile on the OS volume. Small memory dumps can be written into smaller page files, though. See KB254649 for details and for information about the "rules" in Windows Vista, Server 2008, and 7.

| improve this answer | |
  • In short, is it suggested to put page file on OS or not important? – George2 Jul 1 '10 at 3:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.