From: Royce Ausburn <royce@inomial.com>
To: pgsql-performance@postgresql.org
Subject: CPU bound
Date: Mon, 13 Dec 2010 13:43:10 +1100
Message-ID: <F13DEE85-D114-4761-AD4D-924F1A741ACC@inomial.com> (raw)
Hi all,
I notice that when restoring a DB on a laptop with an SDD, typically postgres is maxing out a CPU - even during a COPY. I wonder, what is postgres usually doing with the CPU? I would have thought the disk would usually be the bottleneck in the DB, but occasionally it's not. We're embarking on a new DB server project and it'd be helpful to understand where the CPU is likely to be the bottleneck.
Cheers,
--Royce
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: royce@inomial.com
Subject: Re: CPU bound
In-Reply-To: <F13DEE85-D114-4761-AD4D-924F1A741ACC@inomial.com>
References: <F13DEE85-D114-4761-AD4D-924F1A741ACC@inomial.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