Parameter: ztta/roll_area Short description: Roll area size Description: The value specifies the size of the roll

area in bytes. The roll area is one of several memory areas, which satisfies the user requests of user programs. For technical reasons, however, the first 250 KB or so of a user context are always stored in the roll area, further data - up to the roll area limit ztta/roll_first, - in the extended memory, up to the limit ztta/roll_extension or If extended memory is exhausted, then - again in the roll area, until the roll area is full, then - in the local process area, up to the limit abap/heap_area_dia or abap/heap_area_total or until the address space or the swap space is exhausted. Followed by termination with errors like STORAGE_PARAMETERS_WRONG_SET an error code, that points to memory bottleneck Aim: Minimum data transfer with context change; however, the increase helps to avoid problems (address space, swap space, operating system paging)

Parameter: ztta/roll_extension (Dynamic) Short description: Quota for extended memory Description: This value specifies the storage quantity in bytes that a dialog user context can allocate (extended memory). The value refers to the storage quantity that an external mode (=SAP window) allocates. When the specified value is exceeded, memory from the roll area is allocated until this is full. Local memory is then allocated. ( Data in the roll area is copied at context change When local memory within the work process is allocated, the work process is assigned to this user context and is no longer available for other user contexts (PRIV mode).) If you set the value too high, a user could cause a bottleneck in the extended memory by increasing his user context. Other smaller user contexts would bring work processes to to PRIV mode before their allowed quota is reached. Objective: Minimize no. of work processes in PRIV mode. Allocate extended memory fairly.

Parameter: ztta/roll_first Short description: Quota for early allocation in the roll area Parameter description : The value specifies the amount of memory in bytes that is allocated from the roll area, before memory is allocated from the extended memory. This means that small user contexts remain complete in the roll area. Any wastage and therefore total consumption of the extended memory can be minimized, because extended memory is assigned to users in granules of a specific length (usually 1 MB). Only effective in dialog work processes. (Windows NT) Effective in all work processes, due to identical allocation sequence (Windows NT). Aim: Optimum usage of the extended memory

Parameter: abap/heap_area_total (Dynamic) Short description: Heap memory quota Description: Defines the local process memory quota (heap, malloc) for all user contexts of an SAP application server. The quota is used to avoid allocating swap space memory.

Parameter: em/initial_size_MB Short description: Size of extended memory (Extended Memory) Description: Note the operating system dependency for Windows NT. The value specifies the initial size of the memory area, which is managed by SAP Memory Management as extended memory. This satisfies the storage requests of the interactive users' programs. This type of memory can be very quickly assigned to changing work processes through 'mapping'. This enables rapid context change. Aim: Ideally this pool should be large enough to contain the total of all user contexts, so that the context change of all users can flow as quickly as possible.

You can limit the maximum consumption of a user by using the parameter ztta/roll_extension. This can prevent the extended memory being used up by users. If the extended memory is exhausted, additional memory requests are satisifed from the roll area and then from from the local address area of a work process (heap, malloc). The data in the roll area must be copied during context change, while the data in the local memory of the work process lead to exclusive assignment of entire work process (PRIV mode) Dependencies: The value must be smaller than/equal to (em/blocksize_KB * 16) and an exact multiple of (em/blocksize_KB / 1024). Windows NT: =========== For Windows NT the extended memory has been dynamically increased. This means that if the current extended memory is not sufficient, it is extended by the size [PHYS_MEMSIZE / 2] The standard value is identical to PHYS_MEMSIZE. As a result of this mechanism, it is no longer necessary to maintain this profile parameter manually. Example: Application server with 1 GB main memory. PHYS_MEMSIZE is not maintained and its standard value is the size of the main memory. This means that the initial size of the extended memory = 1 GB. If the size of the memory is insufficient, the extended memory is increased in 500 MB steps, until the maximum size em/max_size_MB (default: 20 GB) is reached or until there is no more address space in the NT page file. Central instance with 1 GB main memory. The database uses 400 MB and the SAP instance 600 MB of main memory. The value for PHYS_MEMSIZE is set to 600 in the instance profile. This means that the extended memory has an initial size of 600 MB, and if necessary extends itself in steps of 300 MB.