comp.lang.ada
 help / color / mirror / Atom feed
From: nsisrv!robots!nbssal@ames.arc.nasa.gov  (Stephe Leake)
Subject: Re: CPU resources for embedded Ada programs
Date: 4 Jan 93 18:58:00 GMT	[thread overview]
Message-ID: <4JAN199313583867@robots> (raw)

In article <cffs.14@fox.nstn.ns.ca>, cffs@fox.nstn.ns.ca (Doug Brown) writes...
>  I recently recieved a copy of lessons learned report that covered two Ada 
>development projects.  The projects were 50 and 80 KLOC, were real-time, 
>embedded military applications that ran 68K series processors.  Based upon 
>the experience of these two projects, the authors suggested that embedded, 
>real-time Ada projects will require about 1 MB of RAM and 3 MIPS of CPU 
>power for every 20 KLOC.
> 
>  Are these numbers valid?  Does anyone have any experience with similar 
>rules of thumb?  Is it even possible to come up with rules of thumb such 
>as this, given the diverse nature of many Ada applications.  Thanks.
> 
>Doug Brown
>cffs@fox.nstn.ns.ca

I'm using Alsys Ada on 3 bare 16 Mhz 386/387 Multibus I boards, running a
real-time robot control system with a basic servo cycle time of 20
milliseconds. There are 24K source lines of code, occupying about 500 kbytes of
RAM. I don't know the MIPS rating, but only half the code is on the servo
board, which has a 50% utilization. So my application and/or Alsys yeilds lower
requirements than the above.

Stephen Leake	NASA Goddard Robotics Lab
internet : nbssal@robots.gsfc.nasa.gov

             reply	other threads:[~1993-01-04 18:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-01-04 18:58 Stephe Leake [this message]
  -- strict thread matches above, loose matches on Subject: below --
1993-01-04 21:33 CPU resources for embedded Ada programs saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!s
1993-01-04 20:20 Mike Ryer
1993-01-04 17:27 agate!spool.mu.edu!uwm.edu!ux1.cso.uiuc.edu!news.cs.indiana.edu!nstn.ns.c
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox