From: John Lister <john.lister@kickstone.com>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Comparative tps question
Date: Tue, 04 Dec 2012 16:30:43 +0000
Message-ID: <50BE2533.5050101@kickstone.com> (raw)
In-Reply-To: <CAHyXU0zqN=xaRLM_uKZAfKWFGnSK6ROKfPMgE0rhmQCORoOD2A@mail.gmail.com>
References: <50B659EC.4080509@kickstone.com>
<CAHyXU0xasEPfQ7d8N=0zH5i_N+Giid8x2rUdNHzabSqu8mBwYA@mail.gmail.com>
<50B793C5.3070806@kickstone.com>
<CAHyXU0zqN=xaRLM_uKZAfKWFGnSK6ROKfPMgE0rhmQCORoOD2A@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 29/11/2012 17:33, Merlin Moncure wrote:
> one thing that immediately jumps out here is that your wal volume
> could be holding you up. so it's possible we may want to move wal to
> the ssd volume. if you can scrounge up a 9.2 pgbench, we can gather
> more evidence for that by running pgbench with the "--unlogged-tables"
> option, which creates the tables unlogged so that they are not wal
> logged (for the record, this causes tables to be truncated when not
> shut down in clean state).
Ok, got myself a 9.2 version of pgbench and run it a few times on
unlogged tables...
changing the number of threads has maybe a 5% change in values which
isn't probably too much to worry about.
-j 25 -c 100 -s 100 gives a tps of around 10.5k
using -N ups that to around 20k
using -S ups that again to around 40k
I'll have to wait until I get to shut the db down again to try the wal
on an ssd. Although unless I did something wrong it didn't seem to make
a huge difference before....
During these tests, iowait dropped to almost 0, user and sys stayed
around the same (60% and 20% respectively). although the disk traffic
was only in the 10s of Mb/s which seems very low - unless there is some
wierd caching going on and it gets dumped at a later date?
John
--
Get the PriceGoblin Browser Addon
www.pricegoblin.co.uk
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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: john.lister@kickstone.com, mmoncure@gmail.com
Subject: Re: Comparative tps question
In-Reply-To: <50BE2533.5050101@kickstone.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