Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id D080D9F9248 for ; Sun, 4 Nov 2007 20:39:56 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 83387-06 for ; Sun, 4 Nov 2007 20:39:52 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from cassarossa.samfundet.no (cassarossa.samfundet.no [129.241.93.19]) by postgresql.org (Postfix) with ESMTP id 297DC9F9245 for ; Sun, 4 Nov 2007 20:39:51 -0400 (AST) Received: from trofast.ipv6.sesse.net ([2001:700:300:1803:20e:cff:fe36:a766] helo=trofast.sesse.net) by cassarossa.samfundet.no with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1Ioq0L-0000dl-0z for pgsql-performance@postgresql.org; Mon, 05 Nov 2007 01:39:49 +0100 Received: from root by trofast.sesse.net with local (Exim 4.68) (envelope-from ) id 1Ioq0K-0006bZ-GN for pgsql-performance@postgresql.org; Mon, 05 Nov 2007 01:39:48 +0100 Date: Mon, 5 Nov 2007 01:39:48 +0100 From: "Steinar H. Gunderson" To: pgsql-performance@postgresql.org Subject: Re: Migrating to 8.3 - checkpoints and background writer Message-ID: <20071105003948.GA25351@uio.no> Mail-Followup-To: pgsql-performance@postgresql.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Operating-System: Linux 2.6.20.4 on a x86_64 X-Message-Flag: Outlook? --> http://www.mozilla.org/products/thunderbird/ User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/52 X-Sequence-Number: 27467 On Sun, Nov 04, 2007 at 07:33:46PM -0500, Greg Smith wrote: > On the topic of performance improvements in 8.3, I don't think this list > has been getting information about the concurrent sequential scans > improvements. Check out these documents for more about that: > > http://j-davis.com/postgresql/83v82_scans.html That's a nice writeup. I'm a bit puzzled by this part, though: "All tests are on linux with the anticipatory I/O scheduler. The default I/O scheduler for Linux is CFQ (Completely Fair Queue), which does not work well for PostgreSQL in my tests." All earlier benchmarks I've seen (even specifically for Postgres) have said that cfq > deadline > anticipatory for database work. How large was the difference for you? /* Steinar */ -- Homepage: http://www.sesse.net/