Need 286 "C" benchmark

[Rick Sellens - Mech. Eng.]

I think the subject that this discussion is running under says it all.
If you go looking for a benchmark "for the 286" you will select a small
memory program if you are an Intel fan, and a large memory program if
you are a Motorola fan. The flaw lies in trying to select a benchmark
for a machine, rather than an application.

To *reasonably* benchmark anything you need an idea of what the application
will be. A benchmark can then be written to test the particular features
that are important in the expected use. A machine that screams at integer
operations in a small memory space may or may not be any good at doing
floating point work in a large memory space.

Please try to test individual capabilities when you benchmark, and then
report the results as representative of *only* those capabilities. That
way maybe we can start to intelligently answer the questions about what
machines do what things faster than others.


Rick Sellens
UUCP:  watmath!watdcsu!rsellens
CSNET: rsellens%watdcsu at waterloo.csnet
ARPA:  rsellens%watdcsu%waterloo.csnet at csnet-relay.arpa