From: Tom Lane <tgl@sss.pgh.pa.us>
To: John A Meinel <john@arbash-meinel.com>
Cc: Dave Held <dave.held@arrayservicesgrp.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 17:56:39 -0500
Message-ID: <15994.1110236199@sss.pgh.pa.us> (raw)
In-Reply-To: <422CDA2A.1000105@arbash-meinel.com>
References: <49E94D0CFCD4DB43AFBA928DDD20C8F90261846B@asg002.asg.local>
<422CDA2A.1000105@arbash-meinel.com>
John A Meinel <john@arbash-meinel.com> writes:
> Dave Held wrote:
>> There is always clock().
> My experience with clock() on win32 is that CLOCKS_PER_SEC was 1000, and
> it had a resolution of 55clocks / s. When I just did this:
The other problem is it measures process CPU time, not elapsed time
which is probably more significant for our purposes.
Which brings up a question: just what does QueryPerformanceCounter
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, john@arbash-meinel.com, dave.held@arrayservicesgrp.com, pgsql-hackers-win32@postgresql.org
Subject: Re: [PERFORM] Help with tuning this query (with
In-Reply-To: <15994.1110236199@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