Re: Performance suggestions for an update-mostly database?

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Steve Atkins <steve(at)blighty(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Performance suggestions for an update-mostly database?
Date: 2004-10-04 17:38:14
Message-ID: 200410041038.14571.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Steve Atkins 2004-10-04 17:40:19 Performance suggestions for an update-mostly database?
Previous Message Patrick Hatcher 2004-10-04 17:14:13 Re: Slow update/insert process