Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!rex!ames!sgi!shinobu!odin!warp.esd.sgi.com!kipp From: kipp@warp.esd.sgi.com (Kipp Hickman) Newsgroups: comp.sys.sgi Subject: Re: Where's the SPARK in my SPARC???? Message-ID: <1991Feb21.235858.21793@odin.corp.sgi.com> Date: 21 Feb 91 23:58:58 GMT References: <1991Feb21.120049.5626@jarvis.csri.toronto.edu> Sender: news@odin.corp.sgi.com (Net News) Reply-To: kipp@warp.esd.sgi.com (Kipp Hickman) Organization: Silicon Graphics, Entry Systems Division Lines: 9 In article <1991Feb21.120049.5626@jarvis.csri.toronto.edu>, corkum@csri.toronto.edu (Brent Thomas Corkum) writes: |> cc -float *.c -lm -o compute -> SGI |> cc -fsingle *.c -lm -o compute -> SUN I think you need to run the optimizer on both machines to achieve a better analysis of your performance. In any case, the best way to determine a machines performance is to run your application, not benchmarks. SGI machines typically show up as slower in benchmarks (especially when other vendors publish them) but actually run real applications significantly faster. SGI also tends to understate our performance numbers as there are a *HUGE* number of variables in determining real application performance. kipp Brought to you by Super Global Mega Corp .com