From: Rodrigo Madera <rodrigo.madera@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: 1 TB of memory
Date: Fri, 17 Mar 2006 05:38:14 -0800
Message-ID: <3cf983d0603170538s788b46b3saeec119a0fd0cce5@mail.gmail.com> (raw)
In-Reply-To: <20060317123121.GO15140@mathom.us>
References: <8B16F5C8-DFC8-4694-902C-AE584E490530@pervasive.com>
<C03F9AC9.1F5EE%llonergan@greenplum.com>
<20060317123121.GO15140@mathom.us>
For God's sake buy a mainframe! =o)
On 3/17/06, Michael Stone <mstone+postgres@mathom.us> wrote:
> On Thu, Mar 16, 2006 at 10:44:25PM -0800, Luke Lonergan wrote:
> >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.
>
> Except, of course, that your solution doesn't have a seek time of zero.
> That approach is great for applications that are limited by their
> sequential scan speed, not so good for applications with random access.
> At 3.2 GB/s it would still take over 5 minutes to seqscan a TB, so you'd
> probably want some indices--and you're not going to be getting 800MB/s
> per system doing random index scans from rotating disk (but you might
> with SSD). Try not to beat your product drum quite so loud...
>
> Mike Stone
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
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: rodrigo.madera@gmail.com
Subject: Re: 1 TB of memory
In-Reply-To: <3cf983d0603170538s788b46b3saeec119a0fd0cce5@mail.gmail.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