Page History
...
- Relative Time Frame. Saving relative timeframe instead of static date. For example, saving the last 7 seven days will always display the last 7 seven days, depending on the day entered.
- One click to specific location. Once you open Precise by launching a saved Favorite item, you will not have to enter a login credential nor click the login button.
- IE Favorites support. Adding a new Favorite item in Precise will also add it to the IE Favorites menu.
- Auto Complete. The Favorites dialog includes a new combo box which supports AutoComplete.
- Auto Naming. The Favorites dialog generates item names based on the current location.
...
| Counter | Description |
|---|---|
| Load time | Should be no more than 10% of the application’s total response time. If this value exceeds 10%, this indicates that the SAP System is spending too much time loading the application. Check the Memory Resources counter to determine if there are any SAP memory shortages. If it appears that the CPU or memory resources are sufficient for the application’s processing, check for the following actions:
|
| Enqueue time | Should constitute a small percentage of the application time. When enqueue time is high, check or perform the following actions:
|
| Roll-wait time | The number of seconds that may be required to wait during roll-in of context information for dialog steps. The number of seconds required to transfer GUI control-related information to the front-end solution is also included. During processing, a program may result in a roll-out while waiting for other processing to take place. The process of roll-out and roll-in (in this case) is usually a change of memory pointers, and roll-wait time is minimal. In SAP 4.6 and higher, several communication steps, called round trips, can occur between the application servers and the front-end system. During the round trip, the application server transfers GUI control-related information to the front-end system. The work process is rolled-out and this time is recorded under roll-wait time. Network and front-end time are included as part of roll-wait time, but only as it applies to the control-related information transferred between the application server and the front-end system during the execution of the dialog step. Network time associated with the first request and the last request is therefore not included in roll-wait time. Roll-wait time should be very low. When high, perform the following steps:
|
| Process time | Should constitute 50-60% of the application’s total SAP response time. When this percentage is higher than it should be, system or SAP memory resources are an issue or the application is spending too much time in application logic. Take the following steps:
|
| Anchor | ||||
|---|---|---|---|---|
|
DB time counters identify whether database response time is attributed to sequential reads, direct reads or changes by comparing their times.
...
| Counter | Description |
|---|---|
| Sequential Reads | The number of logical database requests associated with sequential reads (for example, "select * from ..." ABAP/4 statements). |
| Direct Reads | The number of logical database requests associated with direct reads (for example, "select single ..." ABAP/4 statements). |
| Changes | The number of logical database requests associated with database inserts, updates and deletes. |
See “About About DB time counters” on page 24 and “About counters and About average server buffer ratio” on page 25ratio.
About time per request counters
...
- Sequential reads should be less than 40 milliseconds per request.
- Direct read requests should be less than 10 milliseconds per request.
- Change requests are expected to be greater than 25 milliseconds per request.
- When per request times are not within their expected performance boundaries:
- Use the DB Time section to determine the importance of the types of read or change requests in question, with respect to the overall response time.
- Use the Requests section to understand the request volume involved in read and change requests.
- When sequential reads or direct reads are performing poorly, see the Application Server Buffer Ratio section to investigate whether buffering techniques are optimized for read requests.
- When changes or reads are performing poorly and your Application Server Buffer ratio appears normal, but the number of returned rows appears unacceptable, the database is likely the source of the problem and should be examined for additional indexes or other causes.
| Anchor | ||||
|---|---|---|---|---|
|
The average server buffer ratio illustrates the degree of optimization related to application server buffering techniques, which optimize performance for database requests by avoiding the need to transfer read requests to the database server.
...