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.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,a0fe76afdfe9e57d X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-06-11 23:18:16 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!news.tele.dk!news.tele.dk!small.news.tele.dk!fu-berlin.de!uni-berlin.de!b9a98.pppool.DE!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: milliseconds and delay until Date: Thu, 12 Jun 2003 08:20:43 +0200 Organization: At home Message-ID: References: Reply-To: mailbox@dmitry-kazakov.de NNTP-Posting-Host: b9a98.pppool.de (213.7.154.152) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Trace: fu-berlin.de 1055398694 16853482 213.7.154.152 (16 [77047]) User-Agent: KNode/0.7.1 Xref: archiver1.google.com comp.lang.ada:39025 Date: 2003-06-12T08:20:43+02:00 List-Id: Simon Wright wrote: > NB!! on most desktop machines you'll get a minimum actual delay of 10 > ms (a tick) or even 2 ticks; what happens, I think, is that many of > the "delay until"s turn out to be delaying until a time that has > already passed, so the program spins until it catches up. It is a complicated issue which depends on great variety of factors [OS, whether Ada RT uses native threads etc.] But usually I would expect a better performance. [Even under Windows NT, where the time slicing quant is 10ms, one can force it to 1ms. Under 2k/XP it is already 1ms.] -- Regards, Dmitry A. Kazakov www.dmitry-kazakov.de