From: | "Steinar H(dot) Gunderson" <sgunderson(at)bigfoot(dot)com> |
---|---|
To: | Dave Held <dave(dot)held(at)arrayservicesgrp(dot)com> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, John A Meinel <john(at)arbash-meinel(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <mha(at)sollentuna(dot)net>, Ken Egervari <ken(at)upfactor(dot)com>, pgsql-performance(at)postgresql(dot)org, pgsql-hackers-win32(at)postgresql(dot)org |
Subject: | Re: [PERFORM] Help with tuning this query (with |
Date: | 2005-03-08 01:37:50 |
Message-ID: | 20050308013750.GA29367@uio.no |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 pgsql-performance |
On Mon, Mar 07, 2005 at 06:11:34PM -0600, Dave Held wrote:
>> In which case using it would be a mistake. Since rtdsc doesn't
>> work across processors.
> It doesn't always use RDTSC. I can't find anything authoritative on
> when it does. I would assume that it would use RDTSC when available
> and something else otherwise.
RDTSC is a bad source of information for this kind of thing, as the CPU
frequency might vary. Check your QueryPerformanceFrequency() -- most likely
it will not match your clock speed. I haven't tested on a lot of machines,
but I've never seen QueryPerformanceFrequency() ever match the clock speed,
which it most probably would if it was using RDTSC. (I've been told it uses
some other kind of timer available on most motherboards, but I don't know the
details.)
/* Steinar */
--
Homepage: http://www.sesse.net/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-03-08 02:02:38 | Re: [PERFORM] Help with tuning this query (with |
Previous Message | Dave Held | 2005-03-08 00:29:31 | Re: [PERFORM] Help with tuning this query (with |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-03-08 02:02:38 | Re: [PERFORM] Help with tuning this query (with |
Previous Message | Dave Held | 2005-03-08 00:29:31 | Re: [PERFORM] Help with tuning this query (with |