An SAP Workload Analysis Guideline…
Time
|
Guideline Value
|
Problem Indicated
|
Seeing
|
Dispatcher wait time
(Wait time)
|
<10% of response time
<50ms
|
General performance problem with many
possible causes
|
|
Load time
(Load + Gen time)
|
<50ms
|
Program buffer too small or CPU
bottleneck
|
C2 – Monitoring Hardware, DB, SAP
Basis
|
Roll-in time, Roll-out time
|
<20ms
|
SAP Roll buffer or SAP extended memory
too small or CPU bottleneck
|
C2 – Monitoring Hardware, DB, SAP
Basis
C8 – Memory Management
|
Roll wait time
|
<200ms
|
Problem with frontend communication
(together with higher GUI time), or with communication with external
component
|
C4 – ABAP and Java Programs
Performance
C6 – Interface
C7 – SAP GUI and Internet Connect
|
GUI time
|
<200ms
|
Problem with frontend communication
(together with higher Roll wait time)
|
C4 – ABAP and Java Programs Performance
C6 – Interface
C7 – SAP GUI and Internet Connect
|
Enqueue time
|
<5ms
|
Problem with Enqueue or Network
problems
|
C4 – ABAP and Java Programs Performance
|
Processing time
CPU time
|
Processing time
<2 x CPU time
|
CPU bottleneck or communication problems
|
C5 – Workload Distribution
|
Database time
(DB Request time)
|
<40% of response time minus
Dispatcher wait time;
Guideline value: 200ms -600ms
|
Database problem, Network problem, CPU
bottleneck
|
C3 – Workload Analysis
C4 – ABAP and Java Programs
Performance
C11 – Optimizing SQL Statements
|
Time per DB request
|
<5ms
|
Database problem
|
C3 – Workload Analysis
C4 – ABAP and Java Programs
Performance
C11 – Optimizing SQL Statements
|
Direct reads
|
<2ms
|
Database problem
|
C3 – Workload Analysis
C4 – ABAP and Java Programs
Performance
C11 – Optimizing SQL Statements
|
Sequential reads
|
<10ms
|
Database problem
|
C3 – Workload Analysis
C4 – ABAP and Java Programs
Performance
C11 – Optimizing SQL Statements
|
Changes and Commits
|
<25ms
|
Database problem
|
C3 – Workload Analysis
C4 – ABAP and Java Programs
Performance
C11 – Optimizing SQL Statements
|
Không có nhận xét nào:
Đăng nhận xét