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 1615D563D4 for ; Tue, 8 Mar 2005 02:02:57 +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 82538-08 for ; Tue, 8 Mar 2005 02:02:48 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9651354E9E for ; Tue, 8 Mar 2005 02:02:48 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j2822cpk001972; Mon, 7 Mar 2005 21:02:38 -0500 (EST) To: "Steinar H. Gunderson" 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 In-reply-to: <20050308013750.GA29367@uio.no> References: <49E94D0CFCD4DB43AFBA928DDD20C8F90261846C@asg002.asg.local> <20050308013750.GA29367@uio.no> Comments: In-reply-to "Steinar H. Gunderson" message dated "Tue, 08 Mar 2005 02:37:50 +0100" Date: Mon, 07 Mar 2005 21:02:38 -0500 Message-ID: <1971.1110247358@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/59 X-Sequence-Number: 3017 "Steinar H. Gunderson" writes: > RDTSC is a bad source of information for this kind of thing, as the CPU > frequency might vary. 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. regards, tom lane