7/23/2019 1387644 - Using 64 KB Virtual Memory Pages Sizes on AIX

http://slidepdf.com/reader/full/1387644-using-64-kb-virtual-memory-pages-sizes-on-aix 1/2

7/23/2019 1387644 - Using 64 KB Virtual Memory Pages Sizes on AIX

http://slidepdf.com/reader/full/1387644-using-64-kb-virtual-memory-pages-sizes-on-aix 2/2

 

1. 64K pages are currently not supported in combination with Active Memory Sharing (AMS).

2. 64K pages are currently not recommended in combination with Active Memory Expansion (AME). Thedefault system setup with AME are 4K pages and should not be changed manually.

MONITORING: 

Determining supported page sizes on a system:To determine the page sizes supported by AIX running on a particular system, the pagesize commandwith the options -a (all page sizes) and -f (format) can be used.

Determining a process's page sizes:The ps command with the -Z option can be used to monitor the page sizes being used for a process.

Monitoring page size usage:

By default, the vmstat command displays memory statistics that are cumulative across all page sizes.To display memory statistics for a specific page size, the following vmstat options can be used:-p  Displays global vmstat information along with a break-down of statistics per page size.-P Displays per page size statistics

Page size usage across the operating system:The svmon command can be used to display page size usage across the system. Most svmon options havebeen enhanced to provide a per page size break-down of statistics. For example, to display globalstatistics about each page size, the -G option can be used.

SAP Transaction OS07 / OS07n:The transaction OS07/OS07n and the underlying saposcol was extended to show paging rate per pagesize.

FURTHER CONSIDERATIONS: 

Note for SAP ABAP stack:

Make sure the instance profile parameter ES/TABLE is set to SHM_SEGS (and in versions before 7.10the parameter SHM_SEGS_VERSION=2) according to SAP Note 856848.

Note for SAP Java stack:If you want to enable the Java heap for 64K pages you need to set a parameter for IBM JVM. This hasto be -Xlp64k. In case of SAP JVM 64K pages are supported beginning with SAP JVM 5 Patch Level 57and SAP JVM 6 Patch Level 11. For SAP JVM there is no need to set a special parameter.

Note for Oracle databases:64k pages are supported from Oracle 10.2.0.4 on i.e 10.2.0.4, 10.2.0.5, 11.2.x (x>=0)

Validity

This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes 

This document is referenced by:SAP Notes (6) 

1775923 liveCache on AIX 

1024539 Recommended Settings for NW04 >= SP14, NW 7.0 >= SP6 on AIX 

1008311 Recommended Settings for NW 7.0 >= SR2 for the AIX JVM (J9) 

1775923 liveCache on AIX 

2098347 IBM i: Upgrade to SAP_BASIS 7.40 or SAP NetWeaver kernel 7.4x 

1024539 Recommended Settings for NW04 >= SP14, NW 7.0 >= SP6 on AIX 

1972803 SAP on AIX: Recommendations 

1008311 Recommended Settings for NW 7.0 >= SR2 for the AIX JVM (J9) 

2031037 Upgrade to SAP_BASIS 740 or NetWeaver Kernel 74x