X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 246455345F for ; Fri, 13 May 2005 10:00:50 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 30902-05 for ; Fri, 13 May 2005 13:00:38 +0000 (GMT) Received: from cassarossa.samfundet.no (cassarossa.samfundet.no [129.241.93.19]) by svr1.postgresql.org (Postfix) with ESMTP id EBDAC533A6 for ; Fri, 13 May 2005 10:00:37 -0300 (ADT) Received: from trofast.sesse.net ([129.241.93.32]) by cassarossa.samfundet.no with esmtp (Exim 4.34) id 1DWZmP-0004am-Nv for pgsql-performance@postgresql.org; Fri, 13 May 2005 15:00:39 +0200 Received: from sesse by trofast.sesse.net with local (Exim 3.36 #1 (Debian)) id 1DWZmP-0000Wo-00 for ; Fri, 13 May 2005 15:00:37 +0200 Date: Fri, 13 May 2005 15:00:37 +0200 From: "Steinar H. Gunderson" To: pgsql-performance@postgresql.org Subject: Re: PostgreSQL strugling during high load Message-ID: <20050513130037.GB31454@uio.no> Mail-Followup-To: pgsql-performance@postgresql.org References: <01cc01c557ba$a4fdb0b0$f20214ac@bite.lt> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <01cc01c557ba$a4fdb0b0$f20214ac@bite.lt> X-Operating-System: Linux 2.6.11.8 on a i686 X-Message-Flag: Outlook? --> http://www.mozilla.org/products/thunderbird/ User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.016 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200505/257 X-Sequence-Number: 12421 On Fri, May 13, 2005 at 03:52:38PM +0300, Mindaugas Riauba wrote: > Tables are not big (20000-150000 rows each) but have very high > turnover rate - 100+ updates/inserts/deletes/selects per second. > So contents of database changes very fast. Problem is that when > pg_autovacuum does vacuum those changes slows down too much. > And we keep autovacuum quite aggressive (-v 1000 -V 0.5 -a 1000 > -A 0.1 -s 10) to not bloat database and to avoid bigger impact. > analyze seems not to impact performance too much. Are you using the bgwriter? See http://developer.postgresql.org/~wieck/vacuum_cost/ for details. /* Steinar */ -- Homepage: http://www.sesse.net/