Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site mips.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!decwrl!Glacier!mips!mash
From: mash@mips.UUCP (John Mashey)
Newsgroups: net.micro.att
Subject: Re: compiler speed on the 7300
Message-ID: <137@mips.UUCP>
Date: Mon, 20-May-85 14:14:09 EDT
Article-I.D.: mips.137
Posted: Mon May 20 14:14:09 1985
Date-Received: Thu, 23-May-85 02:25:46 EDT
References: <597@astrovax.UUCP>
Distribution: net
Organization: MIPS Computer Systems, Mountain View, CA
Lines: 26

Michael Richmond writes:
>    I went to play with the 7300 at my local computer store yesterday and have
> some (dis?)heartening news for people like me who want to do a lot of
> program development on the machine. The compile times for a simple program
	....
> is (for 7300 in window environment, 7300 out of window environment and VAX
> 11/750 (out of window environment :-) ))
>                      7300 w/ windows             7300              VAX
> 65 statements                                     :28              :09
> 250 statements           1:58                     :55              :21

It's hard to tell what this means, because the 7300 times are significantly
higher than for its ancestor-Miniframe, even at the same clock speed and
using the same compiler.  What I'd suspect is a high paging rate on a small
system.  I'd suggest redoing the experiment, doing the following:
1) Specify the size of the 7300.  For whatever reasons, doing C compiles
has a fierce knee inthe performance curve.  512K is tight, 1MB is OK.
2) What's OS on VAX? Be warned that the System V linker can often take
50-65% of the time on a minimal compile, whereas BSD linkers are not as
powerful, but are faster.  To measure this, try timing cc -c.
3) It's also worth reporting cpu as well as real.
-- 
-john mashey
UUCP: 	{decvax,ucbvax,ihnp4}!decwrl!mips!mash
DDD:  	415-960-1200
USPS: 	MIPS Computer Systems, 1330 Charleston Rd, Mtn View, CA 94043