From: James Cloos <cloos@jhcloos.com>
To: Royce Ausburn <royce@inomial.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: CPU bound
Date: Sun, 19 Dec 2010 19:57:48 -0500
Message-ID: <m38vzl6z17.fsf@jhcloos.com> (raw)
In-Reply-To: <F13DEE85-D114-4761-AD4D-924F1A741ACC@inomial.com>
References: <F13DEE85-D114-4761-AD4D-924F1A741ACC@inomial.com>
>>>>> "RA" == Royce Ausburn <royce@inomial.com> writes:
RA> I notice that when restoring a DB on a laptop with an SDD,
RA> typically postgres is maxing out a CPU - even during a COPY.
The time the CPUs spend waiting on system RAM shows up as CPU
time, not as Wait time. It could be just that the SSD is fast
enough that the RAM is now the bottleneck, although parsing
and text<=>binary conversions (especially for integers, reals
and anything stored as an integer) also can be CPU-intensive.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
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: cloos@jhcloos.com, royce@inomial.com
Subject: Re: CPU bound
In-Reply-To: <m38vzl6z17.fsf@jhcloos.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