pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: ml@bortal.de <ml@bortal.de>
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres benchmarking with pgbench
Date: Thu, 19 Mar 2009 15:45:21 -0600
Message-ID: <dcc563d10903191445y4783462drad14a043af003505@mail.gmail.com> (raw)
In-Reply-To: <49C2B854.4080303@bortal.de>
References: <49BE2E84.2040506@bortal.de>
	<alpine.GSO.2.01.0903161052430.9846@westnet.com>
	<49C2B854.4080303@bortal.de>

On Thu, Mar 19, 2009 at 3:25 PM, ml@bortal.de <ml@bortal.de> wrote:
> Hi Greg,
>
> thanks a lot for your hints. I changed my config and changed raid6 to
> raid10, but whatever i do, the benchmark breaks down at a scaling factor 75
> where the database is "only" 1126MB big.
>
> Here are my benchmark Results (scaling factor, DB size in MB, TPS) using:
>  pgbench -S -c  X  -t 1000 -U pgsql -d benchmark -h MYHOST

-t 1000 is WAY too short to judge, you'll be seeing a lot of caching
effects and no WAL flushing.  Try a setting that gets you a run of at
least 5 or 10 minutes, preferably a half an hour for more realistic
results.  Also what is -c X ???  Are you following the -c with the
same scaling factor that you used to create the test db?  And why the
select only (-S)???

> 1 19 8600
> 5 79 8743
> 10 154 8774
> 20 303 8479
> 30 453 8775
> 40 602 8093
> 50 752 6334
> 75 1126 3881
> 150 2247 2297
> 200 2994 701
> 250 3742 656
> 300 4489 596
> 400 5984 552
> 500 7479 513
>
> I have no idea if this is any good for a QuardCore Intel(R) Xeon(R) CPU
>  E5320  @ 1.86GHz with 4GB Ram and 6 SATA disk (7200rpm) in raid 10.
>
> Here is my config (maybe with some odd setting):
> http://pastebin.com/m5d7f5717
>
> I played around with:
> - max_connections
> - shared_buffers

You've got this set to 1/2 your memory (2G).  I've found that for
transactional work it's almost always better to set this much lower
and let the OS do the caching, especially once your db is too big to
fit in memory.  Try setting lowering it and see what happens to your
performance envelope.

> - work_mem
> - maintenance_work_mem
> - checkpoint_segments
> - effective_cache_size

This is set to 3G, but with shared_mem set to 2G, you can't cache more
than 2G, because the OS will just be caching the same stuff as pgsql,
or less.  No biggie.  Just not realistic

> ..but whatever i do, the graph looks the same. Any hints or tips what my
> config should look like? Or are these results even okay? Maybe i am driving
> myself crazy for nothing?

Could be.   What do top and vmstat say during your test run?



view thread (11+ messages)  latest in thread

Message-ID: <dcc563d10903191445y4783462drad14a043af003505@mail.gmail.com>
Permalink:  ../dcc563d10903191445y4783462drad14a043af003505@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10903191445y4783462drad14a043af003505@mail.gmail.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 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-performance@postgresql.org
  Cc: scott.marlowe@gmail.com, ml@bortal.de, gsmith@gregsmith.com
  Subject: Re: Postgres benchmarking with pgbench
  In-Reply-To: <dcc563d10903191445y4783462drad14a043af003505@mail.gmail.com>
  References: <49BE2E84.2040506@bortal.de> <alpine.GSO.2.01.0903161052430.9846@westnet.com> <49C2B854.4080303@bortal.de> <dcc563d10903191445y4783462drad14a043af003505@mail.gmail.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