Product
 Why DBspeed

DBspeed offers hundreds of data mining queries as the enhancement to conventional Oracle AWR & ASH reports. Using data mining queries against AWR & ASH data to troubleshoot database performance issues has become a widely-adopted practice nowadays. The uniqueness of DBspeed lies in its user-friendly graphic interface which organizes and presents data mining queries.

By considering the difference between AWR data and ASH data, DBspeed provides a multidimension analytical model to line them up for time-series analysis. Dimensions are identified as key variables which could play roles in database performance, such as SQL, SQL plan, wait event, database object, etc. Dimensions act as entry points to check database performance symptoms. They also enable us to compare and contrast AWR data and ASH data for the purpose of revealing the true image of database workload. DBspeed's systematic methodology has been proven to be efficient for troubleshooting performance issues and identifying potential performance bottlenecks.

DBspeed has been released on Windows 2000/XP/Vista/7 and Mac OS X platform.
Three-month Free Trial download today!

 Screenshots
   AWR Average Active Session
   AWR DB Time
   ASH Average Active Session

Dimension:
Average Active Session

Average Active Session (AAS) is a sensitive indicator of database workload and performance. There are two ways to calculate it: either from AWR data (DB time) or ASH data (sample counts). AWR AAS is usually called as 'cumulative AAS' while ASH AAS is call as 'sampled AAS'. Each AAS has its talent to tell when performance issue starts.

   AWR Top 5 Foreground Wait Events
   ASH Top User Events
   ASH Top Latch Events

Dimension:
Wait Event

Wait event is one of the golden metrics for troubleshooting performance issue. Both AWR data and ASH data can provide ‘top’ list which should be cross-checked. AWR data can be further drilled down to wait statstics details. ASH data can provide ‘tracing’ type of information to reveal session details related to wait events.

   AWR Top SQL by Elapsed Time
   ASH Top SQL

Dimension:
SQL

SQL is another golden metric for troubleshooting performance issue. Both AWR data and ASH data can provide ‘top’ list. The ‘top’ list from ASH data can be filtered out according to session pattern such as user name, service name, module, action, program, client id.

   ASH Top SQL Plan
   SQL Plan Change by SQL ID

Dimension:
SQL Plan

SQL Plan is another golden metric for troubleshooting performance issue. AWR data can provide ‘top’ list based on how many SQLs are related to a specific SQL plan, and what are the footprints (sql stats) those SQLs incur on the database. ASH data can provide ‘top’ list based on how significant a SQL plan shows up in the sampling.

   AWR Top Segments by Logical Reads
   ASH Top Objects

Dimension:
Object

Object, or segment, is also a golden metric for troubleshooting performance issue. Pay attention to ‘% of total’ or ‘% of capture’ when reviewing the ‘top’ list provided by AWR data for the purpose of accuracy. The ‘top’ list from ASH data has constraints because the object information is limited to certain wait events.

   AWR IO Load Profile per Snapshot
   AWR IO Response Time by Wait Event
   ASH Top Files

Dimension:
IO Statistics

AWR data provides dominant IO statistics for performance tuning and capacity planning purposes. Three primary metrics (IO load profile, throughput and response time) are lined up to reveal what is database’s IO characteristic, whether the increase of workload leads to the performance degradation at IO path, etc. ASH data is limited to situations where certain certain data files are significately accessed by sampled sessions.

   AWR GC Throughput
   AWR GC Blocks Served Time

Dimension:
GC Statistics

GC statistics is for RAC database and it primarily comes from AWR data. Like IO statistics, both throughput and response time are examined at various angles to reveal if there is performance issue at interconnect.

   AWR Service Load Profile
   ASH Top Applications
   ASH Top Blocking Sessions

Dimension:
Service, Application, Session

AWR data is cumulative at instance level and plays limited role here: only the load profile can be broken down to service level. ASH data is sampled at session level and has its strength at various angles: the ‘session’ refers to not only session id, but also application level and service level information such as user name, service name, module, action, program, client id.

DBspeed I
for Oracle Database

$399

DBspeed II
for Oracle RAC Database

$499

  Windows 2000/XP/Vista/7/8
  Mac OS X 10.6 and newer
Request trial version contact


Copyright © 2011 Actrace. All Rights Reserved.
Home | Product | Case Study | Support | Order | Contact Us