Response Times: Rules of Thumb 

Definition

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

Average response time

approx. 1 second (dialog), <1 second (update)

Average CPU time

approx. 40% of average response time

Average wait time

<1% of average response time

Average load time

<10% of average response time

Average DB request time

approx. 40% of average response time

The operating system can affect these values by about 10%.

The proportion of CPU time to the complete time elapsed should not fall below approximately 5%. A low percentage might mean that there is an I/O bottleneck, or that a database overload has caused excessive wait times.

The average response time for dialog (online) transactions should not be more than 1 second, as this can unduly tax users' patience.

Database Requests

Time

Direct reads

<10 ms

Sequential reads

<40 ms

Changes

>25 ms

High Values for

Reason

DB req. (Change/Comm.)

Database or index problems?

Load time

Buffer problems?

Wait time

Not enough work processes?
Locked tasks?
Long-running transactions?

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.