| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Ron Peacetree <rjpeace(at)earthlink(dot)net> |
| Cc: | Frank Wiles <frank(at)wiles(dot)org>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Some help on buffers and other performance tricks |
| Date: | 2005-11-10 15:16:10 |
| Message-ID: | 1131635770.3554.58.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frank Wiles | 2005-11-10 15:25:01 | Re: Some help on buffers and other performance tricks |
| Previous Message | Michael Stone | 2005-11-10 14:43:09 | Re: WAL sync behaviour |