pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Viktor <viktor@okservers.eu>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Random server overload
Date: Tue, 01 Oct 2013 16:19:12 +0300
Message-ID: <524ACBD0.5000400@okservers.eu> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Hello,

We are experiencing database random overloads caused by IDLE processes. 
Their count jumps from normal ~70 connections to 250-300 with high I/O 
(30-40% wa, when normal ~ 1 % wa).

The overload isn't long and lasts about 5 -10 minutes just a couple of 
times during the month.

Please suggest how to debug this issue and find the cause of the 
overloads. Or mby we should tune our config file ?

errorlog example:
2013-09-30 10:37:45 EEST FATAL:  sorry, too many clients already
2013-09-30 10:37:45 EEST FATAL:  remaining connection slots are reserved 
for non-replication superuser connections
...

config file:

max_connections = 250
shared_buffers = 16GB
temp_buffers = 16MB
max_prepared_transactions = 0
work_mem = 448MB
maintenance_work_mem = 4GB
max_stack_depth = 6MB
wal_buffers = 18MB
checkpoint_segments = 30
checkpoint_timeout = 5min
checkpoint_warning = 30s
random_page_cost = 4.0
cpu_tuple_cost = 0.01
cpu_index_tuple_cost = 0.005
effective_cache_size = 50GB
default_statistics_target = 100
autovacuum = on

othr values are defaults.

System:
RAM 74 GB
PostgreSQL 9.1.9, Debian 6
Database size on disc: 84 GB data + 23 GB indexes. Different LVMs on 
RAID 10.


--
Best regards



-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (9+ messages)  latest in thread

Message-ID: <524ACBD0.5000400@okservers.eu>
Permalink:  ../524ACBD0.5000400@okservers.eu/
Also on:    postgresql.org/message-id/524ACBD0.5000400@okservers.eu

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: viktor@okservers.eu
  Subject: Re: Random server overload
  In-Reply-To: <524ACBD0.5000400@okservers.eu>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox