Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!ucbcad!ucbvax!decvax!decwrl!pyramid!prls!mips!mash From: mash@mips.UUCP Newsgroups: comp.sys.m68k,comp.sys.intel Subject: Re: 386 vs 020 and big benchmarks (sieve) Message-ID: <316@winchester.UUCP> Date: Sat, 18-Apr-87 17:56:18 EST Article-I.D.: winchest.316 Posted: Sat Apr 18 17:56:18 1987 Date-Received: Sun, 19-Apr-87 08:30:59 EST References: <930@intsc.UUCP> <513@omen.UUCP> <933@intsc.UUCP> <866@oakhill.UUCP> Reply-To: mash@winchester.UUCP (John Mashey) Distribution: comp Organization: MIPS Computer Systems, Sunnyvale, CA Lines: 28 Xref: utgpu comp.sys.m68k:340 comp.sys.intel:144 In article <866@oakhill.UUCP> davet@oakhill.UUCP (Dave Trissel) writes: >In article <933@intsc.UUCP> tomk@intsc.UUCP (Tom Kohrs @fae) writes: .... >>If all you want to do is calculate sieves all day then use the '020. But >>if you want to do real crunching on large problems then the 386 will run >>circles around the '020. ... >>If performance is what you need on Megabyte >>size problems the 386 will give you 50% - 75% more speed at the same clock >>rate. It would be nice to see some more "meaty" problems I have a few collected, but not many where one can get the faster 386s versus 68020s (all that follow are from MIPS Performance Brief, April 1987): Doduc (5300-line FORTRAN program to simulate aspects of nuclear reactors): Rel Perf Machine 17 Sun3/110, 16.7 MHz 19 80386, 16MHz 22 Sun3/260, 25MHz 68020 + 20Mhz 68881 43 Sun3/260, Weitek FPA Thus, looks like the 386 might have a slight edge at same clock rate; hard to see 50-75%., at least on this particular benchmark, and, as usual, memory systems are often hard to compare 1-1. -- -john mashey DISCLAIMER: UUCP: {decvax,ucbvax,ihnp4}!decwrl!mips!mash, DDD: 408-720-1700, x253 USPS: MIPS Computer Systems, 930 E. Arques, Sunnyvale, CA 94086