Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!linus!decvax!ittvax!swatt From: swatt@ittvax.UUCP (Alan S. Watt) Newsgroups: net.works,net.unix-wizards Subject: Re: hello.c benchmark run on all 21 vendors ar usenix Message-ID: <857@ittvax.UUCP> Date: Sun, 17-Jul-83 18:21:18 EDT Article-I.D.: ittvax.857 Posted: Sun Jul 17 18:21:18 1983 Date-Received: Sun, 17-Jul-83 22:08:18 EDT References: tropix.149 Lines: 18 This is an interesting benchmark. However the comparison as given doesn't quite show the whole picture. If you look at the size of the "a.out" file produced, you will find (at least I find on our UTS system [IBM 4341]), that the \smallest/ a.out file you can get from UTS is ~20K bytes. Once you drag any routine from "stdio" in, it appears that an incredible gob of "in-laws" come with it. This may in fact be a disadvantage to UTS, but it does indicate that that sucker can do I/O \fast/. I think the basic filesystem block size is 4096 bytes, which may help explain it. So just comparing real/user/system times for "cc hello.c" may make UTS/470 look good, but if you compared the time per byte of output produced, it would make it look even better. What a pity you still have to edit using those %$@!^@$$! 3270 tubes! - Alan S. Watt