When is there a CPU or Main Memory Bottleneck?

The unused CPU capacity (idle) should normally average at least 20% per hour. This enables the system to accommodate temporary workload peaks. A reading of  35% idle CPU capacity is even better. For the paging rate, the following guideline values apply:

->For computers that contain a database, an SAP J2EE Engine, or TREX, only very minor paging rates should occur; that is, they should be dimensioned in such a way that the available main memory corresponds to the configured memory areas.

->For computers that only include ABAP instances, you can tolerate moderate paging rates of up to 20% of the physical main memory per hour.

For instance,Main memory bottleneck, As a rule of thumb, there should be approximately 50% more virtual memory than physical memory.

Causes of Hardware Bottlenecks

->Incorrect load distribution (It is extremely important that the database server has enough resources.)

->CPU load of individual programs (In the operating system monitor (Transaction ST06), select the analysis SNAPSHOT • TOP CPU PROCESSES.)

* You can identify the following processes:

--> dw_<instance>:SAP work process of the ABAP Server on a UNIX operating system. On Windows operating systems, the name is “disp+work.”

-->jstart ...                :Server process of SAP Java instance.

-->TREX ...               :TREX process. The server type is indicated in the process name, for instance, index server, preprocessor, and so on.

-->icman ...              :Process of the Internet Communication Manager (ICM).

-->saposcol ...         :Auxiliary program, which collects the data for the operating system monitor