Page History
...
For an explanation on how to define instance groups, see the Precise Installation Guide. The table below describes the information displayed in the Instance Grouping table.
Table 8- 1 Instance Grouping table
Item | Description |
---|---|
Group | Displays the name of the group. |
Instances | Displays the number of instances linked to the group. |
Engine Utilization | Displays the average Engine Utilization for the instances in the specified group. |
Committed Transactions | Displays the SUM number of Committed Transactions for the instances in the specified group. |
Connections Opened (Sum) | Displays the sum of opened connections for the instances in the specified group. |
About viewing instances associated with an Tier in the Association area
Displays information on the Instances associated with the selected Tier in the Association area. The table below describes the information displayed in the tabs in the Association area.
Table 8- 2 Viewing information on associated instances
Tab | Description |
---|---|
Overview | Displays counters reporting on CPU Usage, Memory Usage and amount of Locked Data. |
Network | Displays counters reporting on the number of times an engine polls incoming and outgoing packets and bytes. |
Disk I/O | Displays various counters reporting on the amount of disk I/O. |
Transactions | Displays counters reporting on the number of rows changed in the instance, grouped by type (insert, update, and delete). |
Anchor | ||||
---|---|---|---|---|
|
...
The Replication Inbound view is a combination of a few predefined graphs related to the inbound processing phase (replication agent); the view helps you identify what may be causing the latency in the replication system. The information displayed in the Instance level is a summation of all the replicated databases of the instance.
Table 8- 3 I/O vs Cmds Sent
Graph | Description |
---|---|
IO vs. Cmds Sent | Highlights The IO vs. Cmds Sent graph shows the number of commands processed by the RepAgent during the given period and the amount of time the RepAgent had to wait while writing to the inbound queue. Each bar represents a time period. The speed of the RepAgent is directly proportional to the speed of ASE processing the network that sends requests coupled with the speed of the Replication Server processing. What to do next
|
Table 8- 4 Truncation Point Movement
Graph | Description |
---|---|
Truncation Point Movement | Highlights The Truncation Point Movement graph shows the number of times the RepAgent has asked the RS for a new secondary truncation point and then moved the secondary truncation point in the log. If 'Moved' is more than one less than 'Gotten', the likely cause is that a large or open transaction exists from the Replication Server perspective (either it is indeed still open in ASE or the RepAgent has not forwarded the commit record yet). What to do next
|
Table 8- 5 Network
Graph | Description |
---|---|
Network | Highlights The Network graph shows information related to the network activity. If the Number of Full Packets is a considerable percentage out of the total package sent (>= 90%), then you may need to consider increasing the send_buffer_size. What to do next
|
Table 8- 6 Log Scan Summary
Graph | Description |
---|---|
Log Scan Summary | Highlights The Log Scan Summary graph is an indicator of how much work the RepAgent is doing and how much information is being sent to the Replication Server. Replicated log records are records converted into LTL and sent to the RS. Not replicated log records are all log records that were scanned but not sent. What to do next
|
Table 8- 7 Replicated Commands Breakdown
Graph | Description |
---|---|
Replicated Commands Breakdown | Highlights The Replicated Commands Breakdown lists the number and type of commands that were replicated and which most affect the replication.
What to do next
|
About viewing Replication Outbound view graphs
The Replication Outbound view graphs view is a combination of a few predefined graphs related to the outbound processing phase. This enables you to understand what specific component(s) may be causing the latency in the replication system. The information displayed in the instance level is a summation of all the outbound processing performed for the specified instance by all the Replication servers attached to it.
Table 8- 8 SQM Processing
Graph | Description |
---|---|
SQM Processing | Highlights The SQM Processing graph shows the space usage of SQM queue overtime versus the number of commands written to the queue. The SQM Commands Written indicates the amount of activity performed by the replication server. What to do next
|
Table 8- 9 DSI SQT Processing
Graph | Description |
---|---|
DSI SQT Processing | Highlights The DSI SQT Processing graph shows space usage of the outbound queue cache. The Cache size lists the size of the SQT cache. Cached Used shows SQT thread memory usage over time. Each command structure (allocated by an SQT thread) is freed when its transaction context is removed. Consequently, if no transactions are active in SQT, then SQT cache usage is zero. If Cached Used is near the maximum cache size capacity and Trans Removed is constantly greater than zero, you may decide to increase the SQT cache size by increasing dsi_sqt_max_cache_size. Don’t increase the cache size if Trans Removed is occasionally greater than zero; this situation usually means that a transaction was removed from the cache because it was greater than the dsi_sqt_ max_cache_size. For occasional increases of Trans Removed, increasing the cache size will have the opposite effect because the latency in processing transactions ahead of them will likely result in their being removed. The SQM Read Cached indicates how many 16K blocks of cache were read by the SQM Reader thread. This number should be as high as possible. If it is constantly hitting zero, most likely there is a latency in executing the SQL at the replicate; resulting in the DSI SQT cache to reach its maximum. What to do next
|
Table 8- 10 DSIE Transactions Processing
Graph | Description |
---|---|
DSIE Transactions Processing | Highlights The DSIE Transactions Processing graph shows how long it took to process a transaction by a DSI/E thread breakdown to various phases.
What to do next
|
Table 8- 11 DSIE Commands Applied
Graph | Description |
---|---|
DSIE Commands Applied | Highlights The DSIE Commands Applied graph shows how many commands were successfully applied to the target database by DSI/E overtime (relevant for version 15 and higher). It can be used to measure the amount of work imposed by the replication server. You can also compare that number to the SQM Commands Written and check if there is a lag in processing commands inside the replication server. What to do next
|
Anchor | ||||
---|---|---|---|---|
|
...
The table below describes what the utilization status of an engine indicates.
Table 8- 12 Utilization status
Engine Busy | CPU Yields | Status |
---|---|---|
Low | Low | Engine is CPU starved |
Low | High | Engine is inactive |
High | Low | Engine is busy |
High | High | Engine is busy |
To improve kernel utilization, it is recommended to check the Disk I/O and Network view. This is done to determine if the number of checks for I/O or Network that the engine performs, is ideal or are overhead.
...
- Select the associated required performance group from the Associations list.
- Select the required counter.
...
- .
...
...