Date: Mon, 16 Mar 2015 14:38:16 +0100
From: Andreas Kretschmer <akretschmer@spamfence.net>
To: pgsql-performance@postgresql.org
Subject: Re: MusicBrainz postgres performance issues
Message-ID: <20150316133816.GA20821@tux>
References: <B008F2EE-45D7-4535-9163-56A8CDCA553C@musicbrainz.org>
 <55063EBC.5020405@tara-lu.com> <etPan.5506d3c8.2ae8944a.15b19@poot>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <etPan.5506d3c8.2ae8944a.15b19@poot>
User-Agent: Mutt/1.5.18 (2008-05-17)
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

Robert Kaye <rob@musicbrainz.org> wrote:

> However, I am glad to report that our problems are fixed and that our server is
> back to humming along nicely. 
> 
> What we changed:
> 
> 1. As it was pointed out here, max_connections of 500 was in fact insanely
> high, especially in light of using PGbouncer. Before we used PGbouncer we
> needed a lot more connections and when we started using PGbouncer, we never
> reduced this number.
> 
> 2. Our server_lifetime was set far too high (1 hour). Josh Berkus suggested
> lowering that to 5 minutes.
> 
> 3. We reduced the number of PGbouncer active connections to the DB.
> 


Many thanks for the feedback!


Andreas
-- 
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect.                              (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly."   (unknown)
Kaufbach, Saxony, Germany, Europe.              N 51.05082°, E 13.56889°


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