From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Carey <scott@richrelevance.com>
Cc: jd@commandprompt.com <jd@commandprompt.com>
Cc: 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, 09 Dec 2008 17:38:35 -0500
Message-ID: <22285.1228862315@sss.pgh.pa.us> (raw)
In-Reply-To: <C5642B9E.F8A%scott@richrelevance.com>
References: <C5642B9E.F8A%scott@richrelevance.com>
Scott Carey <scott@richrelevance.com> writes:
> 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.
Hmm ... I wonder whether this means that the current work on
parallelizing I/O (the posix_fadvise patch in particular) is a dead
end. Because what that is basically going to do is expend more CPU
to improve I/O efficiency. If you believe this thesis then that's
not the road we want to go down.
regards, tom lane
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: tgl@sss.pgh.pa.us, 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: <22285.1228862315@sss.pgh.pa.us>
* 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