pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matt Clark <matt@ymogen.net>
To: Rod Taylor <rbt@rbt.ca>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Hardware recommendations to scale to silly load
Date: Thu, 28 Aug 2003 17:37:24 +0100
Message-ID: <OAEAKHEHCMLBLIDGAFELIEFFDHAA.matt@ymogen.net> (raw)
In-Reply-To: <1062081711.79027.55.camel@jester>

> Ok.. I would be surprised if you needed much more actual CPU power. I
> suspect they're mostly idle waiting on data -- especially with a Quad
> Xeon (shared memory bus is it not?).

In reality the CPUs get pegged: about 65% PG and 35% system.  But I agree that memory throughput and latency is an issue.

> Write performance won't matter very much. 3000 inserts/second isn't high
> -- some additional battery backed write cache may be useful but not
> overly important with enough ram to hold the complete dataset. I suspect
> those are slow due to things like foreign keys -- which of course are
> selects.

3000 inserts/sec isn't high when they're inside one transaction, but if each is inside its own transaction then that's 3000
commits/second.

> case, additional ram will keep the system from hitting the disk for
> writes as well.

How does that work?

> You may want to play around with checkpoints. Prevention of a checkpoint
> during this hour will help prevent peaks. Be warned though, WAL will
> grow very large, and recovery time should a crash occur could be
> painful.

Good point.  I'll have a think about that.






view thread (45+ messages)  latest in thread

Message-ID: <OAEAKHEHCMLBLIDGAFELIEFFDHAA.matt@ymogen.net>
Permalink:  ../OAEAKHEHCMLBLIDGAFELIEFFDHAA.matt@ymogen.net/
Also on:    postgresql.org/message-id/OAEAKHEHCMLBLIDGAFELIEFFDHAA.matt@ymogen.net

 · 

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-performance@postgresql.org
  Cc: matt@ymogen.net, rbt@rbt.ca
  Subject: Re: Hardware recommendations to scale to silly load
  In-Reply-To: <OAEAKHEHCMLBLIDGAFELIEFFDHAA.matt@ymogen.net>
  References: <1062081711.79027.55.camel@jester> <OAEAKHEHCMLBLIDGAFELIEFFDHAA.matt@ymogen.net>

* 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