pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Heikki Linnakangas <heikki@enterprisedb.com>
To: Manolo _ <mac_man2005@hotmail.it>
Cc: pgsql-performance@postgresql.org
Subject: Re: Benchmarking PG
Date: Tue, 11 Dec 2007 12:11:29 +0000
Message-ID: <475E7E71.1070701@enterprisedb.com> (raw)
In-Reply-To: <BAY112-W366D7B3E454F6A0FBBA62BE6640@phx.gbl>
References: <BAY112-W366D7B3E454F6A0FBBA62BE6640@phx.gbl>

Manolo _ wrote:
> I'd like to benchmark PG. I'd like to compare sorting performances (time spent, #of disk accesses, # of run produced etc) of the present Replacement Selection (external sorting) algorithm and of a refinement I'm going to implement.
> 
> I'm new on PG, I just had the idea of how to possibly get better that algorithm and choosed to test it on PG since it's an open-source DBMS.
> 
> I've been searching the web for a benchmark. I suppose TPC-H and Wisconsin could fit, but had problems when trying to use them.
> Any suggestion on a "good benchmark"?
> Any tutorial on how to use them?

If you want to compare sorting performance in particular, running a big 
query that needs a big sort will be much more useful than a generic DBMS 
benchmark like TPC-H.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com



view thread (4+ messages)

Message-ID: <475E7E71.1070701@enterprisedb.com>
Permalink:  ../475E7E71.1070701@enterprisedb.com/
Also on:    postgresql.org/message-id/475E7E71.1070701@enterprisedb.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: heikki@enterprisedb.com, mac_man2005@hotmail.it
  Subject: Re: Benchmarking PG
  In-Reply-To: <475E7E71.1070701@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox