Thetmpfs file system was introduced with the Linux kernel 2.4. This file system supports POSIX shm_* calls and therefore makes it possible to use the new SAP memory management function.
The following technical prerequisites have to be fulfilled:
If you do not specify a fixed size, the Linux kernel uses half the size of the main memory by default. This is usually too small for operation an SAP system.
An entry in the file
tmpfs /dev/shm tmpfs size=2G 0 0
Improvements on Linux Kernel 2.4
The following improvements on the Linux kernel 2.4 enable the use of the new memory management function:
Configuring SAP Instances
How you configure an SAP instance depends on what SAP release you have.
See the sectionOld or New Memory Management? for information on how to activate the new memory management function.
Old Memory Management
When using the old memory management function, note the following:
New Memory Management Function
The new memory management function allows you to work with much larger user contexts. One user can now use 1.2 GB of EM, whereas before this was the limit for all user contexts.
Only the main memory and the swap space limit the size of the EM backing store in thetmpfs. You should of course make sure that excessive swapping does not occur, especially if you are working with large machines.
The large maximum size of a user context in the EM (parameterem/address_space_MB) means that high heap quotas should not be required.
On very large machines (8 GB and more), it may make sense to run two SAP instances on the new implementation. That way, you can assign each instance to one SAP module (such as FI or HR), thus optimizing your SAP buffers.
SAP note 386605 describes in detail how to use the new memory management function, the prerequisites for using the new memory management function, and sample configurations. The note will be updated sooner than this documentation in the case of any changes being made.