From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers-win32(at)postgresql(dot)org>, "PostgreSQL-patches" <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: explain analyze timings |
Date: | 2005-03-20 13:42:24 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE6C70E5@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 pgsql-patches |
>> 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).
I also hacked commands/explain.c to get the total runtime of the query
correct.
//Magnus
Attachment | Content-Type | Size |
---|---|---|
win32_instr.patch | application/octet-stream | 6.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2005-03-20 15:31:48 | Re: explain analyze timings |
Previous Message | Greg Stark | 2005-03-20 06:49:37 | Re: [pgsql-hackers-win32] snprintf causes regression tests |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2005-03-20 15:31:48 | Re: explain analyze timings |
Previous Message | Greg Stark | 2005-03-20 06:49:37 | Re: [pgsql-hackers-win32] snprintf causes regression tests |