Page History
...
- On the StartPoint screen, click AdminPoint on the Precise bar. The Precise AdminPoint Dashboard tab opens. See About the Dashboard tab on page 24.
| Anchor | ||||
|---|---|---|---|---|
|
...
Table 2-1 Precise bar in AdminPoint
| Icon | Name | Description |
|---|---|---|
 | Back | During a work session, Precise products keep track of where you have navigated to. The Back, Forward, and History buttons enable you to navigate between previously visited views. The Back control displays your previous view. |
 | Forward | Enables you to navigate to the next view. This button is only enabled if you clicked Back, or if you chose a history option. |
 | Stop | Stops a request for information from the server. |
 | Refresh | Updates the data currently displayed. |
 | Home | Navigates to the highest level entity, usually the instance or AppTier (all instances). The time frame settings remain the same. |
 | Send | Opens new email message in your email program with the link to the current environment in context. |
 | Help | Opens the online help in context. |
 | Favorites | Enables you to add or remove favorites in your Precise Favorites list. See Adding, viewing, and deleting Favorites |
| . | ||
 | Settings | Lets you define Precise settings in StartPoint. See Launching StartPoint |
| . |
About the Print function
The new Print function includes the following features:
...
- Click Print on the Precise bar.
- In the Print Option dialog, select the area(s) of the screen you want to print or save.
- Click OK.
- On the resizable preview screen, the dashed line on the right indicates the right margin. Change table column widths to ensure the information you want to print or save is within this margin.
- Click the Print or Save icon at the top right-hand side of the screen, follow the displayed dialog box instructions and click Print or OK.
| Anchor | ||||
|---|---|---|---|---|
|
The Favorites function allows you to save a specific location in Precise and to retrieve the same location later without having to navigate to it. For this purpose, a friendly user interface similar to the familiar Favorites option in the Internet Explorer has been implemented.
...
- On the Add/Delete Favorites dialog box, select the Favorite location to be deleted.
Click Delete. The dialog box closes and the selected Favorite is deleted from the list.
Info The favorite address is displayed in the Address field and cannot be edited.
...
- Click the Table icon on the upper right-hand side of a table and select Copy to clipboard.
The table can be pasted into Microsoft Excel or as an HTML file.
...
- Right-click a graph and choose Copy to clipboard.
You can now paste the image into any application that works with the clipboard.
...
- Right-click the graph.
- Select Export to ASD Portlet.
- Insert a name in the name field that clearly describes the graph view.
- Click OK.
| Anchor | ||||
|---|---|---|---|---|
|
StartPoint can be launched via AdminPoint.
...
This section includes the following topics:
- Top n filtering
- Retention of totals and partial filtering
- Two-phase filtering
- Ranking formula
- Technology-specific implementations
- Additional filtering during summary
| Anchor | ||||
|---|---|---|---|---|
|
The filtering mechanism is based on top n. We rank all activities and then apply the top n filtering. Subsequently, only the top n activities will be loaded. The rest will be filtered out.
...
Some technologies collect data and prepare multiple performance tables to be loaded. When necessary, multiple n thresholds are defined to allow a more granular control on the filtering.
All filtering parameters are defined in the PMDB (per technology) Load process. Filtering thresholds (as well as any other PMDB process parameters) can specify a default value per technology plus specific values for selected instances.
| Anchor | ||||
|---|---|---|---|---|
|
| Info |
|---|
Retention of totals and partial filtering is not new. It has been in use since version 7.1. |
...
The amount of partially filtered rows depends on the number of different combinations of values of the protected identifiers. To control the amount of partially filtered rows, version 8.5 introduced Two-phase filtering.
| Anchor | ||||
|---|---|---|---|---|
|
This filtering mechanism works as follows:
...
Table PW_ORSO_STMT_OBJ_STATS_T is the most detailed statistics table. It contains I/O and locks counters for combinations of Program, User, Machine, Statement, File, and Object (Table or Index).
Prior to version 8.5, we had to choose between two bad alternatives:
...
This way we can protect our most important identifier and at the same time avoid flooding the PMDB with low values of that identifier.
| Anchor | ||||
|---|---|---|---|---|
|
Products that consider Service Time (Avg) as more important than Service Time (Summed) and also use Service Time (Avg) as the default sort field have additional considerations.
...
Thus, in version 8.5, Precise for Web and Precise for J2EE define the primary counter as a formula. This formula is used to rank all activities by the top n mechanism.
The ranking formula is: Service Time (Avg) * Logy Executions.
...
- High. No log function. Ranking based on Service time (Summed). If an activity is executed 1,000,000 times, it will be weighted 1,000,000 times more.
- Med. Base is 2. If an activity is executed 1,000,000 times, it will be weighted 20 times more.
- Low. Base is 10. If an activity is executed 1,000,000 times, it will be weighted 6 times more.
| Anchor | ||||
|---|---|---|---|---|
|
Oracle
Precise for Oracle loads three sets of data:
...
Precise for Oracle uses the Two-phase filtering technique as follows:
- Program. After the first aggregation phase, all records that are not part of the top 300 are partially filtered by protecting all programs, modules, and users. All other identifiers are converted to _I3OTHER_ and then the second aggregation phase takes place. The partially filtered records compete with the original top 300 records. When an ERP extension is installed, the user is overridden by the ERP user. In this case it will not protect the user any more. If many SAP users executed the same SAP transaction, after second aggregation phase all of them will be aggregated into one record. So, this protected SAP transaction is promoted and may make it into the top 300 programs.
- Statement. After the first aggregation phase, all records that are not part of the top 500 are partially filtered by protecting all statements and execution plans. All other identifiers are converted to _I3OTHER_ and then the second aggregation phase takes place. The partially filtered records compete with the original top 500 records.
...
Precise for SQL Server and Precise for Sybase implement a similar top n filtering mechanism. Both technologies generate and filter only one set of records: each record contains a combination of database, user, program, login, machine, statement, and batch.
The Two-phase filtering technique is used as follows:
...
As specified above, by default only top 500 statements will be loaded. To change the default: go to AdminPoint>Warehouse>Processes and select Load Data process of the SQL Server or Sybase technology>Parameters.
Web
Precise for Web has both pre-aggregation and post-aggregation filtering.
...
For each of the two sets you can configure the maximum number of rows to be loaded. Top records will be loaded based on a formula that weights both average service time and number of executions as described in Ranking formula.
By default, top 1000 URL records and top 100 Page records will be loaded each 15 minutes. In both sets, the weight of executions is MEDIUM. If you want to focus on the worst average response time, change the weight of executions to LOW. If you want to focus on the top resource consumers, change the weight of the executions to HIGH.
...
By default, the top 200 records will be loaded every 15 minutes. In all sets, the weight of executions is MEDIUM. If you want to focus on the worst average response time, change the weight of executions to LOW. If you want to focus on the top resource consumers, change the weight of the executions to HIGH.
All the above can be configured for all instances or on a per instance basis using AdminPoint>Warehouse>Processes and selecting Load Data process of the OS | MQ | Tuxedo | OA | Other technology>Parameters.
...
Precise for J2EE has two data filtering mechanisms, one that takes place inside the client JVM (where it can be defined as activated or deactivated), and one that takes place within the PMDB. For information about data filtering inside the client JVM, see “About About configuring data filtering” on page 105filtering.
Version 9.5 introduces an An additional data aggregation interval for Precise for J2EE and Precise SmartLink - is the Short Time Slice (STS), that can be defined as either 30 or 300 seconds. To configure this aggregation interval, see “Modifying Modifying the Precise Load Data slice size” on page 77size.
| Anchor | ||||
|---|---|---|---|---|
|
All the above mentioned filtering refers to filtering the performance data prior to the load into the PMDB. This section deals with additional filtering applied after loading data into the PMDB, when summarizing data into daily, weekly, and monthly tables.
...
For example, we load the top 500 SQL statements per instance, every 15 minutes. The daily summary process aggregates the entire day (96 time slices of 15 minutes each) into one row per SQL statement that contains its daily activity.
The best case scenario is when the application is static and the same top 500 statements are loaded every 15 minutes. In this case, the daily summary will only load 500 statements to the daily tables.
The worst case scenario is when a completely different set of top 500 statements are loaded. In this case nearly 50,000 (500*96) rows will be loaded into the daily tables per instance per day.
...
With additional filtering, while aggregating the rows from the time slice tables, only the top n rows will be loaded into daily tables (plus one row per hour group that retains totals).
...
The Precise administrator can modify these three thresholds per technology or per instance, using the Parameters button when the PMDB Summarize Data process is selected.
In version 9.0, the new STS (short time slice) table is introduced for Precise for J2EE and Precise for SmartLink. The Precise administrator cannot modify the top n threshold value when summarizing a J2EE or SmartLink tree-like table from the STS level to the regular, cube-like, T (15 minute) level. This threshold is defined as the technology’s default daily value, and this summary filters the top n trees (each tree is an activity with multiple rows), into a daily table of rows.
Precise. Performance intelligence from click to storage. Learn more > >
...
...