X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id EDCA19FA1E2 for ; Wed, 13 Sep 2006 16:36:30 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 82980-03 for ; Wed, 13 Sep 2006 19:36:23 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by postgresql.org (Postfix) with ESMTP id 1F0009FA197 for ; Wed, 13 Sep 2006 16:36:22 -0300 (ADT) Received: by nf-out-0910.google.com with SMTP id p77so1891627nfc for ; Wed, 13 Sep 2006 12:36:21 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pnX7cJoVAyJ4RON4nTqp9tvIbuAIU4oqxLeOoLh+Bwt+i8R8qCZsG+MKiegK1qXv66H9PJezaWa7s9i0nHAYCsLqNFTfwuUZVvtHVd49Fs4vstc6T4IcnrgX/gAG4pZPiPBYCHhGkRWtY6Cm0nRfkQfBHYgeOJNOKbegXGjOxq0= Received: by 10.78.157.8 with SMTP id f8mr324483hue; Wed, 13 Sep 2006 12:36:21 -0700 (PDT) Received: by 10.78.45.4 with HTTP; Wed, 13 Sep 2006 12:36:21 -0700 (PDT) Message-ID: Date: Wed, 13 Sep 2006 15:36:21 -0400 From: "Merlin Moncure" To: "Tom Lane" Subject: Re: sql-bench Cc: "yoav x" , pgsql-performance@postgresql.org In-Reply-To: <12097.1158161568@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060913122414.16995.qmail@web35811.mail.mud.yahoo.com> <12097.1158161568@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.199 tagged_above=0 required=5 tests=DNS_FROM_RFC_ABUSE, SPF_PASS X-Spam-Level: X-Archive-Number: 200609/129 X-Sequence-Number: 20815 On 9/13/06, Tom Lane wrote: > IIRC, with these settings PG 8.0 seemed to be about half the speed of > mysql 5.0 w/myisam, which is probably somewhere in the ballpark of the > truth for tests of this nature, ie, single query stream of fairly simple > queries. If you try concurrent-update scenarios or something that > stresses planning ability you may arrive at different results though. > I have not retested with more recent versions. if postgresql uses prepared statements for such queries, it will roughly tie mysql/myisam in raw query output on this type of load which also happens to be very easy to prepare...afaik mysql gets zero performance benefit from preparing statements This is extremely trivial to test&confirm even on a shell script. [aside: will this still be the case if peter e's planner changes become reality?] another cheater trick benchmarkers do to disparage postgresql is to not run analyze intentionally. Basically all production postgresql systems of any size will run analyze on cron. another small aside, I caught the sqlite people actually *detuning* postgresql for performance by turning stats_command_string=on in postgresql.conf. The way it was portrayed it almost looked like cheating. I busted them on it (go to http://www.sqlite.org/cvstrac/wiki?p=SpeedComparison and look for the remarks right below the results) merlin