From: Luke Lonergan <llonergan@greenplum.com>
To: Alex Turner <armtuk@gmail.com>
Cc: Dave Cramer <pg@fastcrypt.com>
Cc: Greg Stark <gsstark@mit.edu>
Cc: Joshua Marsh <icub3d@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hardware/OS recommendations for large databases (
Date: Fri, 18 Nov 2005 08:33:35 -0800
Message-ID: <BFA3425F.1405B%llonergan@greenplum.com> (raw)
In-Reply-To: <33c6269f0511180828m3bc7f41dp186b4573792bf6a0@mail.gmail.com>
Alex,
On 11/18/05 8:28 AM, "Alex Turner" <armtuk@gmail.com> wrote:
> Ok - so I ran the same test on my system and get a total speed of
113MB/sec.
> Why is this? Why is the system so limited to around just
110MB/sec? I
> tuned read ahead up a bit, and my results improve a
bit..
OK! Now we're on the same page. Finally someone who actually tests!
Check the CPU usage while it's doing the scan. Know what it's doing?
Memory copies. We've profiled it extensively.
So - that's the suckage - throwing more CPU power helps a bit, but the
underlying issue is poorly optimized code in the Postgres executor and lack
of I/O asynchrony.
- Luke
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: llonergan@greenplum.com, armtuk@gmail.com, pg@fastcrypt.com, gsstark@mit.edu, icub3d@gmail.com
Subject: Re: Hardware/OS recommendations for large databases (
In-Reply-To: <BFA3425F.1405B%llonergan@greenplum.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