Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!orion.oac.uci.edu!hardy From: hardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy)) Newsgroups: comp.sys.hp Subject: Re: README: Hazard in 68040 upgrades for HP9000/400t! Message-ID: Date: 9 Jun 91 16:31:28 GMT References: <3270@sparko.gwu.edu> Distribution: na Organization: University of California, Irvine, USA. Lines: 43 Nntp-Posting-Host: golem.ps.uci.edu In-reply-to: gritz@seas.gwu.edu's message of 5 Jun 91 15:53:24 GMT In article <3270@sparko.gwu.edu> gritz@seas.gwu.edu (Larry Gritz) writes: [... stuff deleted] >> /* >> This sample program demonstrates problems with the 68040 >> cpu. Here are benchmarks for the same program, run on >> (1) A 68030 diskless HP9000/400t, 8 Mb RAM, served by an >> HP9000/835 disk server, >> (2) A 68040 HP9000/425t, with 16 Mb RAM, internal 200 Mb and >> external 330 Mb disks. >> >> TIME: (1) 68030 (2) 68040 >> >> real 1m 16.42 s 57m 11.20 s >> user 1m 3.96 s 0m 28.46 s >> system 0m 2.46 s 45m 41.26 s >> */ >> Uout of curiosity, I ran the program on a 25 MHz NeXT with 20 MB of memory. Here is the timing (in NeXT format ... use your own translations): 27.772u 60.903s 1:36.83 91.5% 0+0k 33+1137io 0pf+0w Somewhat slower than the 68030 , but a far cry from what the above. Here are the sizes of the code and output on the NeXT, for comparison. -rw-rw-r-- 1 hardy wheel 2100000 Jun 9 09:17 third.out -rw-rw-r-- 1 hardy wheel 2100000 Jun 9 09:17 second.out -rw-rw-r-- 1 hardy wheel 4300000 Jun 9 09:17 first.out drwxrwxr-x 5 hardy wheel 1024 Jun 9 09:16 ./ -rwxrwxr-x 1 hardy wheel 16384 Jun 9 09:16 float* Would the experts please comment? Greetings, Hardy -------****------- Meinhard E. Mayer (Hardy); Department of Physics, University of California Irvine CA 92717; (714) 856 5543; hardy@golem.ps.uci.edu or MMAYER@UCI.BITNET