Re: gettimeofday is at the end of its usefulness? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: gettimeofday is at the end of its usefulness?
Date
Msg-id 20140515185614.GG25053@momjian.us
Whole thread Raw
In response to gettimeofday is at the end of its usefulness?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: gettimeofday is at the end of its usefulness?
List pgsql-hackers
On Tue, May 13, 2014 at 06:58:11PM -0400, Tom Lane wrote:
> A recent question from Tim Kane prompted me to measure the overhead
> costs of EXPLAIN ANALYZE, which I'd not checked in awhile.  Things
> are far worse than I thought.  On my current server (by no means
> lavish hardware: Xeon E5-2609 @2.40GHz) a simple seqscan can run
> at something like 110 nsec per row:

I assume you ran pg_test_timing too:
Testing timing overhead for 3 seconds.Per loop time including overhead: 41.70 nsecHistogram of timing durations:< usec
% of total      count     1     95.83035   68935459     2      4.16923    2999133     4      0.00037        268     8
  0.00004         31    16      0.00000          1    32      0.00000          1
 

My overhead of 41.70 nsec matches yours.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: New timezones used in regression tests
Next
From: Robert Haas
Date:
Subject: Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers