pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Michael D. Sofka <sofkam@rpi.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: Server Hardware Configuration
Date: Mon, 21 Nov 2005 11:12:25 -0600
Message-ID: <20051121171225.GU19279@pervasive.com> (raw)
In-Reply-To: <CD54090BD5C5F87C1B2A7F3C@betelgeuse.cct.rpi.edu>
References: <s37e6ec8.029@fs3.ft.fo>
	<CD54090BD5C5F87C1B2A7F3C@betelgeuse.cct.rpi.edu>

On Mon, Nov 21, 2005 at 09:41:36AM -0500, Michael D. Sofka wrote:
> >I suggest looking at your current bottleneck first.
> >It's likely to be the most cost-efficient route out.
> 
> I/O is our bottleneck.  The machine is not CPU loaded.  And, in fact,
> our current performance is good.  The machine upgrade is planned with a
> service upgrade.  Current hardware is old, and so getting more expensive
> to support.  We also anticipate service growth (read, more spam), and
> so are planning accordingly.

Which, as I mentioned, is why RAID5 is not a good solution if you're
doing any writes at all.

You're talking about a 16G database that you expect to grow to 64G. That
would fit happily in a RAID1 (mirror) of two SCSI 72G drives. I haven't
priced that kind of stuff out recently, but I believe you're looking at
$300-$500. If that doesn't provide enough performance, go to a RAID10
and add more drives. If you're doing much writing at all, spring for a
battery-backed controller so you can enable write caching.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (16+ messages)  latest in thread

Message-ID: <20051121171225.GU19279@pervasive.com>
Permalink:  ../20051121171225.GU19279@pervasive.com/
Also on:    postgresql.org/message-id/20051121171225.GU19279@pervasive.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 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: jnasby@pervasive.com, sofkam@rpi.edu
  Subject: Re: Server Hardware Configuration
  In-Reply-To: <20051121171225.GU19279@pervasive.com>
  References: <s37e6ec8.029@fs3.ft.fo> <CD54090BD5C5F87C1B2A7F3C@betelgeuse.cct.rpi.edu> <20051121171225.GU19279@pervasive.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