Very disappointing: no TSX for K processors and I was hoping for higher memory clocks supported...I might just go with Ivy-E then.
SR? I don't think even AMD knows how much faster it will beWho now believes Steamroller (If ever released as a AM type socket ) will actually have 20% IPC increase?
It's tom's - so i'll wait final silicon and more leaks\real reviews - but damn it's disappointing.
Seems like the way forward really isn't increased IPC.
But maybe a hardware based solution to the thread problems of software.
I don't have confidence software will ever truly efficiently at some point solve the the many thread problems mainstream wise.
+1.
Only thing I'd like to see in HW desktop parts is their ability to OC well without high volts, and if they get rid of the frog snot TIM on their K parts.
Yep. Plus, the only big gains are going to be on recompiled or new apps. I expect we'll see some nice gains in CPU physics on updated gaming engines.
TSX' main advantage will be on the server side when the number of threads is >> than the number of cores.
TSX targets a certain class of shared-memory multi-threaded applications; specifically multi-threaded applications that actively share data.
The changes are absolutely there to hit a 20% IPC increase. AMD's claim was actually 30%, FYI. Go read up on it: http://www.brightsideofnews.com/new...core-architectural-enhancements-unveiled.aspxWho now believes Steamroller (If ever released as a AM type socket ) will actually have 20% IPC increase?
Not as such.
TSX however is a hyped term it seems.
The way I see it Intel just gave AMD 2 free generations to catch up on overall performance. If steamroller can realize a 20%+ IPC increase things might get interesting again.
My comment wasn't so much about the process tech, but that is a part. There are just a lot of power-hungry, yet huge performance boosting design decisions going into Steamroller -- first of which is the doubled decode width. The uop cache should help, along with the dynamic L2, but how they'll manage to maintain clock speed while tackling everything else is beyond me. Thankfully GloFo's 28nm library is reportedly very similar to their 32nm library, so hopefully AMD will run into less issues this time around. But I mean come on, 30% is a lot. That puts AMD back in the game, and then some. 30% IPC is certainly doable, but can we really expect clock speeds to stay the same?
The changes are absolutely there to hit a 20% IPC increase. AMD's claim was actually 30%, FYI. Go read up on it: http://www.brightsideofnews.com/new...core-architectural-enhancements-unveiled.aspx
IPC won't be the problem -- it's clock speed that will be the issue.
As for Haswell: Shame about TSX. I'm hopeful that we won't need to buy a K series processor to overclock, though. The important information was left out -- Haswell's performance was in line with expectations; no surprise there. But what about power consumption? How well will it overclock? Those people that grab Ivy Bridge instead will be eating their hats if Haswell hits 5.5GHz. At the very least, we should be able to expect more chips consistently hitting the magic 5.0. It's too early to draw conclusions, though -- too many unknowns right now.
The way I see it Intel just gave AMD 2 free generations to catch up on overall performance. If steamroller can realize a 20%+ IPC increase things might get interesting again.
Uh, they doubled the decode width from 4 ops per cycle to 8. That's not hyping anything -- it's fact. And this slide is pretty clear about the 30% claim:AMD didnt say 30% IPC on the entire core. Its simply 30% faster decode on the frontend. And its based purely on simulation. So lets not hype it.
Uh, they doubled the decode width from 4 ops per cycle to 8. That's not hyping anything -- it's fact. And this slide is pretty clear about the 30% claim:
http://images.anandtech.com/doci/6201/Screen Shot 2012-08-28 at 4.38.09 PM.png
"Hyping" Steamroller is the absolute last thing that I'm doing. I've made my doubts about clock speed abundantly clear.
They've listed the changes that are coming, and they're substantial. If you take a look at this article, it highlights the biggest weaknesses of Bulldozer. Piledriver addressed one of them (clock speed), and Steamroller will address the other two (branch misprediction penalty and L1 instruction cache). Plus, we're getting double the decode width.But I believe its marketing play when that slide is saying "30% OPs per cycle improvement" rather than saying "30% performance per cycle improvement".
How do you quantify individual improvements without being the head engineer of the design?
And the hype part is believing 30% on a unconfirmed leak versus 15% on official claims. How many times have we been disappointed even with "official figures"? AMD isn't alone of course. Intel, and others in the CPU industry does the same as well.
as much as the performance increase is not impressive in many of the things they tested,
this was good
![]()
and they didn't include power usage tests.
Uh, they doubled the decode width from 4 ops per cycle to 8. That's not hyping anything -- it's fact. And this slide is pretty clear about the 30% claim:
http://images.anandtech.com/doci/6201/Screen Shot 2012-08-28 at 4.38.09 PM.png
"Hyping" Steamroller is the absolute last thing that I'm doing. I've made my doubts about clock speed abundantly clear.
They've listed the changes that are coming, and they're substantial. If you take a look at this article, it highlights the biggest weaknesses of Bulldozer. Piledriver addressed one of them (clock speed), and Steamroller will address the other two (branch misprediction penalty and L1 instruction cache). Plus, we're getting double the decode width.
AMD's taking IPC to the moon with SR. These CMT cores will be virtually indistinguishable from typical ones. I just don't know how they're going to implement all of this while staying within the same thermal headroom. And it's AMD after all -- it's better for my well being and sanity if I chalk things up to being a letdown before they release. With Intel, if they say they're shooting for the moon, I'll expect them to make it there, or at least get close.