Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!brutus.cs.uiuc.edu!psuvax1!schwartz
From: schwartz@psuvax1.cs.psu.edu (Scott Schwartz)
Newsgroups: comp.lang.perl
Subject: Re: speed: V2 verses V3
Message-ID: <1989Dec18.032836.16434@psuvax1.cs.psu.edu>
Date: 18 Dec 89 03:28:36 GMT
References: <1808@uvaarpa.virginia.edu> <6609@jpl-devvax.JPL.NASA.GOV> <4047@convex.UUCP>
Organization: Penn State University Computer Science
Lines: 27

In article <4047@convex.UUCP> tchrist@convex.COM (Tom Christiansen) writes:
>Oddly enough, on a diskless sun/350 with 4 meg of memory, there was little
>variance in user time (5%) but a 50% speedup in system time between perl2
>and perl3.

On my machine, a Sun4/280 w/ 32M, the termcap entry for wyse50 is
matched by an adds entry close to the beginning.  I ran it for a tvi955
instead, which is near the end.  Here's four trials of each...

psuvax1% time perl-3 xxx.pl tvi955 >/dev/null
1.160u 0.240s 0:01.63 85% 0+560k 0+0io 0pf+0w
1.060u 0.330s 0:01.46 95% 0+554k 0+0io 0pf+0w
1.120u 0.330s 0:01.75 82% 0+561k 1+0io 0pf+0w
1.120u 0.270s 0:01.55 89% 0+555k 2+0io 0pf+0w

psuvax1% time perl-2 xxx.pl tvi955 > /dev/null
1.040u 0.530s 0:01.74 90% 0+473k 1+0io 0pf+0w
1.230u 0.390s 0:01.79 90% 0+473k 0+0io 0pf+0w
1.190u 0.420s 0:01.74 92% 0+469k 0+0io 0pf+0w
1.160u 0.460s 0:02.98 54% 0+463k 0+0io 0pf+0w

I think this benchmark is not computationally expensive enough
to give good results.  One second of runtime tells nothing, really.

-- 
Scott Schwartz		<schwartz@shire.cs.psu.edu>
"More mips; cheaper mips; never too many." -- John Mashey