How to determine the appropriate page file size pages/sec

When you install a 64-bit version of Microsoft Windows Server 2003 or Microsoft Windows XP, the operating system creates a page file that is half the number of RAM files installed on your computer. However, as the amount of RAM on the computer increases, page files need to be reduced. The following guidelines and methods will help you determine the appropriate page file size for your system.

Comparing memory and CPU limits in Windows 32-bit and 64-bit versions

When you set the 32-bit version or the 64-bit version Windows Server 2003 or Windows XP, there is not enough space on the system hard disk provided by Ram installed on the computer at one and a half times of page files. However, as more RAM is added to a computer, the page files need to be reduced. If you install enough RAM on your computer, you may not need the page files unless one of them requires a specific application.

The following table describes the amount of Ram and the number of CPUs that can be installed based on the computer of the installed operating system. Ram and CPU are limited to 64-bit operating systems, which are larger than 32-bit operating systems.

Collapse the table and expand the table.

General memory limit	32-bit	64-bit
Total virtual address space	4 GB)	16 TB
Virtual Address Space of each 32-bit Process	2 GB, 3 GB if the/3 GB switch is in the system boot	2 GB, if the application is compiled with the 4 GB switch for this/largeaddressaware
Virtual Address Space of each 64-bit Process	Not applicable	8 TB
Page Buffer Pool	470 MB)	128 GB
Non-page Buffer Pool	256 MB	128 GB
System cache	1 GB	1 Tb

Collapse the table and expand the table.

Physical memory and CPU limits	32-bit	64-bit
Windows XP Professional	4 GB/1-2 CPU	128 GB/1-2 CPU
Windows Server 2003, Standard Edition	4 GB/1-4 CPU	32 GB/1-4 CPU
Windows Server 2003, Enterprise Edition	32 GB/1-8 CPU	1 TB/1-8 CPU
Windows Server 2003, datacenter Edition	64 GB/1-32 CPU	1 TB/1 64 CPU
Windows Server 2003 sp 1, Enterprise Edition	64 GB/1-8 CPU	1 TB/1-8 CPU
Windows Server 2003 sp 1, datacenter Edition	128 GB/1-32 CPU	1 TB/1 64 CPU

There is no specific suggested page file size. Your requirements will be based on hardware, the software you use and the load on your computer. To monitor page file usage and requirements, run the system monitor and collect logs for typical usage. Focus on the following counters.

Collapse the table and expand the table.

Counter threshold	Recommended Value
Memory // available bytes	Not less than 4 MB
Memory // pages input/s	No more than 10 pages
Paging file // % allocation status view	Up to 70%
Paging file // % usage peak	Up to 70%
Process // page file peak bytes	Not applicable

Note:Regular use of page files should be tracked. If you increase the usage or load on the system, you usually need to increase the virtual address space and page file space.

Pages/sec counters

Returned when the system monitor is usedMemoryPerformance objectPages/secThe counter value may exceed expectation. These values cannot be associated with page file activity or cache activity. Conversely, these values may be caused by applications that are reading memory ing files in order.

Pages/secPage of the counter count, read from the disk or write to the disk to parse the memory reference to the page. These pages are not used in memory.Pages/secThe value isPage input/secAndPage output/secThe sum of the counter values.Pages/secThe counter includes the nominal page communication of the application that accesses file data through the system cache.

Pages/secIs the main counter monitoring, if you are worried about excessive memory pressure (crash), and too many pages may cause.

However,Pages/secCounters are also used for other activities, such as continuous reading of memory ing files or accounts that are not cached. Generally,Pages/secWhen you see the following calculation activities:

• High ValueMemory: Pages/secCounter.
• In the average value, relative to the monitored system or high value inMemory: available bytesCounter.
• Average or small valuePaging file: % usedCounter.
• Non-cached memory ing files also view average or low cache activity. (A low cache activity is also called a cache error activity ).

Therefore, the high valueMemory: Pages/secCounters do not necessarily indicate memory pressure or report errors on the system monitor. To read your system accurately, you must monitor other counters.

How to calculate the page file size

You can use one or more of the following methods to calculate the page file size.

Method 1: Use Performance Logs to learn about paging activities on your computer

1. ClickStart, PointingManagement toolsAnd then clickPerformance.
2. ExpandPerformance Logs and alarms, ClickCounter log, Right-click the blank area, in the right pane, and then clickCreate log settings.
3. InNameEnter the name of the log in the dialog box, and then clickOK.
4. InGeneralClickAdd counter.
5. ClickUse a local computer Counter.
6. InPerformance objectList, clickPaging file.
7. ClickSelect a counter from the listClick% Allocation status view, And thenAdd.
8. InPerformance objectList, clickMemory.
9. InSelect a counter from the list, ClickAvailable bytesAnd then clickAdd.
10. InSelect a counter from the list, ClickPage input/secClickAddAnd thenClose.
11. ClickOK.

Use a typical computer to learn about the logs collected during paging activities on your computer. Then, adjust the page file size accordingly.

Method 2: Use Page file byte peakThe counter calculates the page file size.

1. ClickStart, PointingManagement toolsAnd then clickPerformance.
2. ClickSystem Monitor.
3. In the right pane, click+(Add button ).
4. ClickUse a local computer Counter.
5. InPerformance objectList, clickProcess.
6. ClickSelect a counter from the listClickMaximum page file bytes, ClickAdd, And thenClose.
7. Allows your computer to run counters during typical usage.
8. Note thatPage file byte peakThe maximum value of the counter, and then multiply the value by 0.70. The sum of the formula is to set the page file size.

Method 3: Calculate the minimum and maximum page file sizes

To determine the system required to approximate the minimum page file, calculate the total number of private bytes for each process on the system. Then, subtract the amount of memory in the system.

To determine the Approximate Maximum page file space required for your system, calculate the total number of private bytes for each process on the system. Then, add the margin of extra space. Does not subtract the amount of memory on the system. The size of other margins can be adjusted based on the requirements used to estimate page files that you trust in the snapshot data.

Note:The estimated value is accurate only when the snapshot of the data for calculation is accurate.

Page file input/output rate

To avoid heavy-load system or other disk and page input/output (I/O) activities, set page files on your computer to comply with the following guidelines:

• If the page I/O (actual disk I/O) rate is more than 10 pages per second, we recommend that you place the page files that do not show I/O activity on the system disk. When the page I/O rate is 10 pages per second or more, we recommend that you use a dedicated disk for paging on different hard disks.
• If the page I/O rate is used for paging over 60 disk I/O operations per second on a specific disk, use multiple dedicated page hard disks for better performance. In this way, you can use multiple non-strip disks or RAID 0 strip disks. An I/O hard disk dedicated to pages with I/O activity every 60 pages.

  For example, if the system averages 150 pages of I/O activity per second, three independent hard disks or three RAID 0 band disks are used as page files.

  Note:These are estimated to be hard disks running at 7200 revolutions per minute (RPM. If you use a hard disk that runs faster, the I/O rate disk can process the pages that will be added by I/O.

  Note:Whether the highest performance for your system is used for peak I/O rates rather than average I/O rates.

ImportantSupported information: This article is dedicated to computers that do not require kernel mode or full memory dump analysis. When a business process needs to be captured on the server, it should at least be a dump analysis, the physical ram of the business-critical server of the physical memory of the traditional model of page files plus the default physical Ram size of 1 MB or 1.5 times. This ensures that the available disk space of the operating system partition is sufficient to accommodate the operating system, patches, installed applications, installed services, a dump file, and page files. On a 32 GB memory server, drive C may have to be at least 86 GB to 90 GB. This is a 32 GB memory dump, a page file (1.5 times, physical memory) of 48 gb, 4 GB, the operating system and 2 to 4 GB are applications, installed services, and temporary files. Remember that the driver or kernel mode service leakage may consume all available physical memory. Therefore, the SP 1-based Windows Server 2003x64 server has 32 gb ram in 64-Bit mode and may have 32 GB kernel memory dump files, you want only 1-2 GB dump files to be in 32-Bit mode. This is because the memory pool is greatly increased.