pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Heikki Linnakangas <heikki@enterprisedb.com>
To: Markus Schiltknecht <markus@bluegap.ch>
Cc: pgsql-performance@postgresql.org
Subject: Re: dbt2 NOTPM numbers
Date: Mon, 04 Jun 2007 21:22:35 +0100
Message-ID: <4664748B.2060304@enterprisedb.com> (raw)
In-Reply-To: <46642F2E.3080509@bluegap.ch>
References: <466428F7.5010808@bluegap.ch>
	<46642B33.6030101@enterprisedb.com>
	<46642F2E.3080509@bluegap.ch>

Markus Schiltknecht wrote:
> Hi,
> 
> Heikki Linnakangas wrote:
>> There's clearly something wrong. The response times are ridiculously 
>> high, they should be < 5 seconds (except for stock level transaction) 
>> to pass a TPC-C test. I wonder if you built any indexes at all?
> 
> Hm.. according to the output/5/db/plan0.out, all queries use index 
> scans, so that doesn't seem to be the problem.

I still suspect there's something wrong with plans, I doubt you can get 
that bad performance unless it's doing something really stupid. I'd 
suggest setting log_min_duration_statement = 5000, and seeing what you 
get. Also check pg_stat_user_table.seq_scan just to be extra sure 
there's no seq scans.

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



view thread (19+ messages)  latest in thread

Message-ID: <4664748B.2060304@enterprisedb.com>
Permalink:  ../4664748B.2060304@enterprisedb.com/
Also on:    postgresql.org/message-id/4664748B.2060304@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, markus@bluegap.ch
  Subject: Re: dbt2 NOTPM numbers
  In-Reply-To: <4664748B.2060304@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