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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,7d2c8b4487ef2145 X-Google-Attributes: gid103376,public From: ohk@ultra.tfdt-o.nta.no (Ole-Hjalmar Kristensen FOU.TD/DELAB) Subject: Re: Ada versus Java - Tasking Date: 1997/01/21 Message-ID: #1/1 X-Deja-AN: 211219001 references: <01bc03ee$594dc520$829d6482@joy.ericsson.se> organization: Telenor Online Public Access newsgroups: comp.lang.ada Date: 1997-01-21T00:00:00+00:00 List-Id: In article jsa@alexandria (Jon S Anthony) writes: In article <1997Jan19.122511.1@eisner> kilgallen@eisner.decus.org (Larry Kilgallen) writes: > Operating system developers have a much better chance to make the > scheduling interact with the hardware properly, so I think the better > choices are: > > 1) Rely on OS threading support, and wait for improvements. > > 2) Lobby the operating system provider for better support, > using all methods available, including examples of other > operating systems which do it better, either on the same > hardware or some other hardware. Abosolutely. If you happen to need something better than this you probably should not be using typical run of the mill OSs in the first place. /Jon -- Jon Anthony Organon Motives, Inc. Belmont, MA 02178 617.484.3383 jsa@organon.com Many applications are typically required to both run on standard OSs, have good performance, and be portable. DB and TP systems are obvious examples. Of course, you can just avoid using any mechanisms which are too slow, but that may rule out using mecanisms which otherwise could be used to great advantage. With transaction response times in the range of typically 1..10 milliseconds, you don't have time for too many context switches, although I do not think using Ada tasks to represent transactions would be prohibitively costly. The greatest resource hog in the system I'm working on (written in C++, btw) is undoubtedly the network layer, which accounts for more than 1/3 of the CPU time...