- Joined
- Sep 7, 2011
- Messages
- 2,785 (0.58/day)
- Location
- New Zealand
System Name | MoneySink |
---|---|
Processor | 2600K @ 4.8 |
Motherboard | P8Z77-V |
Cooling | AC NexXxos XT45 360, RayStorm, D5T+XSPC tank, Tygon R-3603, Bitspower |
Memory | 16GB Crucial Ballistix DDR3-1600C8 |
Video Card(s) | GTX 780 SLI (EVGA SC ACX + Giga GHz Ed.) |
Storage | Kingston HyperX SSD (128) OS, WD RE4 (1TB), RE2 (1TB), Cav. Black (2 x 500GB), Red (4TB) |
Display(s) | Achieva Shimian QH270-IPSMS (2560x1440) S-IPS |
Case | NZXT Switch 810 |
Audio Device(s) | onboard Realtek yawn edition |
Power Supply | Seasonic X-1050 |
Software | Win8.1 Pro |
Benchmark Scores | 3.5 litres of Pale Ale in 18 minutes. |
The problem there is that the design goal was an architecture aimed squarely at the high ASP enterprise sector. The APU design as originally envisioned (10h based) wasn't actually too bad, and had AMD's foundries (later GloFo) delivered Llano might have had more impact. It was a management decision to starve the company of R&D funds, it was a management decision to deprive their own foundry business of income from third party fabbing, it was also a management decision to pursue a high overhead CPU architecture* when Intel bet on a mobile-centric high IPC arch, and it was also a management decision to sell off AMD's baseband and mobile GPU IP, which kind of indicates where their thinking was in 2006-07 when Bulldozer was being drawn up.I wholeheartedly disagree.
We have one purpose. As high of performance within a reasonable TDP as possible.
That is of course a huge oversimplification, but to say they don't understand that isn't true, what they have done is to allow the design teams to run in multiple directions and end up getting to the end of their leash still running full tilt.
* “Bulldozer” is actually very well aligned with server workloads now and on into the future. In fact, a great deal of the trade-offs in Bulldozer were made on behalf of server, and not just one type of workload, but a diversity of workloads. It's very important that a server not just do one thing well; it needs to do a range of things well - AMD Chief Architect Chuck Moore
Good luck with that. Mike Butler, Bulldozers architect, has been at Samsung for almost two years.Whoever keeps dreaming up the shitty ideas for "modules" when we still have so many single threaded applications needs to be beaten.
Quite simply, AMD blinked in a stare-down with Intel. AMD had a vision of what they thought was competitive, Intel talked up Nehalem, and AMD scuttled back to the drawing board to make an architecture better than Intel's vapourware (remember Nehalem as originally touted by Intel was supposed to be closer to Sandy Bridge with integrated graphics). Development basically stopped and was repurposed while AMD dithered over what they needed to include to counter Nehalem - which is what I meant by AMD's management lacking a clear end goal. AMD's goal wasn't a definitive product, it was some nebulous accretion of features added depending upon what Intel was doing allied with a lot of crossed fingers that their foundry could produce on time.AMD had a great idea, dual core, then quad core, then its like they made that a god, always make more cores, never waiver on the making of more cores, instead of better and more logic throw in two or four more cores.
Probably not a lot else that can be done TBH. A CPU architecture takes upwards of five years to develop and bring to market. Bulldozer as originally envisioned would have been competing with Intel's Bloomfield and Lynnfield desktop processors - all on 45nm. Halting development and repurposing the design meant that the roadmap slipped and things got pretty unfavourable pretty fast - behind in architecture, behind in IPC, behind in process node.When performance failed to materialize lets throw hotdogs down this hallway in the form of PR spins and pure Ghz to fill up the gaps.
AMD FX 85Ghz, now with higher TDP!! (Not for use below the arctic circle, may cause permafrost melt, may kill polar bears, may cause heat stroke)
AMD's problem is that management have almost always been reactive rather than proactive. When they've grabbed the bull by the horns it has paid off handsomely (adoption of MIPS features within x86 architecture, AMD64), but too often they tend to be content to play follow-the-leader. It's hard enough to develop product on your own timetable without changing horses midstream to also keep up with a competitors cadence.