Page History
...
The following table describes the information displayed in the Steps table, when the Steps view is selected.
Table 4-9 Steps table
Column Description
...
| Column | Description |
|---|---|
 | Click on the Details icon to open a dialog box that enables you to view additional details for the selected step. |
...
| Time | Displays the time unit the transaction was run in. |
| Transaction |
...
| Displays the name of the transaction that was run. |
...
| User | Indicates the user that initiated the transaction. |
| Client |
...
| Displays the user's client. |
| Program |
...
| Displays the name of the program that was run. |
...
| Screen | Displays the screen that was run. |
| GUI |
...
| Program | Displays the GUI program that was run. |
| Response |
...
| Time | Displays the total activity time. The response time is the sum of the client time, the queue time, the application time, and the database time. |
| Backend Response |
...
| Team | Displays the total Back End activity time. The Backend Response Time is the sum of the queue time, the application time, and the database time. |
...
| Steps | Number of steps running for the transaction, user, client, program, screen and GUI program, during the specified time slice. |
| Client |
...
| Time | Displays the total client time of the activity. The client time is the time the activity spent going to or from the SAP application server plus the time it spent in the client machine. |
| Queue |
...
| Time | Displays the total queue time of the activity. The queue time is the time the activity spent in the SAP application server waiting for a work process to process it. |
| Application |
...
| Time | Displays the total application time of the activity. The application time is the time the activity spent being processed by the SAP application server. |
| DB |
...
| Time | Displays the total database time of the activity. The database time is the time the activity spent in the SAP database. |
See “Copying data to the clipboard” on page 21, “Determining which table columns to display” on page 21, “Viewing additional step details” on page 41, and “About the counters in Precise for SAP” on page 22.
Viewing additional step details
Clicking on the Details icon in the Steps table opens the Step Details dialog box that displays additional performance statistics about the selected step.
...
Table 4-10 Additional step details
Additional performance statistics Description
...
| Additional Performance Statistics | Description |
|---|---|
| Details |
|
...
|
...
|
...
|
...
|
...
|
...
|
Additional performance statistics Description
...
| Response Time |
|
...
|
...
|
...
|
| Client |
...
| Time |
|
...
|
...
|
| Application |
...
| Time |
|
...
|
...
|
...
|
| DB |
...
| Time |
|
...
|
...
|
| DB |
...
| Operations |
|
...
|
...
|
| DB Requests Average |
...
| Time |
|
...
|
...
|
| Application Server Buffers |
...
| Ratio |
|
...
| |
| Memory Resources |
|
...
|
...
|
Displaying business-oriented entities in the Main Area
The information displayed in the Main area displays the entity’s important counters and performance information in the following views:Overview Displays
- Overview. Displays the entity’s most important counters, in addition to the SLA compliance pie chart and a pie chart representing the various components of response time. The response time components include:
- Client time
...
- Queue time
...
- Application time
...
- Database time
- Performance.
...
- Displays the average response time for the entity over the selected time period, broken down into the following components:
- Client time
...
- Queue time
...
- Application time
...
- Database time
- Load.
...
- Displays the number of transactions and steps executed by the selected entity and its summed response time broken down into its components.
- SLA
...
- compliance. Displays SLA compliance over the selected time period.
...
- Scalability. Displays the steps and the average response time over the selected time period.
See “About the counters in Precise for SAP” on page 22, “About the entities you can examine in the Activity tab” on page 36, and “Business-oriented entities” on page 36.
RFC Entities in the Main Area
The information displayed in the Main area displays the entity’s important counters and performance information in the following views:Overview Displays
- Overview. Displays the entity’s most important counters, in addition to the SLA compliance graph and a graph representing the various components of the call time. The call time components include:
- Wait time
...
- Exe time
- Performance.
...
- Displays the average call time for the entity, broken down into the following components:
- Wait time
...
- Exe time
...
- DB time (showing high, medium, or low)
...
- SLA
...
- compliance. Displays SLA compliance graph over the selected time period.
...
- Scalability. Displays the number of calls executed over the selected time period and the average call time, over time for the selected entity. The average call times are broken down into average Exe times and average Wait times.
| Anchor | ||||
|---|---|---|---|---|
|
You can identify a performance problem by doing one or more of the following:
- Examining resource consumption of the entire system
- Identifying resource consumers
- Examining resource consumption over time
- Examining scalability
| Anchor | ||||
|---|---|---|---|---|
|
When performing a tuning audit it is very important to analyze and understand the performance behavior of your SAP system. You may have already drilled down to analyze the performance of a single organization, locale or application. However, examining the entire SAP system’s behavior can alert you to the health of your system. This will help you answer questions such as: "A specific transaction suffers from long database times, but is the entire SAP system suffering from long database time?"
Examining the entire SAP system can provide a quick overview of the dominant resources consumed. Choose Overview from the View controls in the Main area to view which are the dominant resources consumed by your system.
| Anchor | ||||
|---|---|---|---|---|
|
Precise for SAP enables you to drill down to application components (such as Organizations, Locale, Users, Transactions, etc.) to determine which components are consuming the most resources. This is accomplished by clicking on an component in the Association area. This process is iterative and you may continue to drill down until you discover the component that you want to tune.
...
- You will want to identify heavy resource consumers. During the tuning process, you drill down to determine which are the most resource consuming components. Tuning a transaction that is consuming most of the resources, will free them for other entities. The tuning process is an iterative process. You will continue to list all components, examine their resource consumption and focus in on several of them, until you have completed the tuning process.
- When you try to analyze user experience you need to isolate one user’s activity from the other. to achieve this you can focus in on a single user.
...
| Info |
|---|
When trying to determine which application component to drill down to, take into account not only the total Response Time of the application, but also its number of Transactions and the average Response Time. If you don’t take these elements into account you may concentrate your efforts on the wrong transaction. For example, you may try to tune a transaction that runs once a year, consuming 20 hours, instead of tuning a transaction that consumes 2 seconds but runs every time a user logs on to the system. |
| Anchor | ||||
|---|---|---|---|---|
|
When you analyze and tune the performance of an application component (such as, Organization, Locale and Application) it is important to take into consideration its performance over time. Precise for SAP allows you easily view the component’s performance over a selected time period.
...
- When analyzing a performance problem you want to determine if it is a random problem.
- You are looking for a pattern. For example, does the long client time always happen on Tuesday at around 10 AM?
- You want to determine how your system is behaving throughout an entire day. For example, you see that during the night your system experiences less transaction activity than during the day.
| Anchor | ||||
|---|---|---|---|---|
|
Applications are called upon to support additional users and data, over the years. One of today’s tasks is ensure that your application and servers are scalable for tomorrow’s tasks.
...