This chapter describes how to tune the Windows Server operating system to ensure that Oracle Database is running in the best possible environment.
This chapter contains these topics:
Note:For the sake of brevity, this discussion uses the collective term Windows Server when a statement applies to Windows 2000 Server and Windows Server 2003 operating systems.
Windows Server operating systems offer considerably fewer tuning adjustments than UNIX. This difference constrains systems administrators when they try to optimize Windows Server performance, but it also makes Windows Server easier to use.
There are still ways, however, to make Windows Server a better application server environment for Oracle Database. Most of the operating system specific procedures described in this chapter enable Oracle Database to reserve more system resources, such as CPU, memory, and disk I/O.
In addition, because Oracle Database is a high-performance database management system that effectively uses resources of your Windows computer, it should not also serve as any of the following:
Primary or backup domain controller
File or print server
Remote access server
These configurations consume network, memory, and CPU resources. In addition, the Windows computer that is running Oracle Database should not be locally accessed with a high frequency or intensively used for local user processing, unless it has enough resources to accommodate all this activity.
Large page support is a feature of Oracle Database 10g Release 1 (10.1) or later. It provides a performance boost for memory-intensive database instances. By taking advantage of newly introduced operating system support, Oracle Database 10g Release 1 (10.1) or later can now make more efficient use of processor memory addressing resources. Specifically, when large page support is enabled, the CPUs in the system will be able to access the Oracle Database buffers in RAM more quickly. Instead of addressing the buffers in 4KB increments, the CPUs are told to use 4MB page sizes when addressing the database buffers.
This feature is particularly useful when the Oracle buffer cache is several gigabytes. Smaller-sized configurations will still see a gain when using large pages, but the gain will not be as great as when the database is accessing large amounts of memory.
To enable large page support, the system administrator must grant the "Lock pages in memory" privilege to the
oracle user. This privilege is not enabled by default when Windows is installed. To grant this privilege:
Choose Start > Settings > Control Panel.
The Control Panel window opens.
Double-click Administrative Tools.
The Administrative Tools window opens.
Double-click Local Security Policy.
The Local Security Settings window opens.
In the left pane of the Local Security Settings window, expand Local Policies and select User Rights Assignment.
In the right pane of the Local Security Settings window, select Lock pages in memory and choose Action > Security...
The Local Security Policy Setting dialog opens.
The Select Users or Groups dialog opens.
oracle user from the Name list.
Click OK to close the Select Users or Groups dialog.
Click OK to close the Local Security Policy Setting dialog.
To take advantage of large pages on Windows Server 2003, the amount of physical memory must be greater than the amount of System Global Area (SGA) specified in the parameter file.
Large pages may not be allocated at all times during instance startup; either all of the SGA is allocated using large pages or all of SGA is allocated using regular pages.
Note:Large page usage locks the entire SGA into physical memory. Physical memory is not released during a shrink operation.
See Also:Your operating system documentation for restrictions on allocating large pages
To enable large page support:
oracle.key in a text editor and record the value found. It is set by Oracle Universal Installer. The default is:
Start Registry Editor at the command prompt:
Note:Although Registry Editor lets you view and modify registry keys and parameter values, you normally are not required to do so. In fact, you can render your system useless if you make incorrect changes. Therefore, only advanced users should edit the registry! Back up your system before making any changes in the registry.
Find the key corresponding to the value found in
oracle.key. In the default case, for example, you would look for:
Create one of the following, depending on where you want to enable large page support:
ORA_LPENABLE=1 to enable large page support on all instances
_LPENABLE=1 to enable large page support on a specific instance
Exit Registry Editor.
By default Oracle allocates the minimum available large page size when using large pages. The minimum available large page size, 16 MB, is obtained by using the
Caution:Do not set initialization parameter
lock_sgawhen large pages are enabled. Large page usage locks the entire SGA into physical memory. When used with parameter
lock_sga, database startup fails with an error because the operating system automatically locks. That is, it prevents memory from being paged to disk when large pages are requested. Physical memory is not released during a shrink operation.
One of the settings provided by default during installation of Windows Server gives interactive foreground applications priority over every background process. To prevent foreground applications on the server console from taking excessive processor time away from Oracle Database, you can reduce priority for foreground applications.
See Also:Your operating system documentation for instructions on reducing priority of foreground applications
Windows memory manager divides up system memory into three different pools described in Table 7-1.
|Pool||Percent of Total Memory|
Kernel and other system services
Windows Server memory manager tries to balance each application's usage of memory by dynamically paging memory between physical RAM and a virtual memory paging file. If an application is particularly memory-intensive (like Oracle Database) or if a large number of applications are running concurrently, then combined memory requirements of the applications may exceed physical memory capacity.
The large proportion of memory reserved for file caching (41%) can be quite beneficial to file and print servers. But it may not be advantageous to application servers that often run memory-intensive network applications. A Windows Server file cache is particularly unnecessary for Oracle Database, which performs its own caching through System Global Area.
You can reset the Windows Server memory model from the default file and print server, with its large file cache, to a network applications model, with a reduced file cache and more physical memory available for Oracle Database.
See Also:Your operating system documentation for instructions
After you have significantly reduced the file cache as described in "Configure Windows Server to Be an Application Server", you can retrieve additional physical memory for Oracle Database by disabling services not needed for core operating system functionality. Unnecessary services include:
License Logging Service
Plug and Play
Remote Access Autodial Manager
Remote Access Connection Manager
Remote Access Server
Consult with your systems administrator to identify other unnecessary services.
Do not disable any of the following services:
OracleStartSID (Oracle8 release 8.0.6 and earlier)
Remote Procedure Call (RPC) Service
TCP/IP NetBIOS Helper
See Also:Your operating system documentation for instructions on disabling unnecessary services
Remove all unnecessary network protocols on Windows so that processing time can be concentrated on servicing only critical protocols.
See Also:Your operating system documentation for instructions on removing unnecessary network protocols
If multiple protocols must be installed on the server, you can give the protocol most frequently used by Oracle Database highest priority by resetting the network protocol bind order.
See Also:Your operating system documentation for instructions on resetting network protocol bind order
If you have public and private network interface cards (NICs) on a single Windows computer and they are not in the correct order, then you might experience problems with any configuration (Oracle Enterprise Manager, for example) that uses
If the private NIC is seen first by Windows, then a
gethostname call will return the host name of the private interconnect. Whichever tool is calling
gethostname will have configuration or connectivity problems stemming from this non-public network information.
On a Windows 2000 computer, you can determine the current order of your NICs, and change it if necessary, as follows:
Choose Start > Settings > Network and Dial-up Connections.
Choose Advanced > Advanced Settings.
The Connections: field lists your public and private Local Area Connections. To change the order in which Windows accesses them, select one of them and click the Arrow buttons to move it up or down.
When the public and private NICs are in the order you want, click OK.
The change in priority takes effect immediately. Restarting your computer is not necessary.
Microsoft releases operating system patches, called Service Packs, on a quarterly basis. Service Packs are collections of bug fixes and product enhancements to the basic Windows Server release. In general, apply Service Packs as soon as it is safe to do so, since they fix bugs and can improve Windows Server performance or functionality.
While Service Packs are supposed to fix bugs, they sometimes introduce new problems as well. In general, it is safest to wait a few weeks after a Service Pack is released before implementing it. This allows time for other field sites to report any problems with the SP release.
The latest Windows Server Service Packs may be downloaded as self-extracting archives from
Unless there are assurances that the Service Pack works without flaws on Windows Server, choose to create an
Uninstall directory. This enables the Service Pack to be removed and the original configuration to be restored.
Service Pack files overwrite similarly-named files in the previous Windows Server configuration. However, Service Pack files can be overwritten in turn by setup programs that copy files from the original installation media.
For example, installing a new network protocol or printer driver usually requires copying files from original Windows Server installation media. When Service Pack files are comprehensively or selectively overwritten, the Service Pack must be re-applied.
Compared to CPU and memory speeds, hard disk drives are extremely slow. Now that hard disk drives are relatively inexpensive, Oracle recommends that Windows Server use logical volumes comprised of striped physical disks. Data striping is an effective means of reducing the impact of relatively slow hard drives by distributing file I/O across a number of hard drives simultaneously.
Note:Data striping through the operating system is not permitted with Automatic Storage Management (ASM), which does its own striping. Hardware striping is allowed with ASM, but it is not necessary.
See Also:"Using Automatic Storage Management" in Oracle Database Administrator's Guide
Striping data across a number of disks is one example of a redundant array of inexpensive disks (RAID). There are several different types of RAID, also referred to as RAID levels, ranging from high performance to high reliability. The three most common RAID levels in Oracle Database installations are RAID-0, RAID-1, and RAID-5. Descriptions of each RAID level follow Table 7-2, which shows each level's read and write penalties.
|RAID Level||Read PenaltyFoot 1||Write PenaltyFoot 2|
0 (Disk Striping)
1 (Disk Mirroring)
0 + 1
5 (Distributed Data Gathering)
Footnote 1 Read penalty is ratio of I/O operations to read requests.
Footnote 2 Write penalty is ratio of I/O operations to write requests.
RAID level 0 enables high-performance, fault-intolerant disk striping. Multiple physical hard disks are aggregated into a logical whole, either by a disk controller or through the operating system (for example, Windows 2000 Server striped volumes). Data operations against the logical volume are broken down into as many chunks as there are physical drives in the array, making simultaneous use of all disks. Given identical hard disks, if one hard disk has a throughput rate of
DISKRATE operations/second, then a RAID 0 logical volume has a rate of:
(DISKRATE * [number of physical drives in array]) operations/second
The downside of RAID 0 is its lack of fault tolerance. If one disk in the logical volume fails, the whole volume fails and must be restored from a backup.
RAID level 1 enables fault tolerant disk mirroring with some chance of a performance penalty. Essentially, every write to a mirrored disk is duplicated on another drive dedicated to this purpose (the mirror drive). If the mirrored disk fails, the mirror drive is brought online in real time. After the faulted drive is replaced, the mirror configuration can be reestablished.
The read penalty for RAID level 1 is nominally 1:1, but it may benefit from split reads on some controllers. When the controller knows which mirror can be accessed fastest, for example, it can lower seek times by directing I/O operations to that disk.
RAID level 0+1 enables mirroring of an array of striped hard disks. This is a blend of RAID 0 and RAID 1, offering high-performing fault tolerance.
RAID level 5, also known as disk striping with parity, eliminates the costly requirement to mirror. In RAID 5, multiple hard disks are aggregated into a striped logical volume, similar to RAID 0, but each drive contains parity information such that any single drive failure is tolerated. With one failed drive, a RAID-5 system can allow continued access to data, although access times are greatly reduced due to on-the-fly rebuilding of bytes from parity information. RAID-5 solutions usually allow hot-swapping of faulty drives with replacements, triggering a rebuild of the failed drive's data onto the replacement from parity information.
The write penalty of 4:1 results from 2 reads and 2 writes during parity calculation.
If there are enough physical disks in Windows Server, create at least two striped volumes (in addition to a standalone hard disk or striped volume for the operating system). One striped volume can be used for sequential data access, and the other can be used for random data access.
Oracle Database redo logs and archived redo logs, for example, are written in sequential order. Because of reduced head movement, hard disks perform best when reading or writing sequential data.
Oracle Database data files, however, are usually accessed in random order. Random access in a hard disk results in significant head movement, translating to slower data access.
Unless redo logs are separated from datafiles (at physical device level), undo file I/O contention may result, increasing access times for both types of files.
Some virtual memory paging is likely even if Oracle Database is the only network application running on Windows Server, because Windows Server memory manager will attempt to move seldom-used pages to disk to free up more physical memory for hot pages.
Multiplexing the Windows Server virtual memory paging file is a good strategy to boost overall system performance. Splitting the paging file onto at least two different physical volumes (or logical volumes as long as underlying physical volumes do not overlap) provides a significant performance boost to virtual memory swapping operations.
Even though this is a good technique to increase speed of virtual memory paging, too much paging activity is still a performance hit and should be corrected by adding more RAM to the server.
Oracle recommends that total combined size of your page files be at least equal to physical RAM on your computer. Configurations where combined size is two to four times the size of physical RAM are not uncommon. Minimize paging as much as possible. But situations in which the operating system runs out of or low on paging space are to be avoided at all costs. Adequately-sized paging files spaced across physical disks spread out I/O most efficiently, because the operating system spreads paging evenly across page files.
Note:Internal read/write batch size for Windows is 4K.
Once procedures in previous sections have been applied, remember to close any unnecessary foreground applications. First, remove all applications from Startup folders of Windows Server console operators. Second, minimize the window when executing long-running scripts from a command prompt, so that Windows Server can focus on the operation and not on a flood of window repaint messages. Third, disable screen savers, which can quickly saturate the CPU. If a screen saver must be run, choose Blank Screen, which uses the least amount of processing time.