Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!uunet!virtech!cpcahil
From: cpcahil@virtech.uucp (Conor P. Cahill)
Newsgroups: alt.sources.d
Subject: Re: uutraffic report (in perl)
Message-ID: <1989Nov23.055155.8757@virtech.uucp>
Date: 23 Nov 89 05:51:55 GMT
References: <4025@mhres.mh.nl> <1194@radius.UUCP> <3273@convex.UUCP> <3374@convex.UUCP>
Organization: Virtual Technologies Inc.
Lines: 34

In article <3374@convex.UUCP>, tchrist@convex.COM (Tom Christiansen) writes:
> In article <14947@bfmny0.UU.NET> tneff@bfmny0.UU.NET (Tom Neff) writes:
> |On System V/386, for instance, with all debugging #undef'd and with -O
> |turned on, the latest perl executable *after* both 'strip' and 'mcs -d'
> |subtends 229K, and takes ~5 seconds to load, compile and interpret an
> |in-line script consisting of 'exit 0;'.  

> Which limitations, load time?  Somewhere it does say that perl probably
> isn't good for tiny machines.  My idea of a tiny machine is my diskless
> Sun 3/50 with 4 megabytes.  Here are three successive timings:
> 
> sun% /bin/time perl -e 'exit 0;'
>         4.5 real         0.0 user         0.4 sys
>         1.2 real         0.0 user         0.2 sys
>         1.3 real         0.0 user         0.1 sys

On my high end 386 the timings for a untouched perl (non-stripped, no 
changes to source) are as follows:

/bin/time perl -e 'exit 0;'

          1.4 real         0.0 user         0.1 sys
          0.1 real         0.0 user         0.0 sys
          0.1 real         0.0 user         0.0 sys
  
/bin/time uutraf    # stuff that started this discussion

          0.9 real         0.3 user         0.2 sys

-- 
+-----------------------------------------------------------------------+
| Conor P. Cahill     uunet!virtech!cpcahil      	703-430-9247	!
| Virtual Technologies Inc.,    P. O. Box 876,   Sterling, VA 22170     |
+-----------------------------------------------------------------------+