From: Luke Lonergan <llonergan@greenplum.com>
To: stange@rentec.com, "Greg Stark" <gsstark@mit.edu>
Cc: Dave Cramer <pg@fastcrypt.com>
Cc: Joshua Marsh <icub3d@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hardware/OS recommendations for large databases (
Date: Sat, 19 Nov 2005 08:13:09 -0800
Message-ID: <BFA48F15.14182%llonergan@greenplum.com> (raw)
In-Reply-To: <437E2DF2.50906@rentec.com>
Alan,
On 11/18/05 11:39 AM, "Alan Stange" <stange@rentec.com> wrote:
> Yes and no. The one cpu is clearly idle. The second cpu is 40% busy
> and 60% idle (aka iowait in the above numbers).
The "aka iowait" is the problem here - iowait is not idle (otherwise it
would be in the "idle" column).
Iowait is time spent waiting on blocking io calls. As another poster
pointed out, you have a two CPU system, and during your scan, as predicted,
one CPU went 100% busy on the seq scan. During iowait periods, the CPU can
be context switched to other users, but as I pointed out earlier, that's not
useful for getting response on decision support queries.
Thanks for your data, it exemplifies many of the points brought up:
- Lots of disks and expensive I/O hardware does not help improve performance
on large table queries because I/O bandwidth does not scale beyond
110-120MB/s on the fastest CPUs
- OLTP performance optimizations are different than decision support
Regards,
- 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, gsstark@mit.edu, pg@fastcrypt.com, icub3d@gmail.com
Subject: Re: Hardware/OS recommendations for large databases (
In-Reply-To: <BFA48F15.14182%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