Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 924BC9FB35F for ; Tue, 22 May 2007 07:07:43 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 79425-08 for ; Tue, 22 May 2007 07:07:35 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from h07.llord.com (unknown [195.140.142.194]) by postgresql.org (Postfix) with ESMTP id 1B9419FB354 for ; Tue, 22 May 2007 07:07:39 -0300 (ADT) Received: from par69-8-88-161-102-87.fbx.proxad.net ([88.161.102.87] helo=apollo13) by h07.llord.com with esmtpa (Exim 4.63) (envelope-from ) id 1HqRH6-0001YM-KI; Tue, 22 May 2007 12:07:29 +0200 Date: Tue, 22 May 2007 12:10:03 +0200 To: "Gregory Stark" Subject: Re: Postgres Benchmark Results From: PFC Cc: pgsql-performance@postgresql.org Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 References: <87hcq5l1c7.fsf@oxford.xeocode.com> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <87hcq5l1c7.fsf@oxford.xeocode.com> User-Agent: Opera Mail/9.10 (Linux) X-PopBeforeSMTPSenders: junk@peufeu.com, lists@peufeu.com, peufeu@peufeu.com, pfcaillaud@peufeu.com X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - h07.llord.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - peufeu.com X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.754 tagged_above=0 required=5 tests=AWL=0.089, BAYES_05=-1.11, RCVD_IN_NJABL_SPAM=2.775 X-Spam-Level: * X-Archive-Number: 200705/427 X-Sequence-Number: 24817 > Note that while the average hits/s between 100 and 500 is over 600 tps > for > Postgres there is a consistent smattering of plot points spread all the > way > down to 200 tps, well below the 400-500 tps that MySQL is getting. Yes, these are due to checkpointing, mostly. Also, note that a real forum would not insert 100 posts/s, so it would not feel this effect. But in order to finish the benchmark in a correct amount of time, we have to push on the inserts. > Some of those are undoubtedly caused by things like checkpoints and > vacuum > runs. Hopefully the improvements that are already in the pipeline will > reduce > them. I am re-running it with other tuning, notably cost-based vacuum delay and less frequent checkpoints, and it is a *lot* smoother. These take a full night to run, so I'll post more results when I have usefull stuff to show. This has proven to be a very interesting trip to benchmarkland...