Page History
This section includes the following topics:
- About the Activity tab
- How the Activity tab is structured
- About the entities you can examine in the Activity tab
- About Statement, Batch, Collapsed Statement, and Collapsed Batch entities
- How the Activity tab can help you identify performance problems
| Anchor | ||||
|---|---|---|---|---|
|
The Activity tab allows you to analyze performance behavior over time or within a given time period. When investigating a performance issue, the Activity tab is an excellent place to start. You can easily identify the performance profile of your Sybase instance and determine who is executing which application, what they are waiting for and how many resources they are consuming. This is the critical information you need to identify the top consumers of your Sybase Instance and its major latencies. By focusing on the top consumers and latencies (wait states) you can maximize the tuning impact on your system, while minimizing the time it takes to obtain results.
...
The Activity tab was designed to answer questions such as, "What happened yesterday, as well as a month ago and a year ago?" and "What has been the performance level of my applications over time".
| Anchor | ||||
|---|---|---|---|---|
|
The Activity tab displays information on various entities and their associated entities. The information displayed when you launch the Activity tab depends upon where you are launching from.
...
See About drilling down in context on page 18. See About the Main area on page 18. See About the Association area on page 18. See How most tabs are structured on page 15. See Tasks common to most tabs on page 20. See About the Dashboard tab on page 33.
| Anchor | ||||
|---|---|---|---|---|
|
The Activity tab displays information on different entities. This section provides an overview of all entities, their meaning, and their views. By default, all entities open in Sybase view, with the exception of the Statement, Batch, Collapsed Statement and Collapsed Batch entities, which open by default in the Overview view.
...
See Understanding In Sybase session states on page 25.
| Anchor | ||||
|---|---|---|---|---|
|
When an application component (such as Database or Login) consumes resources in Sybase, it is actually executing a statement that is consuming resources. Tuning performance problems typically involves finding and tuning offending statements.
...
Join Indicates that a join (other than merge join) operation was performed in the execution plan (applicable to Statement entity only).
Nested Loops Join Indicates whether a nested loops join operation was performed in the execution plan (applicable to Statement entity only).
Parallel Access Indicates whether a parallel access operation was performed in the execution plan (applicable to Statement entity only).
Show Plan Error Shows the error that occurred during the last explain process.
...
See Understanding In Sybase session states on page 25.
| Anchor | ||||
|---|---|---|---|---|
|
You can identify a performance problem by doing one or more of the following:
...