From: Merlin Moncure <mmoncure@gmail.com>
To: Rodrigo Madera <rodrigo.madera@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: 1 TB of memory
Date: Fri, 17 Mar 2006 09:57:36 -0500
Message-ID: <b42b73150603170657k3b32705do9adb4ca64f10ea21@mail.gmail.com> (raw)
In-Reply-To: <3cf983d0603170625k370b4d29rcbdd5c7015fc18fa@mail.gmail.com>
References: <8B16F5C8-DFC8-4694-902C-AE584E490530@pervasive.com>
<b42b73150603170555l758cef81haa0e9f1d18ee24a0@mail.gmail.com>
<3cf983d0603170625k370b4d29rcbdd5c7015fc18fa@mail.gmail.com>
On 3/17/06, Rodrigo Madera <rodrigo.madera@gmail.com> wrote:
> I don't know about you databasers that crunch in some selects, updates
> and deletes, but my personal developer workstation is planned to be a
> 4x 300GB SATA300 with a dedicated RAID stripping controller (no
> checksums, just speedup) and 4x AMD64 CPUs... not to mention 2GB for
> each processor... all this in a nice server motherboard...
no doubt, that will handle quite a lot of data. in fact, most
databases (contrary to popular opinion) are cpu bound, not i/o bound.
However, at some point a different set of rules come into play. This
point is constantly chaning due to the relentless march of hardware
but I'd suggest that at around 1TB you can no longer count on things
to run quickly just depending on o/s file caching to bail you out.
Or, you may have a single table + indexes thats 50 gb that takes 6
hours to vacuum sucking all your i/o.
another useful aspect of SSD is the relative value of using system
memory is much less, so you can reduce swappiness and tune postgres to
rely more on the filesystem and give all your memory to work_mem and
such.
merlin
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: mmoncure@gmail.com, rodrigo.madera@gmail.com
Subject: Re: 1 TB of memory
In-Reply-To: <b42b73150603170657k3b32705do9adb4ca64f10ea21@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