95C ... this has gotta be a typo....Quote:
Originally Posted by Lightman
Printable View
95C ... this has gotta be a typo....Quote:
Originally Posted by Lightman
No it's not a typo. They are modeling core frequency at high temperatures because most servers are running in tight blade cases, people in Africa want to use air cooling :p:, etc.Quote:
Originally Posted by JumpingJack
To be serious I think it is industrial standard for measurements. Look at speed modeling of other CPUs like this Intel 80core monster. It's speed was modeled at the same 95C temperature.
This of course has good prospects for us because if you will keep this core at around 65C then @1.15V you can go a bit higher than 2.8GHz on Quad core. :D . Add some volts and job done! 3GHz should be easy.... :woot:
Its not a fact, lol its only a delay. XD :fact: And friends tend to lend you things.Quote:
Originally Posted by brentpresley
Anyways back on topic...
Please by all means show us the K10 your friend has? We would all love to see. I mean if he really did show you these performance numbers why don't you/he post them? Any kind of numbers. If your being truthful with all your arguments please state/show more facts on what your saying. Not trying to flame or anything because my statment is not stated as such. Only your not the kind of person that backs up their clams very well, we all just want to know more. Thats what this thread is all about after all. :toast:
These processors can get hot. Opterons are built to take this heat. Server consissions range from 70C to 80C+ temps usoully in a standard blade. Some of us don't know about server condissions, but the ones that do should be taken word for word. It gets very hot in a blade server more then most like. lol Besides cpus are not that fragile. Xeons and opterons alike you would be amazed the punisment they can take in testing as well as 24/7 use.Quote:
Originally Posted by Lightman
Great find.Quote:
Originally Posted by doompc
I took this as fallows... :ROTF: :wierd: :rofl:Quote:
Originally Posted by LOE
I agree, only K10 has dual memory controllers in the specs. According to previous data in the past threads about K10. Current bandwidth on AM2 is 20GB/s it will nearly be 3x of that bandwidth wise. Double that on memory bandwidth. According to dalytech was it...Quote:
Originally Posted by accord99
http://www.channelinsider.com/print_...ls/191008.aspx
Quad-core parts and other Revision H parts are rumored to have two 64-bit independent memory controllers each with its own physical address space thus giving an opportunity to better utilize the available bandwidth in case of random memory accesses occurring in heavily multi-threaded environment. This approach is in a contrary to the previous "interleaved" design, where the two 64-bit data channels are bounded to a single common address space. It will be the first single-chip implementation of the non-uniform memory access architecture.
http://www.realworldtech.com/page.cf...0206035626&p=1
http://www.realworldtech.com/page.cf...0206035626&p=2
http://www.google.com/search?hl=en&q...rs&btnG=Search
Just some more info on K10 in previous threads. But you all should really read that thread to get the lowdown on K10. I should post a link on the front of the page as a continuation. And not constently rehunting for data having ppl acting like it never existed. Sometimes its silly for somebody to have to repeat themselfs. XD
http://www.xtremesystems.org/forums/...d.php?t=117702
Quote:
Originally Posted by LOE
Dont try and mix numbers in your favour. Core got 1 SSE port thats 64bit. Core 2 got 3 SSE ports thats 128bit. Yet Core at same FSB/Clock aint much slower than Core 2. And thats with all the rest of the improvements too.
AM2's memory bandwidth is 12.8GB/s. If you plug in a Barcelona core into an AM2, that's all you get since there is physically only two channels connecting the memory to the socket.Quote:
Originally Posted by Grayfox84
Intel's current DDR2 memory controllers are already this way.Quote:
http://www.channelinsider.com/print_...ls/191008.aspx
Quad-core parts and other Revision H parts are rumored to have two 64-bit independent memory controllers each with its own physical address space thus giving an opportunity to better utilize the available bandwidth in case of random memory accesses occurring in heavily multi-threaded environment. This approach is in a contrary to the previous "interleaved" design, where the two 64-bit data channels are bounded to a single common address space. It will be the first single-chip implementation of the non-uniform memory access architecture.
Quote:
Originally Posted by accord99
Yeap! At the rated PC6400 speed of course. At the moment AMD and few other companies are trying to push higher memory specification through JEDEC. I heard PC8500 is target for them.
This would allow DESKTOP version of AMD Quad to get 17GB/s memory bandwidth...
Of course servers are different animals and I think maximum we will see would be PC6400 Registered dimms (DDR-II 800MHz :) )
Regarding SSE2, I still expect Core 2 to have edge over the K10, as it has a higher peak theoretical throughput..
Core 2 can issue a max of 6 SSE instructions per cycle, while the K10 can do 3.
Ofocurse, there are other factors involved other than peak SIMD throughput, like latency and memory bandwidth, and the K10 will have the edge there.
But not enough to trounce C2D IMO.
As for INT, C2D should still maintain a healthy lead as the C2D is a beast in INT. It will be interesting to see which processor holds the performance crown for gaming, as games tend to be far more INT based than FP.
Core Duo has 2 64-bit SSE2 ports, not 1.Quote:
Originally Posted by Shintai
As for the closer than expected performance delta between C2D and CD, I put it down to two things:
1) Merom is FSB limited at 667, far moreso than Yonah.
2) Yonah was already a very efficient high IPC processor. Actually, it was even faster than the K8 clock for clock in everything but FP intensive apps.
I'm willing to bet this will be addressed in Penryn.Quote:
Originally Posted by doompc
I don't know how accurate this information is. As far as I know, the K10 can issue 2 SSE operations, and one SSE MOV per cycle in the floating point store pipe.Quote:
On SSE execution K10 has little advantage.
Core2 has 3 SSEs plus one load and one store units.
K8 has 3 FPUs (that do SSE) plus the load/store unit that do two loads/stores per cycle, on K10 the FPUs are widened to 128 bit so it can do 3 128 bit SSE per cycle plus 2 load/stores.
So Core2 does 3 SSE, 1 load and 1 store. K10 does 3 SSE, 1 load and 1 store or 2 loads or 2 stores.
http://www.xbitlabs.com/articles/cpu...amd-k8l_5.html
So thats three instructions peak. Core 2 on the other hand, can potentially do double the K10's SSE issue rate.
Carfax, it's not clear if the FMISC unit (that do FLOAD in K8) will be widened to 128 bit. If not could not do 1x 128 bit SSE Load per cycle.
Core2 can theoricaly issue 6x micro-ops per cycle, and it decodes a maximum 2+3 instructions, but it fetches 16 Byte, that's only 128 bits. With the data on bufer waiting to be decoded it may decode an average 3 instructions per cycle.
I bet the 32 Byte instruction fetch will keep K10's FPUs much busier than Conroe's.
Doompc, do you think it's possible that Intel could implement a 32 byte instruction fetch in Penryn with the extra transistors?
How radical a change would it be to do something like that?
Carfax, I think so, but Intel has not commented anything on this subject.
LOE, we don't have info on that. But even if FMISC is still 64 bit the decoder may simply route the SSE Loads to the Load/Store unit.
Weren't those the same folks who said the Conroe Tests were Bogus and rigged? So why should we believe them?Quote:
Originally Posted by MAS
I'm sorry to say that you've got a messup.Quote:
Originally Posted by Carfax
1) C2D has 6 uOps per cycle. K10 has 3 SSE per cycle. See the difference?
only scalar SSE operations are single uOps while the vector operations are typically 2-4 uOps.
Don't believe? Read here...
just in case you did not know: mOps fusion - old K8 uses it several years already.
Hehehe!Quote:
Originally Posted by brentpresley
Thank you! :DQuote:
Originally Posted by brentpresley
Thank you that you did not break my expectations! I was sure that all fanboys will immediatelly stop thinking right after they read CORE DUE not c2d... :clap:
ok, enough laugh.
I repeat that link this way:
http://www.intel.com/technology/itj/...oved_cores.htm
See? That's the term link it and it is the only purpose of link.Quote:
only scalar SSE operations are single uOps while the vector operations are typically 2-4 uOps.
Let me inform you that's why fanatism is so bad thihg.Quote:
Originally Posted by brentpresley
I see I should bring my point explicitelly:
c2D has up to 6 nOps per cycle.
not SSE instructions per cycle!
uOp is NOT SSE instruction!
and thus the assertionis wrong.Quote:
Core 2 can issue a max of 6 SSE instructions per cycle, while the K10 can do 3.
Additionally:
http://arstechnica.com/news.ars/post/20061011-7961.htmlQuote:
If you just compare floating-point addition and multiplication, both Core and K8L can do four (packed) double-precision operations per cycle (2 x fadd + 2 x fmul) or eight (packed) single-precision operations per cycle (4 x fadd + 4 x fmul). The fact that there's FP/SSE MOV hardware on each of Core's three main issue ports will give the Intel part an edge in handling memory traffic, though.
and for "in handling memory traffic" - AMD will balance it with other technic. So only time will show if it is 10% or whatever else...
ok, first, you admit that
that is it.Quote:
C2D has 3 128-bit SSE units
next,
wrong again...Quote:
That STILL only gives a MAXIMUM throughput of 4 64-bit SSE instructions per cycle.
you lost FSTORE