From: Joshua Marsh <icub3d@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: Hardware/OS recommendations for large databases (
Date: Thu, 17 Nov 2005 13:58:46 -0700
Message-ID: <38242de90511171258v22f334f3ua474a8aa99bdc29d@mail.gmail.com> (raw)
In-Reply-To: <dlipnh$902$1@news.hub.org>
References: <3E37B936B592014B978C4415F90D662D01995F7B@MI8NYCMAIL06.Mi8.com>
<33c6269f0511152115v1a34ab81j30f1f5df5a6c6956@mail.gmail.com>
<dlfjgf$41b$1@news.hub.org>
<33c6269f0511171148q7ea67482xd595ea5717956aa2@mail.gmail.com>
<dlipnh$902$1@news.hub.org>
On 11/17/05, William Yu <wyu@talisys.com> wrote:
>
> > No argument there. But it's pointless if you are IO bound.
>
> Why would you just accept "we're IO bound, nothing we can do"? I'd do
> everything in my power to make my app go from IO bound to CPU bound --
> whether by optimizing my code or buying more hardware. I can tell you if
> our OLTP servers were IO bound, it would run like crap. Instead of < 1
> sec, we'd be looking at 5-10 seconds per "user transaction" and our
> users would be screaming bloody murder.
>
> In theory, you can always convert your IO bound DB to CPU bound by
> stuffing more and more RAM into your server. (Or partitioning the DB
> across multiple servers.) Whether it's cost effective depends on the DB
> and how much your users are paying you -- and that's a case-by-case
> analysis. Not a global statement of "IO-bound, pointless".
We all want our systems to be CPU bound, but it's not always possible.
Remember, he is managing a 5 TB Databse. That's quite a bit different than a
100 GB or even 500 GB database.
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: icub3d@gmail.com
Subject: Re: Hardware/OS recommendations for large databases (
In-Reply-To: <38242de90511171258v22f334f3ua474a8aa99bdc29d@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