Subject: Re: sql-bench
From: Mark Lewis <mark.lewis@mir3.com>
To: yoav x <yoav112003@yahoo.com>
Cc: pgsql-performance@postgresql.org
In-Reply-To: <20060913122414.16995.qmail@web35811.mail.mud.yahoo.com>
References: <20060913122414.16995.qmail@web35811.mail.mud.yahoo.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: MIR3, Inc.
Date: Wed, 13 Sep 2006 07:44:30 -0700
Message-Id: <1158158670.9657.1252.camel@archimedes>
Mime-Version: 1.0

The last I checked (years ago), sql-bench was very synthetic (i.e.
reflecting no realistic use case).  It's the sort of test suite that's
useful for database developers when testing the effects of a particular
code change or optimization, but not so applicable to real-world uses.  

Historically the test was also bad for PG because it did nasty things
like 10,000 inserts each in separate transactions because the test was
written for MySQL which at the time didn't support transactions.  Not
sure if that's been fixed yet or not.

Can you provide details about the schema and the queries that are slow?

-- Mark

On Wed, 2006-09-13 at 05:24 -0700, yoav x wrote:
> Hi
> 
> I am trying to run sql-bench against PostgreSQL 8.1.4 on Linux.
> Some of the insert tests seems to be ver slow 
> 
> For example: select_join_in
> 
> Are there any tuning parameters that can be changed to speed these queries? Or are these queries
> especially tuned to show MySQL's stgrenths?
> 
> 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match