From: Alex Turner <armtuk@gmail.com>
To: Steve Poe <spoe@sfnet.cc>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to improve db performance with $7K?
Date: Mon, 18 Apr 2005 14:19:36 -0400
Message-ID: <33c6269f05041811191e5047fd@mail.gmail.com> (raw)
In-Reply-To: <4263F259.7030804@sfnet.cc>
References: <CC74E7E10A8A054798B6611BD1FEF4D30625DA5B@vamail01.thexchange.com>
<425EBA0C.6030804@sfnet.cc>
<d3vpnn$2iu$1@news.hub.org>
<87pswsku6e.fsf@stark.xeocode.com>
<33c6269f0504180817511b27a3@mail.gmail.com>
<878y3gks3p.fsf@stark.xeocode.com>
<33c6269f05041809566abf91d2@mail.gmail.com>
<4263F259.7030804@sfnet.cc>
I think the add more disks thing is really from the point of view that
one disk isn't enough ever. You should really have at least four
drives configured into two RAID 1s. Most DBAs will know this, but
most average Joes won't.
Alex Turner
netEconomist
On 4/18/05, Steve Poe <spoe@sfnet.cc> wrote:
> Alex,
>
> In the situation of the animal hospital server I oversee, their
> application is OLTP. Adding hard drives (6-8) does help performance.
> Benchmarks like pgbench and OSDB agree with it, but in reality users
> could not see noticeable change. However, moving the top 5/10 tables and
> indexes to their own space made a greater impact.
>
> Someone who reads PostgreSQL 8.0 Performance Checklist is going to see
> point #1 add more disks is the key. How about adding a subpoint to
> explaining when more disks isn't enough or applicable? I maybe
> generalizing the complexity of tuning an OLTP application, but some
> clarity could help.
>
> Steve Poe
>
>
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: armtuk@gmail.com, spoe@sfnet.cc
Subject: Re: How to improve db performance with $7K?
In-Reply-To: <33c6269f05041811191e5047fd@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