Page History
...
- On the StartPoint screen, click AdminPoint on the Precise bar. The Precise AdminPoint Dashboard tab opens. See About the Dashboard tab.
...
- 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.
...
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. |
...
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:
...
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:
...
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.
...
Version 9.5 introduces an additional data aggregation interval for Precise for J2EE and Precise SmartLink - the Short Time Slice (STS), that can be defined as either 30 or 300 seconds. To configure this aggregation interval, see “Modifying the Precise Load Data slice size” on page 77.
| 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.
...