|Skip Navigation Links|
|Exit Print View|
|System Administration Guide: Devices and File Systems Oracle Solaris 10 8/11 Information Library|
The most important factors in determining swap space size are the requirements of the system's software applications. For example, large applications such as computer-aided design simulators, database management products, transaction monitors, and geologic analysis systems can consume as much as 200–1000 MB of swap space.
Consult your application vendors for swap space requirements for their applications.
If you are unable to determine swap space requirements from your application vendors, use the following general guidelines based on your system type to allocate swap space.
Note - Crash dump content is compressed so the dump device does not have to be the same size as physical memory. By default, the dump content value is set to kernel pages. However, if the dump content value is set to dump all memory pages, then consider increasing the dump size to half the size of physical memory or more.
Table 19-1 Swap and Dump Volume Sizes for ZFS File Systems
Note - A busy system with many active ZFS file systems might use 1/2 to 3/4 the size of physical memory for the size of the dump device.
On a system with a ZFS root file system, if you attempt to designate a dump device that is too small to hold a system crash system with the dumpadm -d command, you will see a message similar to the following:
dumpadm: dump device /dev/zvol/dsk/rpool/dump is too small to hold a system dump dump size 43467329536 bytes, device size 42949672960 bytes
Table 19-2 Swap and Dump Device Sizes for UFS File Systems
In addition to preceding general guidelines, consider allocating swap space or disk space for a UFS-based system for the following:
A dedicated dump device.
The /var/crash directory. The default system crash dump content is kernel memory pages only and the dump is compressed before it is written. Consider sizing this directory to the size of the dump device unless you attend to keep several system crash dumps.
Determine whether large applications (such as compilers) will be using the /tmp directory. Then, allocate additional swap space to be used by TMPFS. For information about TMPFS, see Swap Space and the TMPFS File System.
During an initial installation of a ZFS root file system or an Oracle Solaris Live Upgrade migration of a UFS file system to a ZFS root file system, a swap area is automatically created on a ZFS volume in the ZFS root pool. In the case of a UFS to ZFS migration by using Oracle Solaris Live Upgrade, a swap volume is created based on the sizes of existing swap areas.
In a ZFS root pool, swap devices are not pre-allocated to fixed-size slices, so it is fairly easy to modify the swap size later.
After you assess the swap requirements of your applications, you can use the default swap size or adjust the swap volume size during an initial installation or after the installation, if necessary.
During an initial installation, the default dump volume size is calculated by the kernel based on dumpadm information and the size of physical memory.
In a ZFS environment, file systems consume space from the pool so the /var/crash directory consumes what it needs depending on how many crash dumps are saved.