PostgreSQL anomalies

The PostgreSQL collector allows to insert the following types of anomalies in an Anomalies Profile:

Data cache hit ratio

Percentage of time a required data block is found in the data cache. This alarm is raised when the data cache hit rate falls below the ranges defined by the thresholds. When PostgreSQL Server can find the data pages it needs in the data cache, it doesn't have to perform a physical I/O. If you notice that this ratio is dropping over time, consider adding memory. The default anomaly conditions are:

Severity 1: < 99%
Severity 2: < 95%
Severity 3: < 90%

Number of free connections

Consider Increasing the "max_connections" configuration parameter if the number of free connections approaches 0. The default anomaly conditions are:

Severity 1: < 3 connections
Severity 2: < 2 connections
Severity 3: < 1 connections

Percentage of blocked connections

Percentage of connections which are blocked by another connection. Any time a connection waits for another connection to complete its transaction, the overall response time for an application is affected. The default anomaly conditions are:

Severity 1: > 15 %
Severity 2: > 20 %
Severity 3: > 25 %

Percentage of locks waiting

Percentage of locks waiting to be granted. Any time a connection waits for another connection to complete its transaction, the overall response time for an application is affected.

Creating indexes on tables on which lots of update and delete are executed can resolve the problem.
The default anomaly conditions are:

Severity 1: > 15%
Severity 2: > 20%
Severity 3: > 25%





Go back to the Learning center:


Copyright © AgileLoad. All rights reserved.
Agile Load testing tool| Contact AgileLoad | Terms of Use | Sitemap