<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Paging File Size in Windows Server 2003</title>
    <link>https://community.hpe.com/t5/windows-server-2003/paging-file-size/m-p/4207172#M5058</link>
    <description>Gerald,&lt;BR /&gt;I would not have 2 separate files as the OS will need to make calls to both creating more I/O.  I would, however, move the paging file to the other system voluem (e.g. D:) to keep that increased I/O off of the main system volume (e.g. C:).  I've never had to do this, but I know it is recommend to move the paging file to its own drive.&lt;BR /&gt;&lt;BR /&gt;Here's a good set of 'tips' from Petri:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.petri.co.il/pagefile_optimization.htm" target="_blank"&gt;http://www.petri.co.il/pagefile_optimization.htm&lt;/A&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 30 May 2008 13:15:45 GMT</pubDate>
    <dc:creator>Gfuss</dc:creator>
    <dc:date>2008-05-30T13:15:45Z</dc:date>
    <item>
      <title>Paging File Size</title>
      <link>https://community.hpe.com/t5/windows-server-2003/paging-file-size/m-p/4207171#M5057</link>
      <description>I have a 30 DL360G4 and G5 in a Citrix Server farm, and the farm built using Ghost Images.  The Servers have 4 GB RAM, and a single 8 GB Paging File, on C Drive, with /PAE in teh boot.ini&lt;BR /&gt;&lt;BR /&gt;Not all of the servers show 8 GB of paging, some show 4 or 6 GB.  We have tried removing all paging, reboot, defrag and then recreate, but we still do not consistently see 8 GB of paging.&lt;BR /&gt;&lt;BR /&gt;There are two drives on the servers, would having two 4 GB paging files be more reliable?&lt;BR /&gt;&lt;BR /&gt;aNY OTHER SOLUTIONS?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 29 May 2008 14:09:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/paging-file-size/m-p/4207171#M5057</guid>
      <dc:creator>Gerald Stephens</dc:creator>
      <dc:date>2008-05-29T14:09:10Z</dc:date>
    </item>
    <item>
      <title>Re: Paging File Size</title>
      <link>https://community.hpe.com/t5/windows-server-2003/paging-file-size/m-p/4207172#M5058</link>
      <description>Gerald,&lt;BR /&gt;I would not have 2 separate files as the OS will need to make calls to both creating more I/O.  I would, however, move the paging file to the other system voluem (e.g. D:) to keep that increased I/O off of the main system volume (e.g. C:).  I've never had to do this, but I know it is recommend to move the paging file to its own drive.&lt;BR /&gt;&lt;BR /&gt;Here's a good set of 'tips' from Petri:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.petri.co.il/pagefile_optimization.htm" target="_blank"&gt;http://www.petri.co.il/pagefile_optimization.htm&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 30 May 2008 13:15:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/paging-file-size/m-p/4207172#M5058</guid>
      <dc:creator>Gfuss</dc:creator>
      <dc:date>2008-05-30T13:15:45Z</dc:date>
    </item>
    <item>
      <title>Re: Paging File Size</title>
      <link>https://community.hpe.com/t5/windows-server-2003/paging-file-size/m-p/4207173#M5059</link>
      <description>We install the OS on C drive, and Citrix published apps on the D drive.  So we keep the paging on same drive as OS.&lt;BR /&gt;&lt;BR /&gt;Just need to have the machines consistently have 8 GB paging, as this is used in the Citrix Load Evaluator for load balancing.</description>
      <pubDate>Mon, 02 Jun 2008 11:11:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/paging-file-size/m-p/4207173#M5059</guid>
      <dc:creator>Gerald Stephens</dc:creator>
      <dc:date>2008-06-02T11:11:12Z</dc:date>
    </item>
  </channel>
</rss>

