pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rural Hunter <ruralhunter@gmail.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Very slow planning performance on partition table
Date: Wed, 30 Jul 2014 12:16:36 +0800
Message-ID: <53D871A4.8000301@gmail.com> (raw)
In-Reply-To: <CAMkU=1wHC_w6D2kc1V6y1PDkRxDV3B+1fJBk3Z2L=SprGw7omw@mail.gmail.com>
References: <53CFB6BC.4050606@gmail.com>
	<25010.1406253203@sss.pgh.pa.us>
	<53D26875.2080604@gmail.com>
	<53D51E49.102@gmail.com>
	<24564.1406478487@sss.pgh.pa.us>
	<CAMkU=1ydmpt9XRMxt0sPNnQsXEoF_c7bgp2kHxtDbPNGg5Vj5w@mail.gmail.com>
	<53D7597E.2080209@gmail.com>
	<CAMkU=1wHC_w6D2kc1V6y1PDkRxDV3B+1fJBk3Z2L=SprGw7omw@mail.gmail.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

This was no error in the log of pgbouncer, but there is a sudden drop of 
request count when the problem happened:
2014-07-30 11:36:51.919 25369 LOG Stats: 2394 req/s, in 339478 b/s, out 
1422425 b/s,query 3792 us
2014-07-30 11:37:51.919 25369 LOG Stats: 2207 req/s, in 314570 b/s, out 
2291440 b/s,query 5344 us
2014-07-30 11:38:51.919 25369 LOG Stats: 2151 req/s, in 288565 b/s, out 
1945795 b/s,query 10016 us
[=========problem happens=========]
2014-07-30 11:39:51.919 25369 LOG Stats: 1061 req/s, in 140077 b/s, out 
2652730 b/s,query 515753 us
[=========pgbouncer restart=========]
2014-07-30 11:40:52.780 10640 LOG File descriptor limit: 65535 
(H:65535), max_client_conn: 5500, max fds possible: 6560
2014-07-30 11:40:52.781 10640 LOG Stale pidfile, removing
2014-07-30 11:40:52.782 10642 LOG listening on 0.0.0.0:xxxx
2014-07-30 11:40:52.782 10642 WARNING Cannot listen on ::/xxxx: bind(): 
Address already in use
2014-07-30 11:40:52.782 10642 LOG listening on unix:/tmp/.s.PGSQL.xxxx
2014-07-30 11:40:52.782 10642 LOG process up: pgbouncer 1.5.4, libevent 
1.4.13-stable (epoll), adns: libc-2.11
2014-07-30 11:41:52.781 10642 LOG Stats: 2309 req/s, in 331097 b/s, out 
3806033 b/s,query 4671 us
2014-07-30 11:42:52.782 10642 LOG Stats: 2044 req/s, in 285153 b/s, out 
2932543 b/s,query 4789 us
2014-07-30 11:43:52.782 10642 LOG Stats: 1969 req/s, in 282697 b/s, out 
560439 b/s,query 4607 us
2014-07-30 11:44:52.782 10642 LOG Stats: 2551 req/s, in 351589 b/s, out 
3223438 b/s,query 4364 us


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



view thread (21+ messages)  latest in thread

Message-ID: <53D871A4.8000301@gmail.com>
Permalink:  ../53D871A4.8000301@gmail.com/
Also on:    postgresql.org/message-id/53D871A4.8000301@gmail.com

 · 

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-performance@postgresql.org
  Cc: ruralhunter@gmail.com
  Subject: Re: Very slow planning performance on partition table
  In-Reply-To: <53D871A4.8000301@gmail.com>

* 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