pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: William Yu <wyu@talisys.com>
To: pgsql-admin@postgresql.org
Subject: Re: New system recommendations
Date: Thu, 27 Apr 2006 00:34:14 -0700
Message-ID: <e2ps5l$27c8$1@news.hub.org> (raw)
In-Reply-To: <8511B4970E0D124898E973DF496F9B432515CF@stash.stackdump.local>
References: <8511B4970E0D124898E973DF496F9B432515CF@stash.stackdump.local>

Benjamin Krajmalnik wrote:
> We are currently inserting about 1 million rows per day, and will 
> increase to probably 5 million once it goes into full deployment.
> 
> It is currently running on a 3GHz Xeon HT, 2GB RAM, dual 72GB disks 
> running RAID 1.  This server is a 1U without only 2 drive bays, so I 
> have a potential issue with drive space.
> 
> As a result, I will be moving the db server to a Dell 1650 with 3 146GB 
> SCSI drives running RAID 0.  System is a dual processor, 1.2GHz, with 
> 4GB RAM.

I'm assuming you've already optimized your code with all the necessary 
tricks for maximum insert/update performance because your disk upgrade 
plan is rather underwhelming. 3X the disk bandwidth (3dr-RAID0 versus 
2dr-RAID1) won't even keep pace with your expected 5X increased volume. 
Anytime you do a system upgrade, you always have to plan to handle many 
times the current projected volume so you don't have to upgrade yet 
again next year.

Go nuts -- get as many disks as you can afford. Get as much onboard 
cache as you can afford. If number of drive bays is an issue, I'd get a 
separate case/rackmount and run external scsi/sata cables to it.



view thread (15+ messages)  latest in thread

Message-ID: <e2ps5l$27c8$1@news.hub.org>
Permalink:  ../e2ps5l$27c8$1@news.hub.org/
Also on:    postgresql.org/message-id/e2ps5l$27c8$1@news.hub.org

 · 

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: wyu@talisys.com
  Subject: Re: New system recommendations
  In-Reply-To: <e2ps5l$27c8$1@news.hub.org>
  References: <8511B4970E0D124898E973DF496F9B432515CF@stash.stackdump.local> <e2ps5l$27c8$1@news.hub.org>

* 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