pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Fred Moyer <fred@redhotpenguin.com>
To: 'Sean Shanny' <shannyconsulting@earthlink.net>
To: pgsql-performance@postgresql.org
Subject: Re: Has anyone run on the new G5 yet
Date: Wed, 3 Dec 2003 14:35:45 -0800
Message-ID: <000001c3b9ed$cb1bf2a0$0300a8c0@harpua> (raw)
In-Reply-To: <3FCE5B85.9000406@earthlink.net>

> We are running into issues with IO saturation obviously.  Since this
> thing is only going to get bigger we are looking for some advice on 
> how to accommodate DB's of this size.
<snip>
> Second and more radical, has anyone run 
> postgreSQL on the new Apple G5 with an XRaid system?  This seems like 
> a great value combination.  Fast CPU, wide bus, Fibre Channel IO, 
> 2.5TB all for ~17k.
<snip>
If you are going for I/O performance you are best off with one of the
Xserve competitors listed at http://www.apple.com/xserve/raid/.  The
Xserve is based on IDE drives which have a lower seek time (say 8.9 ms)
compared to scsi (3.6 ms for seagate cheetah).  For small random
read/write operations (like databases) this will give you a noticable
improvement in performance over ide drives.  Also make sure to get as
many drives as possible, more spindles equals better I/O performance.

> I keep see references to terabyte postgreSQL installations, I was
> wondering if anyone on this list is in charge of one of those and can 
> offer some advice on how to position ourselves hardware wise.

I've gone to about half terabyte size and all I can say is you should
plan for at least one quarter to one half a rack of drivespace (assuming
14 drives per 4u that's 42 to 84 drives).  Do yourself a favor and get
more rather than less, you will really appreciate it.  I averaged about
2 mb/s average per drive via the raid controller stats on 14 drive array
during I/O bound seek and update operations in 2 raid 10 arrays (half
xlogs and half data).  That comes out to around 2 hours for a terabyte
with 70 drives assuming a constant scaling.  You may be able to get more
or less depending on your setup and query workload.

> Thanks.
>
> --sean
>
>
> ---------------------------(end of 
> broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>      subscribe-nomail command to majordomo@postgresql.org so that your
>      message can get through to the mailing list cleanly
>


---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faqs/FAQ.html




view thread (9+ messages)  latest in thread

Message-ID: <000001c3b9ed$cb1bf2a0$0300a8c0@harpua>
Permalink:  ../000001c3b9ed$cb1bf2a0$0300a8c0@harpua/
Also on:    postgresql.org/message-id/000001c3b9ed$cb1bf2a0$0300a8c0@harpua

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: fred@redhotpenguin.com, shannyconsulting@earthlink.net
  Subject: Re: Has anyone run on the new G5 yet
  In-Reply-To: <000001c3b9ed$cb1bf2a0$0300a8c0@harpua>

* 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