Re: Hardware/OS recommendations for large databases (

From: "Luke Lonergan" <LLonergan(at)greenplum(dot)com>
To: dlang(at)invendra(dot)net
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Hardware/OS recommendations for large databases (
Date: 2005-11-27 08:02:48
Message-ID: 3E37B936B592014B978C4415F90D662DE11EBD@MI8NYCMAIL06.Mi8.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Have you factored in how long it takes to build an index on 5TB? And the index size?

Really, it's a whole different world at multi-TB, everything has to scale.

Btw we don't just scan in parallel, we do all in parallel, check the sort number on this thread. Mpp is for the god box too.

And your price is wrong - but if you want free then you'll have to find another way to get your work done.

- Luke
- Luke
--------------------------
Sent from my BlackBerry Wireless Device

-----Original Message-----
From: David Lang <dlang(at)invendra(dot)net>
To: Luke Lonergan <LLonergan(at)greenplum(dot)com>
CC: pgsql-performance(at)postgresql(dot)org <pgsql-performance(at)postgresql(dot)org>
Sent: Sat Nov 26 14:34:14 2005
Subject: Re: [PERFORM] Hardware/OS recommendations for large databases (

On Sun, 27 Nov 2005, Luke Lonergan wrote:

> For data warehousing its pretty well open and shut. To use all cpus and
> io channels on each query you will need mpp.
>
> Has anyone done the math.on the original post? 5TB takes how long to
> scan once? If you want to wait less than a couple of days just for a
> seq scan, you'd better be in the multi-gb per second range.

if you truely need to scan the entire database then you are right, however
indexes should be able to cut the amount you need to scan drasticly.

David Lang

Browse pgsql-performance by date

  From Date Subject
Next Message David Lang 2005-11-27 11:08:17 Re: Open request for benchmarking input
Previous Message Luke Lonergan 2005-11-27 06:18:54 Re: Hardware/OS recommendations for large databases (