Skip site navigation (1) Skip section navigation (2)

Re: explain analyze timings

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Magnus Hagander <mha(at)sollentuna(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers-win32(at)postgresql(dot)org,PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: explain analyze timings
Date: 2005-03-20 15:31:48
Message-ID: 1111332708.11750.362.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-hackers-win32pgsql-patches
On Sun, 2005-03-20 at 14:42 +0100, Magnus Hagander wrote:
> >> There is. I beleive QueryPerformanceCounter has sub-mirosecond
> >> resolution.
> >
> >> Can we just replace gettimeofday() with a version that's basically:
> >
> >No, because it's also used for actual time-of-day calls.  It'd be
> >necessary to hack executor/instrument.c in particular.
> 
> Here's a patch that does just this.
> 
> On my system, the counter resolution is 3192090000 ticks per second
> (Intel Xeon CPU). On a AMD Athlon XP system, it's 3579545 ticks per
> second (a lot less, but still way way way better than gettimeofday has
> on win32).

Is this just a Win32 hack?

I've been looking for a sub-millisecond counter on other OS for a while
now...anybody know of any port specific counters elsewhere?

Thanks,

Best Regards, Simon Riggs


In response to

Responses

pgsql-patches by date

Next:From: John A MeinelDate: 2005-03-20 16:01:39
Subject: Re: explain analyze timings
Previous:From: Magnus HaganderDate: 2005-03-20 13:42:24
Subject: Re: explain analyze timings

pgsql-hackers-win32 by date

Next:From: Simon RiggsDate: 2005-03-20 15:37:28
Subject: Half filled xlogs
Previous:From: Magnus HaganderDate: 2005-03-20 13:42:24
Subject: Re: explain analyze timings

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group