Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 5DA971337B58 for ; Mon, 20 Dec 2010 02:47:39 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 05597-01 for ; Mon, 20 Dec 2010 06:47:31 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.122]) by mail.postgresql.org (Postfix) with ESMTP id 6E2071337B2F for ; Mon, 20 Dec 2010 02:47:31 -0400 (AST) X-Authority-Analysis: v=1.1 cv=dquaJDitHqzHCdqWSoZ6IgapSuTzW/4TaRYx9N9k4W8= c=1 sm=0 a=8nJEP1OIZ-IA:10 a=RAii6je2cdnAH6ATCOpc6g==:17 a=ILKFzEDYAAAA:8 a=_Ixf_7qHAAAA:8 a=HrUEoev-CmQNJlpbwywA:9 a=P0n_kUs2w8PYIpRLSPMA:7 a=Va2gKBHqJcpcaeyRzf14UnfJYvsA:4 a=wPNLvfGTeEIA:10 a=ryAo9hy1-OkA:10 a=6vsjEBoLwlAA:10 a=0tfO7MgyNwYA:10 a=llswylIc3aAA:10 a=RAii6je2cdnAH6ATCOpc6g==:117 X-Cloudmark-Score: 0 X-Originating-IP: 74.73.87.196 Received: from [74.73.87.196] ([74.73.87.196:50015] helo=[192.168.1.103]) by hrndva-oedge01.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id E5/04-14011-20CFE0D4; Mon, 20 Dec 2010 06:47:30 +0000 Message-ID: <4D0EFC02.7040004@vmsinfo.com> Date: Mon, 20 Dec 2010 01:47:30 -0500 From: Mladen Gogala User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: James Cloos CC: Royce Ausburn , "pgsql-performance@postgresql.org" Subject: Re: CPU bound References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201012/248 X-Sequence-Number: 41700 On 12/19/2010 7:57 PM, James Cloos wrote: >>>>>> "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 Good time accounting is the most compelling reason for having a wait event interface, like Oracle. Without the wait event interface, one cannot really tell where the time is spent, at least not without profiling the database code, which is not an option for a production database. -- Mladen Gogala Sr. Oracle DBA 1500 Broadway New York, NY 10036 (212) 329-5251 www.vmsinfo.com