From: Greg Stark <gsstark@mit.edu>
To: John A Meinel <john@arbash-meinel.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Magnus Hagander <mha@sollentuna.net>
Cc: Ken Egervari <ken@upfactor.com>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-hackers-win32@postgresql.org
Subject: Re: [PERFORM] Help with tuning this query (with
Date: 07 Mar 2005 13:05:30 -0500
Message-ID: <874qfnbac5.fsf@stark.xeocode.com> (raw)
In-Reply-To: <422C8E37.8000009@arbash-meinel.com>
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>
John A Meinel <john@arbash-meinel.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gsstark@mit.edu, john@arbash-meinel.com, tgl@sss.pgh.pa.us, mha@sollentuna.net, ken@upfactor.com, pgsql-hackers-win32@postgresql.org
Subject: Re: [PERFORM] Help with tuning this query (with
In-Reply-To: <874qfnbac5.fsf@stark.xeocode.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox