From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Ron Peacetree <rjpeace@earthlink.net>
Cc: Frank Wiles <frank@wiles.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Some help on buffers and other performance tricks
Date: Thu, 10 Nov 2005 09:16:10 -0600
Message-ID: <1131635770.3554.58.camel@state.g2switchworks.com> (raw)
In-Reply-To: <1793468.1131596410309.JavaMail.root@elwamui-hound.atl.sa.earthlink.net>
References: <1793468.1131596410309.JavaMail.root@elwamui-hound.atl.sa.earthlink.net>
On Wed, 2005-11-09 at 22:20, Ron Peacetree wrote:
> The point Gentlemen, was that Good Architecture is King. That's what I was trying to emphasize by calling proper DB architecture step 0. All other things being equal (and they usually aren't, this sort of stuff is _very_ context dependent), the more of your critical schema that you can fit into RAM during normal operation the better.
>
> ...and it all starts with proper DB design. Otherwise, you are quite right in stating that you risk wasting time, effort, and HW.
Very valid point. It's the reason, in my last job, we had a mainline
server with dual 2800MHz CPUs and a big RAID array.
And our development, build and test system was a Dual Pentium Pro 200
with 256 Meg of ram. You notice slow queries real fast on such a box.
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: smarlowe@g2switchworks.com, rjpeace@earthlink.net, frank@wiles.org
Subject: Re: Some help on buffers and other performance tricks
In-Reply-To: <1131635770.3554.58.camel@state.g2switchworks.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