Analyzing the SAP System

Having discussed the analysis of the hardware and operating system as well as of the Oracle database, we now turn to the analysis of the SAP system, or more precisely, the individual instances of the SAP system. The criteria that are relevant for the performance of an SAP instance can be divided into two main categories:n.

Memory of an SAP Instance

the importance of the SAP memory configuration (not of the SAP buffer) has decreased due to the technological progress in recent years. Above all, the enhancement of the main memory capacities, which also involves changing to the 64-bit technology, means the main memory is usually no longer the limiting factor of an SAP instance.

Roll memory

TEvery work process contains a roll memory area that is located in the local process memory. It stores the initial user context that is swapped to the roll buffer when the process is changed (SAP process multiplexing). The roll buffer itself (don’t confuse it with the roll memory) is also referred to as the roll area and, like the extended memory, is a shared memory area. From SAP R/3 3.0 onward, the roll memory plays only a minor role, because the main part of the user context is directly stored in the extended memory and the access change is performed through the pointer.

Extended memory

This shared memory is used by all work processes and is the most important memory area of an SAP instance. It contains all user contexts of the users that are logged in to the instance, with the exception of the small initial context that is being copied between roll memory and roll buffer

Heap memory

This memory area is a local memory that belongs to one work process. The work process type determines when the heap memory is used. It is used for dialog processes when the extended memory or at least the part of the extended memory that may be used by a single work process is entirely utilized. For nondialog processes, the local heap memory is used immediately after the roll memory, because here no process multiplexing is performed, and the extended memory is therefore reserved for the dialog processes.


What We Do

SAP Buffers

The SAP system also uses the buffers concept to access data quickly that is often reused. This concept is equivalent to that of buffers in the database. illustrates the two-level buffer architecture and the relationships between the buffers. Note that, of course, each instance of an SAP system has its own buffers.The combination of database and SAP buffers involves a performance-relevant feature. Let’s take a data record for currency conversion as an example. This data record is loaded from the Oracle database if a relevant transaction

Sap Hana

SAP HANA is an in-memory, column-oriented, relational database management system developed and marketed by SAP SE. Its primary function as database server is to store and retrieve data as requested by the applications. In addition, it performs advanced analytics (predictive analytics, spatial data processing, text analytics, text search, streaming analytics, graph data processing) and includes ETL capabilities as well as an application server.


With Oracle Database 11g Release 2, SAP customers benefit from innovative features such as self-tuning database components, sophisticated partitioning schemes, and data compression that enables high performance, greater scalability, and optimal hardware resource allocation for enterprise applications. Oracle Database 11g Release 2 Enterprise Edition comes with a wide range of options to extend the world’s #1 database to help fuel business growth and meet your users' performance, security, and availability service-level expectations.