From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 required=5.0 tests=BAYES_00,INVALID_MSGID,
	PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII
X-Google-Thread: 103376,c6128af70f6d02c8
X-Google-Attributes: gid103376,public
From: "Pascal Obry" <p.obry@der.edf.fr>
Subject: Re: Timing things.
Date: 1999/06/17
Message-ID: <7kaalj$j9$1@clnews.edf.fr>#1/1
X-Deja-AN: 490588615
References: <3767E18A.1904F5AF@acm.org>
X-Priority: 3
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Organization: EDF
X-MSMail-Priority: Normal
Newsgroups: comp.lang.ada
Date: 1999-06-17T00:00:00+00:00
List-Id: <comp.lang.ada>


Joel VanLaven <jvanlaven@acm.org> a �crit dans le message :
3767E18A.1904F5AF@acm.org...
> I wrote a program as an assignment for an algorithms class in
> Ada95 that builds and operates on a variety of double-ended priority
> queues.  I am supposed to time certain operations (the build then the
> sum of the subsequent iterations of operations).  I am trying to use
> ada.real_time (rather than using some OS feature).  Problem is on my
> Windows98 PC using Gnat 3.11p I seem to be getting completely bogus and
> useless times. (granularity of at best 1/100 of a second though it looks
> more like 1/10 of a second)
>

This is true in GNAT 3.11 where the clock is implemented with standard
Windows
timing function.

In GNAT 3.12 the clock is implemented using a high resolution counter, this
gives the clock a resolution of about 1 micro-sec.

Pascal.