From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Luke Lonergan <llonergan(at)greenplum(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: 1 TB of memory |
Date: | 2006-03-17 17:36:53 |
Message-ID: | 20060317173653.GC15742@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, Mar 16, 2006 at 10:44:25PM -0800, Luke Lonergan wrote:
> Jim,
>
> > PostgreSQL tuned to the max and still too slow? Database too big to
> > fit into memory? Here's the solution! http://www.superssd.com/
> > products/tera-ramsan/
>
> With a single 3 Gbyte/second infiniband connection to the device?
>
> You'd be better off with 4 x $10K servers that do 800MB/s from disk each and
> a Bizgres MPP - then you'd do 3.2GB/s (faster than the SSD) at a price 1/10
> of the SSD, and you'd have 24TB of RAID5 disk under you.
>
> Plus - need more speed? Add 12 more servers, and you'd run at 12.8GB/s and
> have 96TB of disk to work with, and you'd *still* spend less on HW and SW
> than the SSD.
Now what happens as soon as you start doing random I/O? :)
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2006-03-17 17:38:27 | Re: Help optimizing a slow index scan |
Previous Message | Steinar H. Gunderson | 2006-03-17 17:20:01 | Re: Background writer configuration |