Ach, don't feel bad!
Besides, if I had a quad-360 setup, I wouldn't keep it. Given the
value of such a system, one could sell it and have more than enough to get a very
nice quad-700 Tezro instead.
> I would be happy to try and run the test, if I knew what it was and where to find it. ...
> I searched the net and only found references to Cray, but maybe that is what it means.
Nothing to do with Cray (just goes to show how dumb the search engines are).
Written by John Tsiombikas (one of the people creating the game Theseis), C-ray is a
small ray tracing benchmark, using a dataset that fits entirely in L2 cache, so it's purely
a fp CPU test. I'm taking over the maintenance of the results page and will begin adding
multi-CPU/multi-core results soon. Here's the test archive (198K): http://www.futuretech.blinkenlights.nl/ ... 1.1.tar.gz
and here's the current results table: http://www.futuretech.blinkenlights.nl/c-ray.html
The table doesn't yet include multi-CPU/core results (first need to work out a good
way of making it clear which results are single-CPU/core and which are not) but here
is a MIPS summary which includes some multi-CPU examples I've collated, along
with the C-Ray author's dual-core PentiumD result:
Code: Select all
Dual-core PentiumD 3GHz 692
Octane2 Dual-R14K/600 (2MB) 839
Onyx Quad-R10K/195 (2MB) 1307
Fuel R14K/700 (4MB) 1425
Octane2 R14K/600 (2MB) 1660
Fuel R14K/500 (2MB) 1998
Octane2 R12K/400 (2MB) 2517
O2 R12K/400 (2MB) 2556
O2 R12K/270 (2MB) 3793
O2 R10K/250 (1MB) 4158
Indigo2 R10K/195 (1MB) 5274
Onyx Quad-R4K/150 (1MB) 5749
O2 R5200SC/300 (1MB) 6393
O2 R5000SC/200 (1MB) 9751
The newer IRIX systems perform pretty well for this test, given their low clock, age and lack
of instruction extensions that are available in x86 CPUs. Indeed, the main table shows
R10K/R12K MIPS systems outperforming single-core PCs with much higher clock speeds
quite easily. However, the newer dual-core x86 options changes things a lot.
So, I would expect your quad-270 O200 to be a smidgen slower than the dual-600 Octane2.
PS. As an x86 scaling efficiency comparison, note that John's dual-core PentiumD 3GHz does
the test in 1365ms when running just 1 thread, ie. using only a single core. The scaling is almost
identical to the percentage speed increase for multi-CPU SGIs, eg. single vs. dual-600 Octane2.