pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Mair <chrisnospam@1006.org>
To: Benjamin Krajmalnik <kraj@illumen.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Performance tuning question
Date: Tue, 08 Aug 2006 11:17:15 +0200
Message-ID: <1155028635.4467.11.camel@dell.home.lan> (raw)
In-Reply-To: <BF337097BDD9D849A2F4B818DDB279872525A6@stash.stackdump.local>
References: <BF337097BDD9D849A2F4B818DDB279872525A6@stash.stackdump.local>


> I just finished running some benchmarks on an underpowered server
> compared to the one I am running in production.
> My initial tests were run on an ampty database, pg_xlog on the same
> spindle.
> Stored procedure execution speed was ~15 ms.
> 
> I then restored the production database so I would have ~3GB database.
> Execution time for the stored procedure went up to about 40 ms average
> (with a miuch higher variance), but with a processing speed of 18 stored
> procedure calls per second.
> 
> I them moved pg_xlog to a separate spindle.
> Execution time went down to about 17 ms

Good!


> Beyond moving pg_xlog to a separate spindle, are there any other things
> you can think of which may improve the performance?

You could bundle more work into a single transaction.

I don't know what your call is doing, but 1 call that does 20 inserts in
a transaction is certainly more efficient than 2 calls doing two
transactions with 10 inserts each. If you can use bigger bundles of
work, do that.

Maybe reasoning in "MByte (or whatever) per second" rather than "time to
do a small piece of the work" helps. Otherwise you're into real time
stuff and RDBMS' and real time stuff don't mix well.

Bye :)
Chris.


-- 

Chris Mair
http://www.1006.org





view thread (7+ messages)  latest in thread

Message-ID: <1155028635.4467.11.camel@dell.home.lan>
Permalink:  ../1155028635.4467.11.camel@dell.home.lan/
Also on:    postgresql.org/message-id/1155028635.4467.11.camel@dell.home.lan

 · 

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: chrisnospam@1006.org, kraj@illumen.com
  Subject: Re: Performance tuning question
  In-Reply-To: <1155028635.4467.11.camel@dell.home.lan>
  References: <BF337097BDD9D849A2F4B818DDB279872525A6@stash.stackdump.local> <1155028635.4467.11.camel@dell.home.lan>

* 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