| What To Monitor In ST03
What are the things we have to monitor in ST03 (Workload Analysis Monitor) and what should be the range (ie time in ms)? System statistics are written to the R/3 kernel and can be displayed using the workload monitor (Transaction ST03N). They provide system administrators with varied and detailed information on CPU time, numbers of database changes, roll out times and so on. The table below defines the most important workload statistics:
During a dialog step, the CPU of the application server is used for processing (loading, generating, database request processing, ABAP processing and so on). The CPU time is determined by the operating system. At the end of a transaction step, the R/3 work process queries the CPU time from the operating system. The CPU time is therefore not an additive component of the response time, unlike the wait, roll-in, load and database time. Average response time - The average response time of a dialog step is the average time measured from the time a dialog sends a request to the dispatcher work process through the processing of the dialog up to the time the dialog is completed and the data is passed to the presentation layer. The response time between the SAP GUI and the dispatcher is not included in this value. The response time does NOT include the time taken to transfer data from the R/3 frontend to the application server. For networks with low performance, this can create a highly subjective response time. The transfer time is contained in the GUI network time. Response time is usually split into wait time plus dispatch
time. The SAP response time is composed of the following components:
The CPU time is not an additive component of the response time, but the sum of the CPU time that is used by the individual components. The CPU time therefore provides additional, independent information on the response time. Average wait time - The time an unprocessed dialog step waits in the dispatcher queue for a free work process. Under normal conditions, the dispatcher work process should pass a dialog step to the application process immediately after receiving the request from the dialog step. Under these conditions, the average wait time would be a few milliseconds. A heavy load on the application server or on the entire system causes queues at the dispatcher queue. Average load time - The time needed to load and generate objects such as ABAP source code and screen information from the database. Database calls - The number of parsed requests sent to the database. Database requests - The number of logical ABAP requests for data in the database. These requests are passed through the R/3 database interface and parsed into individual database calls. The proportion of database calls to database requests is important. If access to information in a table is buffered in the SAP buffers, database calls to the database server are not required. Therefore, the ratio of calls/requests gives an overall indication of the efficiency of table buffering. A good ratio would be 1:10. GUI time - The GUI time is measured in the work process
and is the response time between the dispatcher and the GUI.
Roll wait time - Queue time in the roll area. When synchronous RFCs are called, the work process executes a roll out and may have to wait for the end of the RFC in the roll area, even if the dialog step is not yet completed. In the roll area, RFC server programs can also wait for other RFCs sent to them. Average time per logical DB call - Average response time for all commands sent to the database system (in milliseconds). The time depends on the CPU capacity of the database server, network, buffering, and on the input/output capabilities of the database server. Access times for buffered tables are many magnitudes faster and are not considered in the measurement. The following times give you an overview of optimal response times in your SAP System. Use the workload monitor to display the current workload statistics in your system. Performance Data Time
Database Requests Time
High Values for Reason
The times for direct reads and changes should not exceed 10 milliseconds in a healthy database system. The sequential reads time should not exceed 30-40 milliseconds. You can use the workload monitor (Transaction ST03N) to analyze the workload statistics for each task type (for example for background processing, dialog processing, update processing, ALE, and RFC) for the application servers in your SAP System. You can use the workload monitor to display and compare the time profiles. A time profile displays the workload for a specific task type over a specific period of time. You can display the workload of the instances that are configured in your SAP System, not just the instance that you have logged on to. You can also switch easily between the information for these instances. You can display and analyze the time profile for one individual
task type, or for all task types. You can display the workload for the
following parameters:
You can use the workload monitor to display the number
of users working on an application server. You can display the number of
dialog steps that each user has executed, and check that application server
response times are acceptable.
SAP Basis Reference Books:
Back to Basis Menu:
Return to :-
(c) www.gotothings.com All material on this site is Copyright.
|