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 056E25367F; Tue, 5 Apr 2005 04:57:56 +0100 (BST) 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 92903-03; Tue, 5 Apr 2005 03:57:50 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id A19F9537BE; Tue, 5 Apr 2005 04:57:48 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j353veGE007439; Mon, 4 Apr 2005 23:57:40 -0400 (EDT) To: Greg Stark Cc: Christopher Petrilli , jd@commandprompt.com, "Marc G. Fournier" , pgsql-performance@postgresql.org Subject: Re: Sustained inserts per sec ... ? In-reply-to: <87y8bxophw.fsf@stark.xeocode.com> References: <20050401140421.P18194@ganymede.hub.org> <59d991c4050401113857086517@mail.gmail.com> <28353.1112388128@sss.pgh.pa.us> <59d991c4050401124638c4ab5d@mail.gmail.com> <1112388818.3487.34.camel@jd2.commandprompt.com> <59d991c4050401125956d6069d@mail.gmail.com> <59d991c40504040648457808e9@mail.gmail.com> <26454.1112629979@sss.pgh.pa.us> <59d991c405040409094e7bbd17@mail.gmail.com> <26669.1112631807@sss.pgh.pa.us> <59d991c40504041846bc39a6@mail.gmail.com> <5217.1112668589@sss.pgh.pa.us> <87y8bxophw.fsf@stark.xeocode.com> Comments: In-reply-to Greg Stark message dated "04 Apr 2005 23:45:47 -0400" Date: Mon, 04 Apr 2005 23:57:40 -0400 Message-ID: <7438.1112673460@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/81 X-Sequence-Number: 11478 Greg Stark writes: > All this is happening within a single transaction too, right? So there hasn't > been an fsync the entire time. It's entirely up to the kernel when to decide > to start writing data. No ... there's a commit every 500 records. However, I think Chris said he was running with fsync off; so you're right that the kernel is at liberty to write stuff to disk when it feels like. It could be that those outlier points are transactions that occurred in the middle of periodic syncer-driven mass writes. Maybe fsync off is counterproductive for this situation? regards, tom lane