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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,cae92f92d6a1d4b1 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news4.google.com!feeder.news-service.com!85.214.198.2.MISMATCH!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Ada.Execution_Time Date: Tue, 28 Dec 2010 16:18:11 +0000 Organization: A noiseless patient Spider Message-ID: References: <4d05e737$0$6980$9b4e6d93@newsspool4.arcor-online.net> <1wmsukf0wglz3$.odnzonrpayly.dlg@40tude.net> <6n1c5myuf2uz$.10jl3ln7il3aq.dlg@40tude.net> <8n0mgnFv2sU1@mid.individual.net> <1n3o55xjdjr9t.1u33kb75y2jfl$.dlg@40tude.net> <8n1142Fto2U1@mid.individual.net> <1o5cbm4b1l20d$.19winbma6k5qw.dlg@40tude.net> <8n4mskF7mmU1@mid.individual.net> <8nm30fF7r9U1@mid.individual.net> <1akm5muxu9zni.mu91b7pubqw0$.dlg@40tude.net> <8nrg25FoucU1@mid.individual.net> <2k07hwmh6123.1pgx57welw9of$.dlg@40tude.net> <8nsa76Fj4rU1@mid.individual.net> <1j9i6trxinqtg$.renlw9wdtpsf.dlg@40tude.net> <4kkxaiynm22p$.sld84rm8849d$.dlg@40tude.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="dFCm8HWntFqmDIilBLqEJQ"; logging-data="11250"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18NcLXchXcUvgE9w7ECJXK1EK7oaFqzeh4=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (darwin) Cancel-Lock: sha1:KRffLk0JDnry0PDpdnkCKZCoHVg= sha1:ky/REsZFiHqXJQMtHyRgj/NwKZY= Xref: g2news2.google.com comp.lang.ada:17169 Date: 2010-12-28T16:18:11+00:00 List-Id: "Dmitry A. Kazakov" writes: > Yes, this thing. In our case it was Pentium VxWorks 6.x. (The PPC we > used prior to it had poor performance) The problem was that > Ada.Real_Time.Clock had the accuracy of the clock interrupts, > i.e. 1ms, which is by all accounts catastrophic for a 1.7GHz > processor. You can switch some tasks forth and back between two clock > changes. Our experience was that where there are timing constraints to be met, or cyclic timing behaviours to implement, a milliscond is OK. We did consider running the VxWorks tick at 100 us but this was quite unnecessary!