Powered By

Free XML Skins for Blogger

Powered by Blogger

Friday, January 2, 2009

Determining Swap Space SAP Memory Management Requirements

The program sappfpar lets you check the minimum and maximum (worst case) swap space requirements for an R/3 application server. It also checks the shared memory requirements and if the parameters em/initial_size_MB and abap/heap_area_total are correctly set. Proceed as follows:

  1. To check the instance profile for the R/3 application server, start the program sappfpar from the UNIX command line.
  2. /usr/sap//SYS/exe/run/sappfpar check pf=/usr/sap//SYS/profile/ nr= name= | more

  3. The program generates a list. Note the total value for the shared memory in the field Shared memory under Memory requirements estimated. This value corresponds to the size of the shared memory required for this profile, and must be calculated into the shared memory requirements for the new Memory Management.
  4. At the end of the list, the program specifies the minimum swap space requirements, the maximum heap memory requirements and the swap space requirements in a worst case scenario:

Total, minimum requirement.....: 169.5 MB (shared memory requirement)
Process local heaps, worst case: 762.9 MB
(is set with abap/heap_area_total )
Total, worst case requirements: 962.5 MB

Ensure that there is more swap space available than what is specified in the worst case scenario. (This is because non-R/3 processes also require swap space.)

The following minimum values for the swap space are valid in each case for host systems on which application servers run:

  • 3 GB (OSF/1 systems)
  • 2 GB (all other systems)

For optimum performance, 3-6 GB swap space is recommended.

The additional swap space requirements may be higher for application servers where heavy online operations and background jobs with large data volumes alternate (day/night operation).

Expanding the swap space may require additional disk space in certain circumstances. This is highly recommended due to inexpensive hardware prices.

Independent of the swap space size, you should monitor the swap space to avoid bottlenecks.

No comments:

Archives