From: Scott Carey <scott@richrelevance.com>
To: jd@commandprompt.com <jd@commandprompt.com>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Jean-David Beyer <jeandavid8@verizon.net>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Need help with 8.4 Performance Testing
Date: Tue, 9 Dec 2008 14:05:18 -0800
Message-ID: <C5642B9E.F8A%scott@richrelevance.com> (raw)
In-Reply-To: <1228854042.13962.91.camel@jd-laptop.pragmaticzealot.org>
Which brings this back around to the point I care the most about:
I/O per second will diminish as the most common database performance limiting factor in Postgres 8.4's lifetime, and become almost irrelevant in 8.5's.
Becoming more CPU efficient will become very important, and for some, already is. The community needs to be proactive on this front.
This turns a lot of old assumptions on their head, from the database down through the OS and filesystem. We're bound to run into many surprises due to this major shift in something that has had its performance characteristics taken for granted for decades.
> On 12/9/08 12:20 PM, "Joshua D. Drake" <jd@commandprompt.com> wrote:
> > So, at least in relative terms, 15k sas drives are not 'fast'. They
> > are terribly, awfully, painfully slow. They are also not cheap in
> > terms of $/IOPS. The end is near.
> >
> No doubt about it. I give it 24 months tops.
>
> Joshua D. Drake
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: scott@richrelevance.com, jd@commandprompt.com, mmoncure@gmail.com, scott.marlowe@gmail.com, jeandavid8@verizon.net
Subject: Re: Need help with 8.4 Performance Testing
In-Reply-To: <C5642B9E.F8A%scott@richrelevance.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