Welcome!

SOA & WOA Authors: Liz McMillan, Paige Leidig, Andreas Grabner, Tim Hinds, Jerry Melnick

Related Topics: SOA & WOA, Java, AJAX & REA, Big Data Journal

SOA & WOA: Article

When It REALLY Is the Database to Blame for Bad Performance

A Story About Slow Statements and Resulting Connection Pool Issues

Far too often "the database" is blamed for impacting performance and scalability of applications. In many cases, however, it turns out that it's not the database itself, but the way the database is accessed by the application. Common problem patterns are requesting too much data, inefficient queries, lack of data caching, and waste connection usage, for example.

But, there are cases where the database is to be blamed. This is the scenario of the following story one of our customers shared with me:

The company runs 4 JVMs in a WebLogic cluster with each of them having a connection pool to its Oracle database with 20 max connections. They have setup proper application monitoring which includes both system monitoring and application and real user monitoring. Here is what happened on December 16th at 2PM.

Step 1: Alerting on Connection Pool Exhaustion
As part of its application monitoring, the team members are watching connection pool stats from WebLogic via JMX. They look at measures such as ActiveConnectionsCurrentCount, ActiveConnectionsHighCount as well as ConnectionDelayTime. Besides having these metrics on a dynaTrace dashboard that shows them pool usage per JVM over time they also have an automatic alert configured that triggers when a pool is exhausted. This alert triggered at 2:06PM.

The alert triggered at 2:06PM when the first connection pool was exhausted.

If you would like to read more tips and insights on

Step 2: Identifying Long Running SQL

Step 3: Fixing Database Table Statistics

click here!

And If you are interested in more problem patterns around database I encourage you to read some of our other blogs on database related performance topics and also check out our series of Hibernate blogs as we often see E/R Mappers as performance problems in enterprise applications.

More Stories By Andreas Grabner

Andreas has over a decade of experience as an architect and developer, and currently works as a senior performance architect and technology strategist for dynaTrace Software, where he influences product strategy and works closely with customers in implementing performance management solutions across the application life cycle. He is a regular speaker at software conferences, writes for a number of technology publications, and blogs at http://blog.dynatrace.com

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.