From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steinar H. Gunderson <sgunderson@bigfoot.com>
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: Mon, 07 Mar 2005 21:02:38 -0500
Message-ID: <1971.1110247358@sss.pgh.pa.us> (raw)
In-Reply-To: <20050308013750.GA29367@uio.no>
References: <49E94D0CFCD4DB43AFBA928DDD20C8F90261846C@asg002.asg.local>
<20050308013750.GA29367@uio.no>
"Steinar H. Gunderson" <sgunderson@bigfoot.com> writes:
> RDTSC is a bad source of information for this kind of thing, as the CPU
> frequency might vary.
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.
regards, tom lane
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: tgl@sss.pgh.pa.us, sgunderson@bigfoot.com, 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: <1971.1110247358@sss.pgh.pa.us>
* 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