X-Original-To: pgsql-hackers-win32-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id BCFCD56388; Tue, 8 Mar 2005 02:06:50 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 83425-07; Tue, 8 Mar 2005 02:06:41 +0000 (GMT) Received: from cassarossa.samfundet.no (cassarossa.samfundet.no [129.241.93.19]) by svr1.postgresql.org (Postfix) with ESMTP id CDC1252AA6; Tue, 8 Mar 2005 02:06:40 +0000 (GMT) Received: from trofast.ipv6.sesse.net ([2001:700:300:dc03:20e:cff:fe36:a766] helo=trofast.sesse.net) by cassarossa.samfundet.no with esmtp (Exim 4.34) id 1D8U7A-0004tL-N6; Tue, 08 Mar 2005 03:06:29 +0100 Received: from sesse by trofast.sesse.net with local (Exim 3.36 #1 (Debian)) id 1D8U76-0000Hn-00; Tue, 08 Mar 2005 03:06:24 +0100 Date: Tue, 8 Mar 2005 03:06:24 +0100 From: "Steinar H. Gunderson" To: Tom Lane Cc: Dave Held , Greg Stark , John A Meinel , Magnus Hagander , Ken Egervari , pgsql-performance@postgresql.org, pgsql-hackers-win32@postgresql.org Subject: Re: [PERFORM] Help with tuning this query (with Message-ID: <20050308020624.GA753@uio.no> Mail-Followup-To: Tom Lane , Dave Held , Greg Stark , John A Meinel , Magnus Hagander , Ken Egervari , pgsql-performance@postgresql.org, pgsql-hackers-win32@postgresql.org References: <49E94D0CFCD4DB43AFBA928DDD20C8F90261846C@asg002.asg.local> <20050308013750.GA29367@uio.no> <1971.1110247358@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1971.1110247358@sss.pgh.pa.us> X-Operating-System: Linux 2.6.11-rc3 on a i686 X-Message-Flag: Outlook? --> http://www.mozilla.org/products/thunderbird/ User-Agent: Mutt/1.5.6+20040907i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.024 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/62 X-Sequence-Number: 3020 On Mon, Mar 07, 2005 at 09:02:38PM -0500, Tom Lane wrote: > One thought that was bothering me was that if the CPU goes idle while > waiting for disk I/O, its clock might stop or slow down dramatically. > If we believed such a counter for EXPLAIN, we'd severely understate > the cost of disk I/O. > > I dunno if that is the case on any Windows hardware or not, but none > of this thread is making me feel confident that we know what > QueryPerformanceCounter does measure. I believe the counter is actually good in such a situation -- I'm not a Win32 guru, but I believe it is by far the best timer for measuring, well, performance of a process like this. After all, it's what it was designed to be :-) OBTW, I think I can name something like 15 or 20 different function calls to measure time in the Win32 API (all of them in use); it really is a giant mess. /* Steinar */ -- Homepage: http://www.sesse.net/