Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!rutgers!mcnc!uvaarpa!murdoch!astsun.astro.Virginia.EDU!gl8f
From: gl8f@astsun.astro.Virginia.EDU (Greg Lindahl)
Newsgroups: comp.sys.atari.st
Subject: Re: Can we avoid speculating until the TT actually ships, please?
Message-ID: <1990Jun8.000125.9237@murdoch.acc.Virginia.EDU>
Date: 8 Jun 90 00:01:25 GMT
References: <1990Jun6.212710.15236@murdoch.acc.Virginia.EDU> <5440122@hplsla.HP.COM>
Sender: news@murdoch.acc.Virginia.EDU
Organization: Department of Astronomy, University of Virginia
Lines: 31

In article <5440122@hplsla.HP.COM> andyc@hplsla.HP.COM (Andy Cassino) writes:
>gl8f@astsun.astro.Virginia.EDU (Greg Lindahl) writes:
>
>| The TT is not yet shipping. Until it does:
>| 
>| -- we won't have good benchmarks.
>
>Well, there are some good benchmarks... Darek Mihocka just uploaded to 
>GEnie his report on benchmarks he ran on the TT at it's Canadian unveiling. 

This is *exactly* why I say we won't get good benchmarks until it
ships. We don't have any/enough details about the benchmarks he ran...
and I won't be satisfied until I can run my benchmarks myself.

>(Sorry, the report carries a copyright notice so I cannot post it!) However, 
>I think it tends to support the comment regarding a 1/3 speed increase for 
>non-recompiled code. Apparently, this performance is projected (by Atari) to
>improve as the TOS on the TT is optimized.

That comment isn't useful until we get an idea of what the benchmark
does. Disk I/O? Screen I/O? Floating point? Compute-intensive integer
operations? Just throwing a number around with no details is not
useful, and inspires a lot of moaning and groaning.

I'm not trying to insult here, but just make the point that the
information isn't complete until we can all sit an ST next to a TT and
run our favorite program.

--
"Perhaps I'm commenting a bit cynically, but I think I'm qualified to."
                                              - Dan Bernstein