From: Steinar H. Gunderson <sgunderson@bigfoot.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Dave Held <dave.held@arrayservicesgrp.com>
Cc: Greg Stark <gsstark@mit.edu>
Cc: John A Meinel <john@arbash-meinel.com>
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: Tue, 8 Mar 2005 03:06:24 +0100
Message-ID: <20050308020624.GA753@uio.no> (raw)
In-Reply-To: <1971.1110247358@sss.pgh.pa.us>
References: <49E94D0CFCD4DB43AFBA928DDD20C8F90261846C@asg002.asg.local>
<20050308013750.GA29367@uio.no>
<1971.1110247358@sss.pgh.pa.us>
On Mon, Mar 07, 2005 at 09:02:38PM -0500, Tom Lane wrote:
> 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.
I believe the counter is actually good in such a situation -- I'm not a Win32
guru, but I believe it is by far the best timer for measuring, well,
performance of a process like this. After all, it's what it was designed to
be :-)
OBTW, I think I can name something like 15 or 20 different function calls to
measure time in the Win32 API (all of them in use); it really is a giant
mess.
/* Steinar */
--
Homepage: http://www.sesse.net/
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: sgunderson@bigfoot.com, tgl@sss.pgh.pa.us, dave.held@arrayservicesgrp.com, gsstark@mit.edu, john@arbash-meinel.com, mha@sollentuna.net, ken@upfactor.com, pgsql-hackers-win32@postgresql.org
Subject: Re: [PERFORM] Help with tuning this query (with
In-Reply-To: <20050308020624.GA753@uio.no>
* 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