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 68CED564D5; Mon, 7 Mar 2005 18:05:53 +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 56257-07; Mon, 7 Mar 2005 18:05:50 +0000 (GMT) Received: from stark.xeocode.com (stark.xeocode.com [216.58.44.227]) by svr1.postgresql.org (Postfix) with ESMTP id 0A7E656454; Mon, 7 Mar 2005 18:05:48 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=stark.xeocode.com) by stark.xeocode.com with smtp (Exim 3.36 #1 (Debian)) id 1D8Mbi-0002io-00; Mon, 07 Mar 2005 13:05:30 -0500 To: John A Meinel Cc: Tom Lane , Magnus Hagander , Ken Egervari , pgsql-performance@postgresql.org, pgsql-hackers-win32@postgresql.org Subject: Re: [PERFORM] Help with tuning this query (with References: <6BCB9D8A16AC4241919521715F4D8BCE476A60@algol.sollentuna.se> <23086.1110206737@sss.pgh.pa.us> <422C817A.8050009@arbash-meinel.com> <2555.1110213531@sss.pgh.pa.us> <422C8E37.8000009@arbash-meinel.com> In-Reply-To: <422C8E37.8000009@arbash-meinel.com> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 07 Mar 2005 13:05:30 -0500 Message-ID: <874qfnbac5.fsf@stark.xeocode.com> Lines: 17 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.015 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/67 X-Sequence-Number: 3025 John A Meinel writes: > Then we would only be wrong for 256 gettimeofday calls. I agree it isn't > great, though. And probably better to just abstract (possibly just with > #ifdef) the calls for accurate timing, from the calls that actually need > the real time. What would be really neato would be to use the rtdsc (sp?) or equivalent assembly instruction where available. Most processors provide such a thing and it would give much lower overhead and much more accurate answers. The main problem I see with this would be on multi-processor machines. (QueryPerformanceCounter does work properly on multi-processor machines, right?) -- greg