From: Alan Stange <stange@rentec.com>
Cc: Dave Cramer <pg@fastcrypt.com>
Cc: Luke Lonergan <llonergan@greenplum.com>
Cc: Greg Stark <gsstark@mit.edu>
Cc: Joshua Marsh <icub3d@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hardware/OS recommendations for large databases (
Date: Fri, 18 Nov 2005 08:41:58 -0500
Message-ID: <437DDA26.4000603@rentec.com> (raw)
In-Reply-To: <437DD5A1.1090605@archonet.com>
References: <BFA2AFBA.13FC4%llonergan@greenplum.com>
<0F3B99E2-4575-42B8-8AAC-3FE4B231348C@fastcrypt.com>
<437DD5A1.1090605@archonet.com>
Richard Huxton wrote:
> Dave Cramer wrote:
>>
>> On 18-Nov-05, at 1:07 AM, Luke Lonergan wrote:
>>
>>> Postgres + Any x86 CPU from 2.4GHz up to Opteron 280 is CPU bound
>>> after
>>> 110MB/s of I/O. This is true of Postgres 7.4, 8.0 and 8.1.
>>>
>>> A $1,000 system with one CPU and two SATA disks in a software RAID0
>>> will
>>> perform exactly the same as a $80,000 system with 8 dual core CPUs
>>> and the
>>> world's best SCSI RAID hardware on a large database for decision
>>> support
>>> (what the poster asked about).
>>
>>
>> Now there's an interesting line drawn in the sand. I presume you
>> have numbers to back this up ?
>>
>> This should draw some interesting posts.
That's interesting, as I occasionally see more than 110MB/s of
postgresql IO on our system. I'm using a 32KB block size, which has
been a huge win in performance for our usage patterns. 300GB database
with a lot of turnover. A vacuum analyze now takes about 3 hours, which
is much shorter than before. Postgresql 8.1, dual opteron, 8GB memory,
Linux 2.6.11, FC drives.
-- Alan
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: stange@rentec.com, pg@fastcrypt.com, llonergan@greenplum.com, gsstark@mit.edu, icub3d@gmail.com
Subject: Re: Hardware/OS recommendations for large databases (
In-Reply-To: <437DDA26.4000603@rentec.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