Re: Performance suggestions for an update-mostly database? - Mailing list pgsql-performance

From Jim C. Nasby
Subject Re: Performance suggestions for an update-mostly database?
Date
Msg-id 20041004192254.GT1297@decibel.org
Whole thread Raw
In response to Re: Performance suggestions for an update-mostly database?  (Josh Berkus <josh@agliodbs.com>)
List pgsql-performance
And obviously make sure you're vacuuming frequently.

On Mon, Oct 04, 2004 at 10:38:14AM -0700, Josh Berkus wrote:
> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>

--
Jim C. Nasby, Database Consultant               decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"

pgsql-performance by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Caching of Queries
Next
From: Miles Keaton
Date:
Subject: would number of fields in a table affect search-query time?