pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marcin Giedz <marcin.giedz@eulerhermes.pl>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Xeon vs Opteron - second revision - tests and questions
Date: Fri, 11 Nov 2005 19:39:59 +0100
Message-ID: <4374E57F.5030201@eulerhermes.pl> (raw)
In-Reply-To: <18347.1131563949@sss.pgh.pa.us>
References: <200511091526.51685.marcin.giedz@eulerhermes.pl>
	<18347.1131563949@sss.pgh.pa.us>

Hello,

First of all: many thanks Tom for pointed me out what I made wrong and 
Jim for 'spikes'.

I made some new tests:
available at http://85.128.68.44

What have changed since last time:
    - database engine - now it's 8.1.0
    - number of clients  - "-c 20 "
    - number of transactions - "-t 1000"

Really seems that you have made EXCELLENT work. Performance increased 
about 25% in 8.1.0.

I also made some changes related with bg_write and wal (according to Jim):
bg_writer_all_percent = 0.433
bg_writer_all_maxpages = 15
wal_buffers = 8192

However I still can see 'spikey' performance but  not as much as  before 
changes.  What can I do  more to  eliminate or smooth these spikes? I 
tried to increase bg_writer_all_xxx parameters but.... spikes still 
exists ;).


Regards,
Marcin

>This is pretty nearly an ideal example of how NOT to use pg_bench :-(
>
>In the first place, don't use a number of clients (-c) much exceeding
>the scale factor (-s).  If you do, then almost all you are measuring is
>the effects of update contention.  There are only scale-factor rows in
>the branches table, and every pgbench transaction wants to update one of
>the branches rows, so with -c 100 and -s 20 there are on average going
>to be 5 transactions simultaneously trying to modify the same branches
>row.  4 of them are going to be waiting.  Does that really correspond
>to a real-world situation that you want to optimize?
>
>In the second place, you need a run length considerably longer than
>-t 100 to avoid getting swamped by noise of startup/shutdown overhead.
>I usually use at least -t 1000 if I want repeatable numbers.
>
>BTW, PG 8.1 will probably do better than 8.0 on multi-CPU hardware.
>
>			regards, tom lane
>
>---------------------------(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
>
>  
>




view thread (4+ messages)  latest in thread

Message-ID: <4374E57F.5030201@eulerhermes.pl>
Permalink:  ../4374E57F.5030201@eulerhermes.pl/
Also on:    postgresql.org/message-id/4374E57F.5030201@eulerhermes.pl

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: marcin.giedz@eulerhermes.pl, tgl@sss.pgh.pa.us, jnasby@pervasive.com
  Subject: Re: Xeon vs Opteron - second revision - tests and questions
  In-Reply-To: <4374E57F.5030201@eulerhermes.pl>
  References: <200511091526.51685.marcin.giedz@eulerhermes.pl> <18347.1131563949@sss.pgh.pa.us> <4374E57F.5030201@eulerhermes.pl>

* 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