The time taken by the user request to reach the dispatcher. You need to understand here is that the user interact on presentation layer and dispatcher is on application layer so GUI time is this time If GUI time > 200ms then consider the following-: GUI Issues Network Issues [bandwidth] Desktop Issues Network congestion

The amount of time user request waits in the queue for allocating a work process. Once you have reached the dispatcher you should get a work process to actually execute the operation , dispatcher is just a router to understand this is just like the a hotel reception which guides you to the room which is available Wait time>50ms or 10% of the response time. Work processes are not sufficient [Increase based on application monitor and available resources] Work processes are processing expensive programs or in the PRIV mode [restrict the processes that are going into PRIV mode by using parameter “rdisp/wppriv_max_no and rdisp/max_priv_time”] Configure the memory parameters

The time taken by the process to reach the database and get the response from database. DATABASE TIME > 40% EXECUTION TIME Consider database buffers are not sufficient [increase buffers] Consider resources bottle on the database [check memory and CPU utilization] DB indexing issues [check missing indexes in DB02] DB statistics are outdated [schedule DB stats job in DB13] Db has to be re-organized [Reorganize the DB using Brtools] Expensive SQL statements [ST05]

PROCESSING TIME-: The time taken to process the user request. Processing time >2 * CPU time [Twice the time of CPU] Then consider processing of screens, ABAP and SQL is expensive and tune the ABAP programs, SQL Screens and SQL Statements. LOAD AND GENERATION TIME-: The time taken to load and generation the response from the buffer or from the process after fetching the content from database. LOAD AND GENERATION TIME > 200ms Processing the response from buffers or load and generating the response from database is expensive MONITOR ST02. RFC/CPIC Time-: It should be as minimal as possible, it is always an overload. If it is periodical then check the interface/gateway/RFC connections or the target system resources. ENQUEUE TIME-: The time taken by the dialog process to communicate with enque process and obtain a lock on that record. It is also the time taken by the dialog process to communicate with message server and the message with enque server process when the dialog process is coming from other dialog instances. ENQUEUE TIME > 5ms on CENTRAL INSTANCE > 100ms for request that is coming from dialog instances. Increase the enque work processes if required. Increase the size of enque table if required, when the enque lock table overflows.

CPU TIME-: The amount of time the work process utilizes the CPU resources while processing the request. CPU Time >40% [response time – wait time = execution time] Identify the Expensive ABAP programs in ST03n. If required execute SE30/ST30 for runtime analysis of ABAP programs.

The time taken by the work process to roll-in the user context into its task handler. Roll-In time >50ms

The time taken by the work process to roll-out the user information into user context before sending the response to the user. Roll-Out time >50ms Reduce the user authorization, commonly used attributes and parameters.