pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Franck Routier <franck.routier@axege.com>
To: Guillaume Cottenceau <gc@mnc.ch>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: Postgresql performance degrading... how to diagnose the root cause
Date: Fri, 29 Mar 2013 16:31:07 +0100
Message-ID: <5155B3BB.4080209@axege.com> (raw)
In-Reply-To: <m3hajudzv1.fsf@mnc.ch>
References: <5155A33A.4090000@axege.com>
	<m3hajudzv1.fsf@mnc.ch>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

Hi,
> I don't know that tcp-b does
tpcb.jar is a java implementation of the http://www.tpc.org/tpcb/ 
benchmark. It is not particularly representative of my workload, but 
gives a synthetic, db-agnostic, view of the system performance.
We use it to have quick view to compare differents servers (different 
OS, different RDBMS, etc...).

That said, the test wil create tables, load them with data, and perform 
some transactions on them.
The point that makes me wonder what happens, is that the test run on my 
main database is slow, while the same test run on a database on its own 
is quick.
This is the same postgresql cluster (same postgresql.conf), same 
tablespace (so same disks), same hardware obviously.

Regarding the server activity, it seems quite flat : iostat shows that 
disks are not working much (less than 5%), top shows only one active 
core, and load average is well under 1...


>
> http://wiki.postgresql.org/wiki/Show_database_bloat
How do I interpret the output of this query ? Is 1.1 bloat level on a 
table alarming, or quite ok ?

Franck

Attachments:

  smime.p7s (application/pkcs7-signature, 4.4K) download

view thread (9+ messages)  latest in thread

Message-ID: <5155B3BB.4080209@axege.com>
Permalink:  ../5155B3BB.4080209@axege.com/
Also on:    postgresql.org/message-id/5155B3BB.4080209@axege.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: franck.routier@axege.com, gc@mnc.ch
  Subject: Re: Postgresql performance degrading... how to diagnose the root cause
  In-Reply-To: <5155B3BB.4080209@axege.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