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 E79A1564A7; Mon, 7 Mar 2005 23:15: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 39890-01; Mon, 7 Mar 2005 23:15:48 +0000 (GMT) Received: from stark.xeocode.com (stark.xeocode.com [216.58.44.227]) by svr1.postgresql.org (Postfix) with ESMTP id 7BD1656488; Mon, 7 Mar 2005 23:15:47 +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 1D8RRh-0003wi-00; Mon, 07 Mar 2005 18:15:29 -0500 To: "Dave Held" Cc: "Greg Stark" , "John A Meinel" , "Tom Lane" , "Magnus Hagander" , "Ken Egervari" , , Subject: Re: [PERFORM] Help with tuning this query (with References: <49E94D0CFCD4DB43AFBA928DDD20C8F90261846A@asg002.asg.local> In-Reply-To: <49E94D0CFCD4DB43AFBA928DDD20C8F90261846A@asg002.asg.local> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 07 Mar 2005 18:15:29 -0500 Message-ID: <87br9v9hf2.fsf@stark.xeocode.com> Lines: 31 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.014 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/63 X-Sequence-Number: 3021 "Dave Held" writes: > > 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?) > > I believe QueryPerformanceCounter() already does this. This would be a good example of why selectively quoting the part of the message to which you're responding to is more useful than just blindly echoing my message back to me. Already does what? Use rtdsc? In which case using it would be a mistake. Since rtdsc doesn't work across processors. And using it via QueryPerformanceCounter would be a non-portable approach to using rtdsc. Much better to devise a portable approach that works on any architecture where something equivalent is available. Or already works on multi-processor machines? In which case, uh, ok. -- greg