In the workload monitor, you can display the workload in different Analysis Views, each of which displays a particular aspect of the workload. One of these aspects is the workload caused by Remote Function Calls (RFC).
By displaying the RFC profiles, you can answer the following questions:
For transaction steps with RFC, the kernel writes subrecords with additional information about the processing time, the destination, and the function module used. The parameter stat/rfcrec (default: stat/rfcrec = 5) specifies the maximum number of subrecords of each type (RFC client, RFC server, RFC client destination, and RFC server destination) that the kernel writes. If more RFCs are performed during a transaction step, only the five calls with the longest execution time are therefore logged, Which is sufficient for performance analyses. The restriction to a maximum of five records represents a compromise between the required accuracy on one side and the workload created by the performance collector on the other side. A larger value for stat/rfcrec can lead to performance problems in the collector (see also Configuring the Workload Monitor).
The RFC client and RFC server records contain data such as execution time and called function for individual RFCs. The RFC destination records contain the total of all RFC calls per destination and therefore no additional information about the called function modules.
Depending on the RFC profile selected, the output area shows the following tab pages:
Tab Page | Meaning |
---|---|
|
What workload is caused by the function modules, transactions, or users (depending on the selected RFC profile, as the RFC client or the RFC server)? |
|
Where is the RFC workload created? |
A special authorization (profile S_TOOLS_EXE) is required to display user-specific data.
On all tab pages: if you double-click a line, a new screen appears showing detailed information about the selected line.
Workload Monitor start page