Re: Paging file larger than physical memory

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Anywhere between 1.5 and 2.0 will usually work quite well. There is a limit of 4GB per volume though. So if you have 4GB of physical RAM, you'd have to spread the Pagefile over a couple of volumes/drives

--
Cris Hanna [SBS - MVP]
Contributing Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-Business-Server-Unleashed/dp/0672329573/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Harvs" <Harvs@xxxxxxxxxxxxxxxx> wrote in message news:uXNZ2X%23bJHA.5412@xxxxxxxxxxxxxxxxxxxxxxx
Hi

I've run the Exchange BPA on one of my clients' SBS 2003 Server installation with Exchange SP2. One of the critical issues highlighted is "The space for the paging file (4092) is larger than the physical memory (2047). This may affect the system performance. It is recommended to have paging file size equal to the physical memory."
The server has 2 GB of memory installed. On the Virtual Memory dialog page the "Total paging file size for all drives" is recommended to be set at 3069 MB, and is currently configured with Custom Size: initial size 2046 Maximum size 4092.

The BPA help sends me to a KB (bb738135) article which states "The recommended page file size is equivalent to 1.05 times the RAM up to a maximum of 4,095 MB. This means that the largest paging file size per volume that you can set is 4,095 MB."

When viewing some of the other articles listed at the bottom of bb738135 further advice suggests that 1.5 times (not 1.05 times) the installed memory is best. In fact that supports the recommended size stated in the Virtual Memory dialog.

As these Microsoft issued articles appear to contradict themselves, can you tell me what the correct settings should be to satisfy both the Exchange BPA and the SBS server requirements.

Thanks for your interest and help.

Harvs



.

Relevant Pages

  • Re: Low on Virual Memory in SBS 2003
    ... Configuring page files for optimization and recovery in Windows Server ... How to overcome 4,095-MB paging file size limit in Windows ... I don't think a memory leak is the only explanation for this. ... for a lot of RAM faster than Exchange could release it, ...
    (microsoft.public.windows.server.sbs)
  • Paging file larger than physical memory
    ... I've run the Exchange BPA on one of my clients' SBS 2003 Server installation ... the paging file is larger than the physical memory. ... The server has 2 GB of memory installed. ...
    (microsoft.public.windows.server.sbs)
  • Re: Virtual Memory and Paging File
    ... should SQL Server be using a paging file for its SQL ... "memory" in the paging file be faster than retrieving them from "hard disk", ...
    (microsoft.public.sqlserver.server)
  • Re: physical/virtual memory usage problem
    ... Do you make special settings to the paging file? ... > I have another server at another company with 3GB ram, domain controller, ... > 1,6 GB physical ram remain free, store.exe uses a lot of VM (800 MB paged ... exchange is on a DC but It is a single small domain. ...
    (microsoft.public.exchange.admin)
  • Re: Problems with users logging in
    ... This could very well be kernel memory being ... Microsoft MVP - Terminal Server ... seen is 2.25GB used of physical ram and this problem started ... I would first eliminate the licensing problem. ...
    (microsoft.public.windows.terminal_services)