Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Database Performance Analyzer (DPA) > Database Performance Analyzer Getting Started Guide > Investigate performance issues > The DPA approach to investigating performance issues

The DPA approach to investigating performance issues

Created by Melanie Boyd, last modified by Melanie Boyd on Sep 30, 2016

Views: 63 Votes: 0 Revisions: 5
DPA_GS_Home.png
video-icon.png
Check out this video (4:09) on navigating the DPA interface to diagnose performance issues.
 

DPA provides a unique approach to investigating performance issues. Use DPA's wait-based analysis approach to focus on issues that provide the greatest performance improvements.

DPA's agentless architecture uses less than one percent of database resources, so it can monitor production systems without affecting their performance.

Wait-based analysis

Traditional database monitoring tools focus on database health metrics to troubleshoot database performance problems. DBAs can spend hours tuning the database to improve these metrics, only to find that their changes had little or no effect on performance.

Instead of database health metrics, DPA focuses on application and end-user wait times. DPA graphically shows you where the longest wait times are. You can drill in to find the root cause of a performance issue and get advice on how to fix it. When you use DPA to find and fix the issues that are directly responsible for long wait times, you can deliver performance improvements that get noticed.

Use the DPA home page to quickly identify database instances with high wait times, and then drill in for details.

File:Success_Center/New_Articles/DPA_Getting_Started_Guide/060/010/gs-home-page-overview.png

Additional context from resource metrics

Storage administrators, network administrators, and DBAs often function within silos, using tools that give them an incomplete view of the factors that affect performance.

In addition to database performance data, DPA also shows resource metrics such as disk usage, CPU usage, I/O latency and rates, and memory usage. These metrics show what was happening in the rest of your environment during database slow-downs. You can correlate waits in the database with other events such as disk I/O or CPU spikes. This information provides the context you need to identify the root cause of complex performance problems.

File:Success_Center/New_Articles/DPA_Getting_Started_Guide/060/010/gs-resource-metrics.png

Using DPA to investigate problems

For more information about using DPA to find the root cause of performance problems, see:

Last modified
14:57, 30 Sep 2016

Tags

Classifications

Public