X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 02D469FA2C7 for ; Tue, 2 May 2006 19:50:17 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 43337-06-2 for ; Tue, 2 May 2006 19:49:55 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.digitalfairway.ca (ns.digitalfairway.ca [207.164.133.170]) by postgresql.org (Postfix) with ESMTP id CD2939FAA6E for ; Tue, 2 May 2006 19:49:55 -0300 (ADT) Received: from toronto.toronto.digitalfairway.ca (unknown [192.168.100.10]) by mail.digitalfairway.ca (Postfix) with ESMTP id 7680F548B2 for ; Tue, 2 May 2006 18:49:53 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by toronto.toronto.digitalfairway.ca (Postfix) with ESMTP id 1E02C144DF8 for ; Tue, 2 May 2006 18:49:53 -0400 (EDT) Received: from toronto.toronto.digitalfairway.ca ([127.0.0.1]) by localhost (toronto.toronto.digitalfairway.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16655-10 for ; Tue, 2 May 2006 18:49:53 -0400 (EDT) Received: from [192.168.0.101] (CPE00119557f5ec-CM000f9faa78f6.cpe.net.cable.rogers.com [70.24.152.86]) (using SSLv3 with cipher EXP1024-RC4-SHA (56/128 bits)) (No client certificate requested) by toronto.toronto.digitalfairway.ca (Postfix) with ESMTP id EAD03144DF7 for ; Tue, 2 May 2006 18:49:52 -0400 (EDT) From: Jan de Visser To: pgsql-performance@postgresql.org Subject: Re: Performance Issues on Opteron Dual Core Date: Tue, 2 May 2006 18:49:48 -0400 User-Agent: KMail/1.9.1 References: <445498AC.10700@paradise.net.nz> <20060502202837.GC97354@pervasive.com> In-Reply-To: <20060502202837.GC97354@pervasive.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200605021849.48613.jdevisser@digitalfairway.com> X-Virus-Scanned: amavisd-new at digitalfairway.ca X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/54 X-Sequence-Number: 18841 On Tuesday 02 May 2006 16:28, Jim C. Nasby wrote: > On Sun, Apr 30, 2006 at 10:59:56PM +1200, Mark Kirkwood wrote: > > Pgadmin can give misleading times for queries that return large result > > sets over a network, due to: > > > > 1/ It takes time to format the (large) result set for display. > > 2/ It has to count the time spent waiting for the (large) result set to > > travel across the network. > > > > You aren't running Pgadmin off the dev server are you? If not check your > > network link to dev and prod - is one faster than the other? (etc). > > > > To eliminate Pgadmin and the network as factors try wrapping your query > > in a 'SELECT count(*) FROM (your query here) AS a', and see if it > > changes anything! > > FWIW, I've found problems running PostgreSQL on Windows in a multi-CPU > environment on w2k3. It runs fine for some period, and then CPU and > throughput drop to zero. So far I've been unable to track down any more > information than that, other than the fact that I haven't been able to > reproduce this on any single-CPU machines. I have had previous correspondence about this with Magnus (search -general= =20 and -hackers). If you uninstall SP1 the problem goes away. We played a bit= =20 with potential fixes but didn't find any. jan =2D-=20 =2D------------------------------------------------------------- Jan de Visser =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 jdevisser@digitalfair= way.com =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Baruk Khazad! Khazad ai-menu! =2D-------------------------------------------------------------