Path: utzoo!censor!geac!torsqnt!hybrid!scifi!bywater!uunet!telesoft!rlk
From: rlk@telesoft.com (Bob Kitzberger @sation)
Newsgroups: comp.software-eng
Subject: Re: Effect of execution-speed on reliability/testing
Message-ID: <1157@telesoft.com>
Date: 12 Jan 91 21:56:40 GMT
References: <1990Dec19.102005.11830@engin.umich.edu> <470@eiffel.UUCP> <11541@pt.cs.cmu.edu>
Organization: TeleSoft, San Diego, CA.
Lines: 24

In article <11541@pt.cs.cmu.edu>, tgl@g.gp.cs.cmu.edu (Tom Lane) writes:
>
> Plauger says you should "choose the slowest mechanism that is fast
> enough.  By fast enough, I imply that you allow plenty of headroom, in
> accordance with the 70% rule."  

While arguably a worthwhile heuristic, Plauger's approach still begs 
the question of how fast the system should be.  Seat-of-the-pants
methods won't get us reliable mission-critical systems of the scale
of the new air-traffic control system or Space Station.

Anybody using Rate Monotonic Scheduling for filling hard real-time 
requirements?  Any success?

	.Bob.
-- 
Bob Kitzberger               Internet : rlk@telesoft.com
TeleSoft                     uucp     : ...!ucsd.ucsd.edu!telesoft!rlk
5959 Cornerstone Court West, San Diego, CA  92121-9891  (619) 457-2700 x163
------------------------------------------------------------------------------
"Civilization rests on two things," said Hitzig; "the discovery that
fermentation produces alcohol, and voluntary ability to inhibit defecation."

				-- Robertson Davies, "The Rebel Angels"