pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Steve Atkins <steve@blighty.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance suggestions for an update-mostly database?
Date: Mon, 4 Oct 2004 10:38:14 -0700
Message-ID: <200410041038.14571.josh@agliodbs.com> (raw)
In-Reply-To: <20041004174019.GA25671@gp.word-to-the-wise.com>
References: <20041004174019.GA25671@gp.word-to-the-wise.com>

Steve,

> I'm used to performance tuning on a select-heavy database, but this
> will have a very different impact on the system. Does anyone have any
> experience with an update heavy system, and have any performance hints
> or hardware suggestions?

Minimal/no indexes on the table(s).    Raise checkpoint_segments and consider 
using commit_siblings/commit_delay if it's a multi-stream application.   
Figure out ways to do inserts instead of updates where possible, and COPY 
instead of insert, where possible.  Put your WAL on its own disk resource.

I'm a little curious as to what kind of app would be 95% writes.  A log?

-- 
Josh Berkus
Aglio Database Solutions
San Francisco



view thread (5+ messages)  latest in thread

Message-ID: <200410041038.14571.josh@agliodbs.com>
Permalink:  ../200410041038.14571.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200410041038.14571.josh@agliodbs.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: josh@agliodbs.com, steve@blighty.com
  Subject: Re: Performance suggestions for an update-mostly database?
  In-Reply-To: <200410041038.14571.josh@agliodbs.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