pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dimitri Fontaine <dim@dalibo.com>
To: pgsql-hackers@postgresql.org, Martijn van Oosterhout <kleptog@svana.org>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Kelly Burkhart <kelly.burkhart@gmail.com>
Cc: Evgeny Gridasov <eugrid@fpm.kubsu.ru>
Cc: pgsql-performance@postgresql.org
Subject: Re: [HACKERS] EXPLAIN ANALYZE on 8.2
Date: Fri, 15 Dec 2006 12:24:35 +0100
Message-ID: <200612151224.42158.dim@dalibo.com> (raw)
In-Reply-To: <20061215105008.GD958@svana.org>
References: <20061214163230.d46f0138.eugrid@fpm.kubsu.ru>
	<1166178488.3882.56.camel@silverbirch.site>
	<20061215105008.GD958@svana.org>

Hi list,

Le vendredi 15 décembre 2006 11:50, Martijn van Oosterhout a écrit :
> BTW, doing gettimeofday() without kernel entry is not really possible.
> You could use the cycle counter but it has the problem that if you have
> multiple CPUs you need to calibrate the result. If the CPU goes to
> sleep, there's is no way for the userspace process to know. Only the
> kernel has all the relevent information about what "time" is to get a
> reasonable result.

I remember having played with intel RDTSC (time stamp counter) for some timing 
measurement, but just read from several sources (including linux kernel 
hackers considering its usage for gettimeofday()  implementation) that TSC is 
not an accurate method to have elapsed time information.

May be some others method than gettimeofday() are available (Lamport 
Timestamps, as PGDG may have to consider having a distributed processing 
ready EA in some future), cheaper and accurate?
After all, the discussion, as far as I understand it, is about having a 
accurate measure of duration of events, knowing when they occurred in the day 
does not seem to be the point.

My 2¢, hoping this could be somehow helpfull,
-- 
Dimitri Fontaine
http://www.dalibo.com/

view thread (24+ messages)  latest in thread

Message-ID: <200612151224.42158.dim@dalibo.com>
Permalink:  ../200612151224.42158.dim@dalibo.com/
Also on:    postgresql.org/message-id/200612151224.42158.dim@dalibo.com

 · 

reply

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: dim@dalibo.com, kleptog@svana.org, simon@2ndquadrant.com, tgl@sss.pgh.pa.us, kelly.burkhart@gmail.com, eugrid@fpm.kubsu.ru
  Subject: Re: [HACKERS] EXPLAIN ANALYZE on 8.2
  In-Reply-To: <200612151224.42158.dim@dalibo.com>

* 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