Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!ncar!noao!arizona!modular!olson From: olson@modular.UUCP (Jon Olson) Newsgroups: comp.unix.wizards Subject: Re: Benchmarks of 68020's vs Vax's under load Message-ID: <603@modular.UUCP> Date: 29 May 88 03:09:25 GMT Distribution: comp Organization: Modular Mining Systems, Tucson Lines: 35 I decided to test out some of the theories on the NET about Vax's being better at handling alot of jobs and high user loads. The benchmarks below show the elapsed time required for 8 simultaneous optimized compiles of a 3783 line C program on each machine, with no other jobs currently running. Here are some stats on the machines with the following configurations: 1) Vax 11/780, 8Mb memory, VMS V4.6, VAX-C V2.4 2) MicroVax, 9Mb memory, Ultrix V2.0, Unix PCC compiler 3) Sun 3/60, 20Mhz 68020, 8 Mb memory, SUNOS V3.4 -Time (secs)- -Relative Performance- Machine CPU Elapsed CPU/Elapsed CPU Elapsed ------- ----- ------- ----------- ----- ------- 11/780 1206 1728 69.8% 1.0 1.0 MicroVax 1206 1370 88.2% 1.0 1.3 Sun 3/60 498 551 90.4% 2.4 3.1 The CPU time in the above table is the sum of all jobs; the elapsed time is the time for the last job to finish. All jobs were started simultaneously and had exclusive use of the machine during execution. Note from the above table that the Sun 3/60, (yes running a 68020) had the highest ratio of (CPU time / elapsed time) and the worst performer was, as I would have guessed, the Vax 11/780 running VMS. Also interesting was that the 11/780 and MicroVax had identical CPU times even though running different compilers on different systems. The VMS overhead, however, makes the VAX-C compiler much slower than the portable C compiler on Ultrix V2.0. Seems to me that the system that does poorly under load is Vax's running VMS! -- Jon Olson, Modular Mining Systems USENET: {ihnp4,allegra,cmcl2,hao!noao}!arizona!modular!olson INTERNET: modular!olson@arizona.edu