Whew! :innocent:

$945.13 in donations, $835.32 spent, and $109.81 left...

It's nice to hear that the revisions don't matter for mrime and glucas. And it also shows that the compiler isn't producing bad code (although not perfectly optimized) for SSE2. :)

Well, now it's time to explore what we can do with 32 doubles held in registers at once...

Here is the Opteron B timings. Note that test 1001 and 1004 are significantly faster on the C. These test read 16-bit values from the L1 cache to an MMX register. So, something was improved in the core.

Test 1012 and 1013 are about the same. These are 10000 iterations of the typical prime95 code chunk we talked about in a different thread.

[code:1]Test 0: 0.000 sec. (137 clocks), avg: 0.000 sec. (149 clocks)
Test 1: 0.000 sec. (2156 clocks), avg: 0.000 sec. (2162 clocks)
Test 2: 0.000 sec. (654156 clocks), avg: 0.000 sec. (654249 clocks)
Test 3: 0.002 sec. (2752185 clocks), avg: 0.002 sec. (2753265 clocks)
Test 4: 0.002 sec. (3144129 clocks), avg: 0.002 sec. (3163605 clocks)
Test 1000: 0.000 sec. (528168 clocks), avg: 0.000 sec. (529374 clocks)
Test 1001: 0.002 sec. (2122592 clocks), avg: 0.002 sec. (2122969 clocks)
Test 1002: 0.002 sec. (2279096 clocks), avg: 0.002 sec. (2298604 clocks)
Test 1003: 0.000 sec. (525161 clocks), avg: 0.000 sec. (525214 clocks)
Test 1004: 0.002 sec. (2460430 clocks), avg: 0.002 sec. (2463085 clocks)
Test 1005: 0.003 sec. (4385117 clocks), avg: 0.003 sec. (4578506 clocks)
Test 1006: 0.000 sec. (528167 clocks), avg: 0.000 sec. (528226 clocks)
Test 1007: 0.002 sec. (2846988 clocks), avg: 0.002 sec. (2854400 clocks)
Test 1008: 0.003 sec. (4238748 clocks), avg: 0.003 sec. (4401877 clocks)
Test 1009: 0.001 sec. (1040154 clocks), avg: 0.001 sec. (1040256 clocks)
Test 1010: 0.004 sec. (4928441 clocks), avg: 0.004 sec. (5036041 clocks)
Test 1011: 0.004 sec. (5346607 clocks), avg: 0.004 sec. (5672540 clocks)
Test 1012: 0.000 sec. (504970 clocks), avg: 0.000 sec. (505043 clocks)
Test 1013: 0.001 sec. (780852 clocks), avg: 0.001 sec. (780980 clocks)
Test 1014: 0.001 sec. (1120793 clocks), avg: 0.001 sec. (1122172 clocks)
Test 1015: 0.001 sec. (1561666 clocks), avg: 0.001 sec. (1563385 clocks)
Test 1016: 0.001 sec. (1290787 clocks), avg: 0.001 sec. (1290936 clocks)
Test 1017: 0.001 sec. (1892635 clocks), avg: 0.001 sec. (1892894 clocks)
Test 1018: 0.001 sec. (1152665 clocks), avg: 0.001 sec. (1152785 clocks)
Test 1019: 0.001 sec. (1997701 clocks), avg: 0.001 sec. (1997987 clocks)[/code:1]

If you want I can email you the code for the tests above along with a P4's timings.

Xyzzy, here's a silly question...

Did you disable the on-board video on that Tyan S2850 motherboard?
I'm sure you did, cause I think I see a PCI video card in this photo:

http://www.mersenneforum.org/viewtopic.php?p=10367#10367

But when you mentioned the system components in this thread I don't think you ever actually mentioned the video card, so I'm just being paranoid about the benchmarks.

The card I added was a network card...

Most onboard video solutions suck, but in this case it is okay because it is a real video card... It just happens to be on the motherboard... It has its own memory...

Besides, we don't use it... All logins are via SSH...

[quote="Prime95"]If you want I can email you the code for the tests above along with a P4's timings.[/quote]

That would be nice. Also it would be interesting to see how different code blocks behave on Opteron.

On weekend I didn't find the time to test some different scheduling tricks on Opteron but I will do during this week.

$970.13 in donations, $835.32 spent, and $134.81 left...

The CD-ROM arrived a few days ago... As soon as we reboot I'll toss it in...

Could someone with revision C Opteron (Bok?) try a small test under Linux in 64bit mode?

Please download this ZIP file and run the included "readtest" (source code is included too): [URL=http://www.informatik.uni-rostock.de/~mw212/readtst.zip]http://www.informatik.uni-rostock.de/~mw212/readtst.zip[/URL]

It does a read loop using MMX and SSE2 floating point and integer instructions.

Thanks.

Hopefully not too far off topic...
If I were wanting to purchase an Opteron now, which is the right one to get for single cpu?
940 pin?
939 pin?
740 pin?
Which motherboard?
Do we need to wait another month ? :surrender
TIA

@Ironbits:

Well, you can already buy an Opteron. In future they will still have 940 pins. Only Athlon 64 FX will have 939 (no SMP but dual channel) and Athlon 64 will have 754 pins (single channel). There are a lot of motherboards around.

Just look what socket they have and buy the CPU accordingly. BTW the 754 pin Athlon 64 is only a few percent slower than an equally clocked Athlon 64 FX. In most cases the single channel has very little to no impact except on the price which will be lower by a significant amount :grin:

The Athlon 64's won't be one month late. And look out for MoBo+CPU combo's. There will be special offers where you can save a lot.