未来已来

SAP Monitor Counters

上一篇 / 下一篇  2008-08-27 18:50:43 / 个人分类:性能测试

 

Av. DB Req. Time

 

A considerable amount of the dispatched time of a dialog is spent reading or changing the data of the respective database. The time for processing logical data base requests is stored in this field.

 

Various factors affect the logical DB access time. Read requests can either be sent to the data base buffers or to the fast local SAP buffers. The efficiency of the buffers, the required number of requests as well as a large number of database change requests affects the total access time.

 

The DB access time also takes into account the data base server CPU performance as well as network transfer times.

 

 

Av. Enqueue Time

 

No information for this from the SAP server.

 

 

Av. Response Time

 

The response time of a dialog step comprises the time for the dialog request to the dispatcher work process, dialog processing, and completion of the dialog in the dispatcher and transfer of data to the presentation medium.

 

Please note that the time required for processing the "Presentation -- Dispatcher -- Presentation" communication step is not taken into account here. In long-distance or low-performance networks, this step can lead to considerably longer 'subjective' response times.

 

Response time is usually divided into waiting time and dispatched time.

 

The SAP response time consists of the following components:

 

Response time            =    Waiting time + "Dispatched" time

 

Dispatched time =    Generation times at run-time

 

+ Loading time for programs, screens, and CUA interfaces

 

+ Roll times for rolling the working data in and out

 

+ ABAP / 4 processing time

 

+ DB database interface time – that required at the SAP interface from ABAP / 4 to the database and SAP buffer

 

+ Enqueue time for SAP logical lock processes

 

The displayed CPU time is also a component of the response time, but is not broken down further. Thus the CPU time is a further independent component of the response time.

 

 

Av. RFC + CPIC Time

 

There is no information for this in the ST03 transaction.

 

 

Av. Roll I + w time

 

No documentation available.

 

 

Average Bytes Req.

 

A number of interfaces provide the SAP application with data for various purposes. The data requests are differentiated according to the following interfaces/data types:

 

Screen sources

Screen load

ABAP  sources

ABAP  load

CUA   sources

CUA   load

Nametab interface

CPIC   interface

DDIC   interface

DSQL   interface (user data from data base)

 

 

Average CPU Time

 

During execution of a dialog step, the application server CPU is used for processing (loading, generating, processing DB requests, processing ABAP/IV...). The CPU time represents a large part of the dispatched time, which is response time without waiting time.

 

 

Average Load Time

 

Loading and generating time comprises the time required to load objects such as source codes, CUA interface and screen information from the database and to generate them, if required.

 

 

Average Wait Time

 

Under normal circumstances, a dialog step should be transferred from the dispatcher work process to the application process immediately after its request. If this is executed, the average waiting time in the dispatcher process is several milliseconds. In high-load situations in the application server or the system, waiting times in the dispatcher queue and considerable response times (> 1s) can occur.

 

 

CPU Time

 

During execution of a dialog step, the application server CPU is used for processing (loading, generating, processing DB requests, processing ABAP/IV). The CPU time represents a considerable amount of dispatched time, and thus of response time without waiting time.

 

 

Database Calls

 

Total of the modification (INSERTs, UPDATEs, DELETEs) and delete commands to the database system.

 

 

Database Requests

 

The number of logical data base requests corresponds to the number of requests transferred by the ABAP/IV processor to the interface. Please note the difference between logical requests and calls transferred to the database by the interface.

 

 

DB Calls:Changes

 

Number of logical table change requests. Change requests are UPDATE, DELETE or INSERT one or more lines of a table.

 

 

DB Calls:Direct Reads

 

Number of logical "direct read" data base requests, e.g. ABAP/IV "SELECT SINGLE ..." statements.

 

The local SAP buffer can in certain cases, process the request. If not, it must be transferred to the database.

 

 

DB Calls:Sequential Reads

 

Number of logical "sequential read" data base requests, e.g. ABAP/IV SELECT * FROM ... statements. This request can, in certain cases, be processed by the local SAP buffer (100% buffer for tables) and if not, is transferred to the database.

 

 

Dialog Steps

 
The number of counted/usable dialog steps or statistics records. A dialog step is logged as a statistics record in the SAP workload statistics if it is one of the following types: DIALOG, UPDATE, BATCH, SPOOL, ENQUEUE.

 

 

Roll wait time

 

Response time of dialog steps which are not ended, despite roll out (such as some RFCs, for example), and which wait a certain time in the roll area until the dialog step is continued. This time is called the waiting time in the roll area.

 

 

Roll-in time

 

Time used in dialog steps for roll in/out operations.

 

In roll-in operations, user-specific data is transferred (rolled in) to the process work area from the shared memory roll buffer or roll file. In roll-out operations, data is transferred (rolled out) to the roll buffer or roll file.

 

 

Roll-ins

 

Number of roll-in operations.

 

In roll-in operations, user-specific data is transferred (rolled in) to the process work area from the shared memory roll buffer or roll file. In roll-out operations, data is transferred (rolled out) to the roll buffer or roll file.

 

 

Roll-out time

 

Time used in dialog steps for roll in/out operations.

 

In roll-in operations, user-specific data is transferred (rolled in) to the process work area from the shared memory roll buffer or roll file. In roll-out operations, data is transferred (rolled out) to the roll buffer or roll file.

 

 

Roll-outs

 

Number of roll-out operations.

 

In roll-in operations, user-specific data is transferred (rolled in) to process work area from the shared memory roll buffer or roll file. In roll-out operations, data is transferred (rolled out) to the roll buffer or roll file.

 

 

Time per DB Request

 

Average response time of all commands to the database system in milliseconds.

 

As access times to buffered tables are shorter, they are not included in the runtime measurement.

 

 

Time per Req.:   Changes and commits

 

Mean time per dialog step for logical "UPDATE", "DELETE" or "INSERT" database requests.

 

The time requirements for 'Commit work' requests to the database are also taken into account here.

 

 

Time per Req.:   Direct Reads

 

Mean time per dialog step for a logical "direct read" data base request, e.g. the ABAP/IV "SELECT SINGLE ..." statement.

 

 

Time per Req.:   Sequential Reads

 

Mean time per dialog step for a logical "sequential read" data base request, e.g. the ABAP/IV "SELECT * FROM ..." statement.

 


TAG: 性能测试

 

评分:0

我来说两句

显示全部

:loveliness: :handshake :victory: :funk: :time: :kiss: :call: :hug: :lol :'( :Q :L ;P :$ :P :o :@ :D :( :)

Open Toolbar