Dual-Interlagos Benchmarks

[Spooony]

Jf now when will we get a mobo to overclock that thing. 32cores mmm since Sandy got a cold surely that thing leaks volts like 1930 condom and will do huge frequencies

 

[DedEmbryonicCe11]

Jf now when will we get a mobo to overclock that thing. 32cores mmm since Sandy got a cold surely that thing leaks volts like 1930 condom and will do huge frequencies

Weren't the other dozens of times he answered the same question enough?

 

[drescherjm]

Jf now when will we get a mobo to overclock that thing. 32cores mmm

Besides the fact that JF said the dual socket platform will not support overclocking I seriously hope your planned usage of this > $5000 US beast is not for gaming or general desktop usage.

 

[sirmo]

That would make the Stream results irrelevant. Do you have a link for that claim ?

http://www.futuretech.blinkenlights.nl/c-ray.html

 

[jeremyshaw]

Besides the fact that JF said the dual socket platform will not support overclocking I seriously hope your planned usage of this > $5000 US beast is not for gaming or general desktop usage.

yeah, we've been down this road, lol. He won't even give an answer as to allowing their board partners to do such a thing on their own, other than "we don't support overclocking."

 

[Topweasel]

yeah, we've been down this road, lol. He won't even give an answer as to allowing their board partners to do such a thing on their own, other than "we don't support overclocking."

What do you expect from a company man. In the end he has to toe the company line. If AMD says they don't support overclocking, whether or not Asus plans on making a board that does, he can't really say anything other then AMD doesn't support it.

Just like this whole AM3-AM3+ debate that raged up. AMD isn't supporting BD in AM3+. What that means to AMD vs. Us, doesn't matter to JF he really can't say anything other then AMD isn't supporting it. So really he can't even get into specifics of whether it will even fit into the socket.

 

[pxc]

Damage control engaged.

 

[veri745]

The IPC is per thread , not per core. BD's multithreaded front end dispatches instructions from 2 threads. Even if it has 16 FPUs it is running 32 threads.

Is the "not real core" the last defense ? I mean, all that matters is per socket performance and single threaded one.

What he's saying is that a FPU-heavy benchmark will provide drastically different results than a int-heavy benchmark since there's 2x the number of int cores. as FPUs.

You can still compare Interlagos to Xeon, but only as far as the FPU is concerned. In order to do and Int comparison you need an Int benchmark.

Seems pretty obvious, but still...