Paging file question

[xpgeek]

Was reading a site with some tweaks for increasing NTFS file system performance, a bunch of stuff I already knew and know doesn't really make that big a difference, but this one I'd never seen before, and am wondering if its true and or will really make a difference.

Use FAT32 for the Paging File

Finally, if you have a second physical disk in your machine, you can boost performance by moving your paging file (pagefile.sys) onto your second drive.

Format the new volume using FAT32 instead of NTFS, since FAT32 gives slightly better read performance on smaller volumes.

I keep a separate small 2 gig partition on my second drive just for my paging file already, but the partition is formatted NTFS. Will making this a FAT32 partition instead really make a difference ? Looking especially for Microns opinion.

[Micron]

If you want to move the page file to another drive, first select the original drive and then choose the No Paging File option to remove the page file from that drive. Then select the other drive and choose either Custom Size or System Managed Size to add a new page file to that drive.

If you want to split the page file over a second drive, leave the original drive as is, select the second drive, and choose either Custom Size or System Managed Size to create a second page file on that drive. If Custom Size is specified for either or both drives, set the new values now.

I would not recommend using different file systems. Certain files within windows need windows encryption that comes with NTFS, not only that, system data like Logon information, user information are all encrypted. Putting these on a FAT32 drive or partition will cause problems, Why...

Too many reasons, but a main reason is the system's memory dumps.

Windows XP first writes the debugging information to the paging file—Pagefile.sys in the %SystemDrive%. (Note that this is not affected if you choose to purge the contents of the paging file at shutdown).

When you restart the computer, Windows XP then transfers the information to the dump file. Therefore, you need to have a large enough paging file to handle the memory dump. If your main drive is NTFS and the page file is FAT32 the chances are your system will crash.

This is particularly true for the Complete Memory Dump option, which requires the paging file to be as large as the physical RAM, plus one megabyte. The file size of the Kernel Memory Dump is typically about a third of physical RAM, although it may be as large as 800 MB.

How they work

Small Memory Dump (64 KB). This option writes the minimum amount of useful information that could be used to identify what caused the stop error. This 64-KB file includes the stop error number and its description, the list of running device drivers, and the processor state.

Kernel Memory Dump. This option writes the contents of the kernel memory to the disk. (The kernel is the Windows XP component that manages low-level functions for processor-related activities such as scheduling and dispatching threads, handling interrupts and exceptions, and synchronizing multiple processors.) This dump includes memory allocated to the kernel, the hardware abstraction layer, and the drivers and programs used by the kernel. Unallocated memory and memory allocated to user programs are not included in the dump. This information is the most useful for troubleshooting, so we recommend using this option.

Complete Memory Dump. This option writes the entire contents of RAM to the disk.

Below are the advantages and disadvantages of NTFS over FAT32

NTFS or FAT32: Which Disk Format Should You Choose?

The single most important disk decision you have to make on a Windows XP system is which file system to choose for each drive or volume. On a clean install, you face this choice during Windows Setup; on an upgrade from Windows 98 or Windows Me, Setup lets you choose whether to convert the file system used on your existing drive. And you face the issue all over again if you repartition an existing drive or add a second (or third or fourth) drive to an existing system. File-system choices available to you depend on the size of the partition or volume you create. Most of the time, the choice comes down to NTFS or FAT32. On drives that are less than 4 GB in size, the 16-bit version of the FAT file system is also an option.

Avoid FAT16

The 16-bit FAT file format exists in Windows XP for backward compatibility purposes only. Because it was designed in an era when hard disks were dramatically smaller, it’s woefully inadequate on modern systems. In the modern era, FAT16 is appropriate for floppy disks and very small hard-disk partitions only. If you must use a FAT16 partition for compatibility reasons, try to keep its size under 511 MB.

Which file system should you choose? There’s no right or wrong answer. NTFS has significant advantages in reliability, security, and flexibility, but in some system configurations FAT32 is a better choice. Make your decision based on the following factors and how they apply to your needs:

Compatibility. Windows 95/98/Me cannot recognize NTFS volumes. On multiboot systems, it’s essential that you use FAT32 for any local drives that you want to access when you boot the system using Windows 95, Windows 98, or Windows Me. Note that this restriction does not apply to network access. Assuming you’ve set up sharing properly, other network users can access your shared folders from computers running any other version of Windows, regardless of the local disk format.

Security. On an NTFS volume, you can restrict access to files and folders using permissions. With Windows XP Professional, you can add an extra layer of protection by encrypting files. On a FAT or FAT32 drive, anyone with physical access to your computer can access any files stored on that drive.

Reliability. By design, an NTFS volume can recover from disk errors more readily than an otherwise identical FAT/FAT32 drive. NTFS uses log files to keep track of all disk activity. In the event of a system crash, Windows XP can use this journal to repair file system errors automatically when the system is restarted. In addition, NTFS can dynamically remap clusters that contain bad sectors and mark those clusters as bad so that the operating system no longer uses it. FAT and FAT32 drives are more vulnerable to disk errors.

Expandability. Using NTFS-formatted volumes, you can expand storage on existing drive letters without having to back up, repartition, reformat, and restore.

Efficiency. On partitions greater than 8 GB in size, NTFS volumes manage space more efficiently than FAT32. The maximum partition size for a FAT32 drive created by Windows XP is 32 GB; by contrast, you can create a single NTFS volume of up to 16 terabytes (16,384 GB) using default settings, and by tweaking cluster sizes, you can ratchet the maximum volume size up to 256 terabytes.

Use Fdisk for extra-large FAT32 drives

Most of the time, it’s better to use the Disk Management utility to manage partitions you plan to use with Windows XP. However, under one specific circumstance, you might want to prepare a disk using the tools from Windows 98 or Windows Me instead. Windows XP cannot create or format a FAT32 partition greater than 32 GB in size, but the Fdisk utility from those earlier Windows versions can. Boot from a startup disk prepared by either of those operating systems and use Fdisk to create the partition. After formatting the extra-large FAT32 partition using the Windows 98/Me Format command, restart Windows XP.

To view information about the file system currently used for a given drive or volume, right-click the drive icon in the My Computer window or the volume in the Disk Management window and choose Properties.

[xpgeek]

Thanks for reply. I already knew all the rest just needed to know if using FAT32 for paging file, while system drive is NTFS, was a good idea. I didn't think it sounded like a good idea.

[Micron]

Your welcome, I knew you knew it, but detailed it for others that don't know.

[FisionChips]

...like me. Very informative, thanks.

Couple of questions though:

Is it not possible to override the use of the paging file for system dumps - is there no option to specify an alternative file for example?

Is there a guide somewhere to the optimal partition, cluster etc sizes when formatting and partitioning a volume for the first time.

[Micron]

I will write one.

You can turn off the dumps as I mentioned in my previous post, but I wouldn't recommend it.

To delete the paging file at shutdown. You can do this via the Group Policy snap-in (gpedit.msc gpedit is not available in Windows XP Home Edition) by opening the Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Options branch. In the Policy list, choose the Shutdown: Clear Virtual Memory Pagefile item. Note that this is equivalent to changing the value of the following registry setting to 1:

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ClearPageFileAtShutdown

You can also automatically clear the Start menu’s My Recent Documents list at shutdown. To do this, open the Group Policy snap-in, and display the User Configuration, Administrative Templates, Start Menu And Taskbar branch. There are two policies to work with here:

Clear History Of Recently Opened Documents On Exit Enable this policy to clear the My Recent Documents list at shutdown. This is equivalent to setting the following registry value to 1:

HKCU\Software\Microsoft\Windows\CurrentVersion\Gro up Policy Objects\LocalUser\Software\Microsoft\Windows\Curre ntVersion\Policies\Explorer\ClearRecentDocsOnExit

Do Not Keep History Of Recently Opened Documents Enable this policy to prevent Windows XP from tracking recently used documents altogether. This is equivalent to setting the following registry value to 1:

HKCU\Software\Microsoft\Windows\CurrentVersion\Gro up Policy Objects\LocalUser\Software\Microsoft\Windows\Curre ntVersion\Policies\Explorer\NoRecentDocsHistory

[FisionChips]

OK... one other question...

Any idea how Vista will be handling the system dumps? Will it too be writing them to the pagefile?

Sorry XPgeek - getting somewhat off topic here but, coming from a mainframe systems background where things are organised somewhat differently, the idea of writing system dumps to a pagefile is akin to scraping your fingernails down a blackboard.

[Micron]

Yeah, Vista will still use the Paging file. Though through WINFS.

[xpgeek]

I thought WINFS wasn't gonna be ready in time for Vista.

[Micron]

Apparently it will be: http://msdn.microsoft.com/windowsvista/getthebeta/default.aspx

[xpgeek]

Oh, cool. Vista is looking better everyday.

I just read they testing a kickass two way (inbound and outbound protection) firewall for Vista too.

[Micron]

Vista is soooo cool.