Performance Analysis
In order to perform analysis of a SAP software component the component should start without an error and there should be spare work processes available to run the analysis.
If there are no work processes available then use the program dpmon at the operating system level which will give the same output as the work process overview.
Workload Analysis (tcode ST03 or ST03N)
Menu Path
Tools=> Administration=> Monitor=> Performance=> Workload=> Analysis
Problem | Analysis |
High database time i.e. more than 40% (database time = response time – wait time) | Check using tcode STAT / STAD if buffer reload then check ST10 for Table Access Statistics if OK, then use ST05 for SQL trace analysis. |
Roll wait time more than 200 mseconds | Check using tcode ST05 for RFC trace |
GUI time more than 200 mseconds | Check for networks bottlenecks |
Load time more than 50 mseconds | Check the program buffer, maybe the program buffer too small |
Roll out or roll in time more than 20 mseconds | Check SAP memory, problem cold be with SAP extended memory or SAP roll buffer |
Programs with high CPU time i.e. >40% | Check ABAP program tcode SE30 |
Work Process Overview SM50 / SM66
Menu Path
Tools=> Administration=> Monitor=> Performance=> Exceptions / Users=> Active Users=> All processes
Work Processes with status running |
|
Direct read, Sequential read, Insert, Update, Delete or Commit | Check databse locks tcode DB01, if exclusive lock wait, check process holding the lock. |
Load Report or semaphore 1 | SAP program buffer too small |
Roll in, Roll out or semaphore 6 | Check SAP memory problems due to extended memory or roll buffer |
Work processes with status stopped |
|
Reason PRIV | Check SAP memory problems due to extended memory or roll buffer |
Reason CPIC | Test RFC destination using tcode SM59 |
Work process with status complete | Save the work process trace file and restart work process |
Operating System Monitor ST06
High CPU load i.e. idle avarage <35% |
|
SAP work process causing the high CPU load? | SM50 SM66 Check ABAP trace using tcode SE30 |
Database processes causing high CPU load? | ST04 Check expensive SQL statement |
External processes causing high CPU load? | Postpone the process to off peak hours |
File system cache >10% of RAM | Reduce file system cache |
SAP Memory Configuration Monitor ST02
SAP extended memory >80% | Enlarge the SAP extended memory |
Individual users consuming a lot of memory | Check user action |
Many buffer swaps | Enlarge the related buffer |
ztta/roll_first >1024 | ztta/roll_first=1 |
Table Access Statistics ST10
Invalidations for buffered tables | If required deactivate buffering |
Large buffer size for buffered tables | If required deactivate buffering |
Many rows affected for buffered tables | If required deactivate buffering |
Many total ABAP processor requests for non-buffered tables | If required activate buffering |
0 comments:
Post a Comment