Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Sun, 20 Mar 2005 15:31:48 +0000
- Message-id: <1111332708(dot)11750(dot)362(dot)camel(at)localhost(dot)localdomain>
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
- Follow-Ups:
- Re: explain analyze timings
- From: John A Meinel
- Re: explain analyze timings
- References:
- Re: explain analyze timings
- From: Magnus Hagander
- Re: explain analyze timings
- Prev by Date: Re: explain analyze timings
- Next by Date: Half filled xlogs
- Previous by thread: Re: explain analyze timings
- Next by thread: Re: explain analyze timings
- Indexes: