克米亚sap论坛,中国最好的sap论坛,sap系统,sap培训,kemiya,克米亚,sap账号,sap ides,sap mm,sap hana,sap fico,sap pp

 找回密码
 注册
查看: 134|回复: 2

ST03N: SAP Workload Monitor

[复制链接]
kmy 发表于 2018-3-4 17:09:55 | 显示全部楼层 |阅读模式
Transaction code ST03N is used to analyze statistical data for the ABAP kernel and monitor the performance of a system. You can display the total values for all instances, and compare the performance of particular instances over a period of time. ST03N is the replacement of transaction code ST03.
The workload overview provides system administrators with various detailed information about the most important workload data, such as the CPU time, the number of database changes, the response times, and so on. You can display the workload overview for all task types (Dialog, Background, RFC, ALE, and Update), or only for one particular task type.
Workload OverviewWorkload statistic overview
Processing timeThis is equivalent to response time minus the sum of wait time, database request time, load time, roll time, and enqueue time
Hint: > 2x of CPU time.
Problem: Check on hardware side.
CPU timeA work process uses the CPU.
Hint: 40% of response time.
Problem: CPU bottleneck
Solution:
• Using transaction code ST06, go to Detail Analysis Menu -> Top CPU , check existence of Non-SAP (external) programs by sorting by CPU time. Try to run these external programs in offline hours.
• Using transaction code ST02, check for any swapping happening in all the buffers. If there is high swapping for any buffer, increase the size of the buffer.
Response timeThe time when a dialog process sends a request to a dispatcher work process, and the dialog is complete and the data is transferred to the presentation layer. The response time does not include the time for transferring the data from the SAP front end to the application server.
Hint: 1 second (dialog), <1 second (update)
Wait timeThe time when a user request sits in the dispatcher queue. It starts when user request is entered in the dispatcher queue; and ends when the request starts being processed.
Hint: < 10% of response time
Problem: Long running tasks, locked tasks, not enough work process.
Solution:
• Using transaction code SM50, look for all the configured work processes are in Waiting or Running state. If all the wotk processes are running state, then increase the number of Dialog work processes.
• Using transaction code SM66, monitor and analyze the total work processes configured in all the servers and instances.
DB callsNumber of parsed accesses to the database.
Hint: DB calls/requests good ratio is 1:10 = efficiency table buffering
DB requests/DB TimeThe time when a database request is put through to the database interface & when the database interface has delivered the result.
Hint: 40% of response time
Problem: CPU/memory bottleneck on DB server, expensive SQL statement, missing indexes, small buffer, missing statistics
Solution:
Using transaction code ST04,
• The value of database buffer quality (> 95%), if <, increase database buffer cache size.
Reads/User Calls (< 30), if >, the expensive SQL statements need to be tune.
Some of expensive SQL statement problems:
i) incorrect index access (Solution = create new index or reorganize the index)
ii) high table size (Solution = archive the old entries)
Average load & generationThe time needed to load and generate objects.
Hint: < 10% of response time, < 50ms.
Problem: Program buffer, CUA buffer, screen buffer too small.
GUI timeResponse time between the dispatcher and the GUI during the round trips (round trips are communication steps between the SAP system and the front end during a transaction step).
Hint: < 200ms.
Problem: Network between GUI & SAP GUI.
Solution:
• Using transaction code ST06, go to Detail Analysis Menu -> LAN Check by PING. If there is high Avg. time or Loss time for any presentation servers, means there are some settings need to be change for the presentation server.
• Using transaction code SE38, execute report PROFGEN_CORR_REPORT_5. From the output check if any user assigned with > 1000 user menu nodes.
Roll in timeThe time needed to roll user context information into the work process.
Hint: < 20ms.
Problem: SAP memory configuration (extended memory, roll buffer).
Roll wait timeQueue time in the roll area.
Hint: < 200ms.
Problem: Network between GUI & SAP.

本帖子中包含更多资源

您需要 登录 才可以下载或查看,没有帐号?注册

x
rvdru 发表于 2018-4-2 17:45:13 | 显示全部楼层
sap hr
小小样儿儿 发表于 2018-4-12 20:59:54 | 显示全部楼层
sap mm
您需要登录后才可以回帖 登录 | 注册

本版积分规则

QQ|克米亚sap论坛,sap账号,sap系统,sap ides,sap学习机,sap练习环境 ( 渝ICP备18002525号-5 )

GMT+8, 2018-6-22 11:15

Powered by Discuz! X3.4

© 2001-2017 Comsenz Inc.

快速回复 返回顶部 返回列表