
A few steps need to be check to identify the slowness of SAP system. Login to the affected system and check the following transaction codes:
1. SM66: Global Work Process Overview
• Monitor the work process load on all active instances across the system
• Identify locks in the database (lock waits).
2. SM50: Process Overview
• Monitor work process load on specific instance.
• Identify work process running/waiting status – are Dialog work process free or all occupied
3. SM37: Background & Batch Jobs
• Check for long running jobs
4. SM12: Lock Concept
• Check for long held locks
5. SM04: User List
• Determine current users online.
6. ST06: OS Performance Analysis
• Operating system performance: memory, CPU, Top CPU, hard disk & network utilization
• Check for jobs that consume more than 60% from the resource in Top CPU
• Check for network collision between the server and end user.
• On OS level, if UNIX / Linux, check command top command to verify utilization usage or task manager on windows.
7. ST02: Tune Memory
• Look on buffered memory. Identify how many red entries found.
8. ST03N: Workload Monitor
• Determine the response time of transaction code, database process
9. ST04: DB Performance Analysis
Transaction code ST04 is used to shows detail of the database behave & usage, both history and current time.
• Data buffer cache size & quality must be above 95% [meaning less physical read from disk]
• User/Recursive Call > 2 [Recursive call will get more over time]
• Read/User Call < 30 [> 30 means expensive SQL statements]
• Time/User Call < 15ms
• Busy time & CPU time ratio 60:40 ratio. Higher ratio means tuning required
• Sort sections. It should be less than 0.1% of total sorts.
• Shared pool statistics. DD (data dictionary) cache quality should be more than 99%, similarly the SQL area get ratio.
10. SMGW: SAP Gateway Monitor
• Check gateway number not reaching 100 of usage.
11. Backup
Verify that backups are running or not. If backups are running, it may affected the SAP system performance. Backup should be running out of business working hours.
How about st22 to check if there’s too many abap dumps occur
what does SMGW screenshot is telling?