Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 420561337BF4 for ; Sun, 19 Dec 2010 21:12:02 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 73066-02 for ; Mon, 20 Dec 2010 01:11:55 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from eagle.jhcloos.com (eagle.jhcloos.com [207.210.242.212]) by mail.postgresql.org (Postfix) with ESMTP id 75F331337BA8 for ; Sun, 19 Dec 2010 21:11:44 -0400 (AST) Received: by eagle.jhcloos.com (Postfix, from userid 10) id B55284025D; Mon, 20 Dec 2010 01:11:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jhcloos.com; s=eagle; t=1292807503; bh=KABljou19C0QajjJgx584GTNvNXnovYgxjaUVHeX4U4=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=Vgz6S3cw9V1RNIZns/t4dZ80t+jnwqwscy/sD0S7mx+ad/LS56HUxIC3kU0R2gfi6 20VvO4l7PrHMq7EnmvZlFxu8irMRp4yBcUGMYPEL5XdjwQfpcI5xmilCp2UuIG+SQi HnnnPokW2EUIvL0MUZ9ox1CPIafXC7XlTzWpmxuI= Received: from carbon (localhost [127.0.0.1]) by carbon.jhcloos.org (Postfix) with ESMTP id 3FD4330002A; Mon, 20 Dec 2010 00:57:48 +0000 (UTC) From: James Cloos To: Royce Ausburn Cc: pgsql-performance@postgresql.org Subject: Re: CPU bound In-Reply-To: (Royce Ausburn's message of "Mon, 13 Dec 2010 13:43:10 +1100") References: User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) Face: iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAABHNCSVQICAgIfAhkiAAAAI1J REFUOE+lU9ESgCAIg64P1y+ngUdxhl5H8wFbbM0OmUiEhKkCYaZThXCo6KE5sCbA1DDX3genvO4d eBQgEMaM5qy6uWk4SfBYfdu9jvBN9nSVDOKRtwb+I3epboOsOX5pZbJNsBJFvmQQ05YMfieIBnYX FK2N6dOawd97r/e8RjkTLzmMsiVgrAoEugtviCM3v2WzjgAAAABJRU5ErkJggg== Copyright: Copyright 2009 James Cloos OpenPGP: ED7DAEA6; url=http://jhcloos.com/public_key/0xED7DAEA6.asc OpenPGP-Fingerprint: E9E9 F828 61A4 6EA9 0F2B 63E7 997A 9F17 ED7D AEA6 Date: Sun, 19 Dec 2010 19:57:48 -0500 Message-ID: Lines: 14 MIME-Version: 1.0 Content-Type: text/plain X-Hashcash: 1:30:101220:royce@inomial.com::s3Ib1+XWm7t2BECU:0000000000000000000000000000000000000000000DuGpo X-Hashcash: 1:30:101220:pgsql-performance@postgresql.org::M/skau3idvbL5Qad:0000000000000000000000000000tf4u3 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201012/247 X-Sequence-Number: 41699 >>>>> "RA" == Royce Ausburn 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 OpenPGP: 1024D/ED7DAEA6