7 ms·
Bulldozer, AMD’s Crash Modernization: Front End and Execution Engine
- dist1ll 4y ago> But as you might think, nobody at AMD envisioned it that way in the planning or design stages. No engineer would ever start working with the idea to “build a shit product”; That made me chuckle. There are many reason for why a design turns sour, but actual malice is rarely on of them - although it may feel that way for the user.
- brnt 4y agoOn the other hand: I can very well imagine some senior staff rolling eyes but feeling unfree to 'spoil the mood' by explaining how certain choices are going to come back and create problems later on. I find it superinteresting, but also superhard to have that sort of feedback as things are ongoing. I've seen both happen (old hats hating progress too), but I was never successful (not in those larger above-my-paygrade-but-visible-nonetheless) in having a conversation about how we're having the discussion and whether or not every point/everyone is seriously hearda and considered. There can be a 'mood' that is overriding, and I haven't found a way to override the mood. Things tend to have to break down before that can happen.
- CoastalCoder 4y agoI've experienced that as well, albeit in the software realm. It reminds me of the myth of Cassandra.
- deaddodo 4y agoThe myth of Cassandra?
- Tomte 4y agoGreek mythology: https://en.m.wikipedia.org/wiki/Cassandra https://en.m.wikipedia.org/wiki/Cassandra
- moffkalast 4y agoThe myth that Cassandra DB is faster than Redis for large databases, but nobody believes it. /s
- fallous 4y agoI've found that when in discussions where choices made now will create problems in the future it's useful to raise that issue by couching it as a potential issue of priorities. Yes, the short-term solution may create problems in the long-term but sometimes the short-term priorities are more important. Taking on a tech debt isn't inherently bad, it's when you take it on unknowingly or without a full understanding of the terms of that debt that it goes bad. Just as with any other debt, the cost in the long term must be balanced against the needs of the short term. And as with any other debt, if someone takes on that debt and then decides to ignore repayment there will be much wailing and gnashing of teeth when the bill comes due. ;)
- muxator 4y agoHowever, more often than not the person having to repay that debt is not going to be the one that created it. The fairness of this dynamic has at least to be taken into consideration.
- deleted 4y ago[deleted]
- irusensei 4y agoCue the “fine wine” bulldozer memes. Are the memes grounded on reality though? Plenty of youtube videos from 2020 or later showing the 8350 displaying some impressive results for their age, specially on proper multithreading stuff.
- BlueTemplar 4y agoSeems like where AMD went wrong is expecteing programmers to be able to easily take advantage of multithreading... while in reality the extra performance is often not worth the extra complexity, and sometimes it's even impossible to implement ?
- zokier 4y agoWell, one big aspect is gaming, and in particular consoles at that time only had few cores. That changed few years later with ps4/xb1, but of course it took bit longer for gamedevs to catch up. It didn't help that it was also time when Intel was at top of their game, still pushing significant single-thread perf improvements. Sandy Bridge, which was Bulldozers main competitor, was exceptionally successful launch on its own right
- deleted 4y ago[deleted]
- adrian_b 4y agoNo, where AMD went wrong was in marketing. For some years, and especially during the last six months before the Bulldozer launch in 2011, AMD has continuously made various claims about its performance, always stressing that it will crush Sandy Bridge, due to having a double number of "cores". Immediately after launch, all the AMD claims were proved to be shameless lies. There is absolutely no excuse for AMD. Intel had published accurate information about the performance of Sandy Bridge, one year in advance. Even without the advance publication, the performance of Sandy Bridge could have been easily extrapolated from the evolution of Penryn, Nehalem and Westmere. The performance of Bulldozer was determined by design decisions taken by AMD at least 3 to 4 years before its launch. Therefore, during the last 6 months, when they have lied the most, they knew perfectly well that they were lying and it should have been obvious to them that this is futile, because the lies will be exposed by independent benchmarks immediately after launch. For most operations, a so-called Bulldozer "module" (with 2 "cores") had exactly the same execution resources as a Sandy Bridge core, while for a few operations, like integer multiplication, a Bulldozer "module" had even less execution resources than a Sandy Bridge core. The common FPU of 2 Bulldozer "cores" was more or less equivalent with the FPU of a single Sandy Bridge core. The Bulldozer integer "cores" were stripped down in comparison with the cores of the previous AMD CPUs, e.g. a new "core" had 2/3 of the addition throughput and 1/2 of the multiplication throughput of an old core. So 2 Bulldozer integer "cores" were together barely faster than one old AMD core, while a single Sandy Bridge core was faster than them, by having an equal addition throughput, but a double multiplication throughput. Bulldozer could have been a decent CPU, if only AMD, instead of describing it as a 4-"module"/8-"core" CPU, would have described it as a 4-core/8-thread CPU, which matched Sandy Bridge, except that in Sandy Bridge the 2 threads of a core shared dynamically most execution resources, while in Bulldozer only a part of the execution resources were shared dynamically, e.g. the FPU, while the rest of the execution resources were allocated statically to the 2 threads of a core, which is less efficient. Such a description would have set correctly the expectations of the users, and they would not have felt cheated. I am pretty certain that the huge disappointment that has accompanied the Bulldozer launch has hurt much more the AMD sales than they might have gained from the buyers lured by the false advertising about the 8-core monster AMD CPUs, which should easily beat the puny 4-core Intel CPUs.
- johnklos 4y agoI remember deliberating between AMD's eight core FX-8150 and the latest Intel Sandy Bridge in early 2012. Even though lots of people consider Bulldozer to be an AMD misstep, I don't regret my choice: AMD's eight integer cores performed favorably compared with the four real cores plus four hyperthreads of the Intel. Considering I bought it to be used primarily for compiling, it was a good choice. This is an interesting read, and seeing the design choices with knowledge of how things turned out later makes it even more interesting.
- BlueTemplar 4y agoI am still using a FX-8xxx (and probably will until RISC-V will beat it), and haven't even bothered overclocking it yet. Anyone knows what kind of issues having "The frontend, FPU, and L2 cache [] shared by two threads" causes compared to 2 real cores / 2 hyper threads on 1 core / 4 hyper threads on 2 cores ?
- Dalewyn 4y agoMy ELI5 understanding is it's a problem of throughput and resource availability. Long story short, running two threads with only enough hardware to run just one at full speed means any thread that tries to run at full speed will not be able to.
- deaddodo 4y agoIt would work fine with double integer loads, or heavily integer based work with the occasional FPU necessity. The problem wasn't throughput as much as the latter: it didn't have enough FPU resources and would get deadlocked waiting on availability; so would behave in the worst case (as a single core) more often than not.
- paulmd 4y agoThe problem isn't execution unit throughput at all, it's decode, where running the second thread on the module would bottleneck the decoder and force it to alternate between servicing the two threads. And this doesn't really matter what is running on the other core, it simply cannot service both cores at the same time regardless of instruction type even if the first core isn't using all its decode. If it has to decode a macro-op, it can even stall the other thread for multiple cycles. > Each decoder can handle four instructions per clock cycle. The Bulldozer, Piledriver and Excavator have one decoder in each unit, which is shared between two cores. When both cores are active, the decoders serve each core every second clock cycle, so that the maximum decode rate is two instructions per clock cycle per core. Instructions that belong to different cores cannot be decoded in the same clock cycle. The decode rate is four instructions per clock cycle when only one thread is running in each execution unit. ... > On Bulldozer, Piledriver and Excavator, the shared decode unit can handle four instructions per clock cycle. It is alternating between the two threads so that each thread gets up to four instructions every second clock cycle, or two instructions per clock cycle on average. This is a serious bottleneck because the rest of the pipeline can handle up to four instructions per clock. > The situation gets even worse for instructions that generate more than one macro-op each. All instructions that generate more than two macro-ops are handled with microcode. The microcode sequencer blocks the decoders for several clock cycles so that the other thread is stalled in the meantime. https://www.agner.org/optimize/microarchitecture.pdf https://www.agner.org/optimize/microarchitecture.pdf
- unity1001 4y agoAMD FX-8150 worked well for me for a loooong time. From gaming top titles of the time to programming to other tasks.
- heelix 4y agoI had one running as an ESX server for a long time. Back then, this was the cheapest path to 8 cores and was ideal for carving up into smaller VMs. The 8 core/32M specs were what was the most you could put on a personal 'free' box.
- mlvljr 4y ago[dead]
- chaboud 4y agoWell before Bulldozer had taped out, AMD briefed us on the high level processor plans (our software was included in BAPCo Sysmark and we'd been a very early adopter of AMD64, so we had lots of these meetings). I told them that it was a total mismatch for our workloads (audio and video production tools) and would prove to be a bad fit. They protested at first, as our inputs and outputs were fixed point formats and the doubled-up integer/logic units would allow us to thread more. That's when I spelled it out: 1. Our business logic and UI each basically operated in single threads. 2. Our intermediate audio and video processing buffers were floating point or moving in that direction in the future. 3. Wherever possible in filtering and effects, we avoided branching, relying on zero-folding in vector instructions. I went on to explain where they'd be in trouble for game engines, document processing, and other key use-cases. Their hardware architects slowly sank in demeanor over the course of that all-day meeting. I later heard from contacts at AMD that it was an "oh shit" moment for them. That said, having been at Sony at the time, we'd gone down the long dark road of the Cell... Sometimes people try bold and interesting things that don't work. Bulldozer was definitely one of those, and it should have been killed (or at least diverted), like Larrabee. Nonetheless, AMD survived, and their current architectures owe some of their thinking to the hard-learned lessons of Bulldozer.
- zozbot234 4y agoMeanwhile the "efficiency cores" in the latest processors (both x86 and ARM) are basically optimal for precisely those highly threaded integer workloads. Bulldozer was just too early for its time.
- phkahler 4y ago>> Each module was designed to run two threads. The frontend, FPU, and L2 cache are shared by two threads, while the integer core and load/store unit are private to each thread. If I recall correctly, they ended up calling each module 2 cores. I thought in the beginning that each module would be a single core running 2 threads. I've always thought the problem was marketing. If Bulldozer was sold as having half the cores, it's multithreaded performance would have been spectacular while single thread was meh. But some have said those modules were too big (expensive) to be sold as a single core. I have no proof, but the use of the word "module" seems to support the confusion around what constitutes a core vs thread.
- johnklos 4y agoThere is enough actual stuff so that each integer core is, in fact, a separate, distinct core. The issue is that there was only technically one FPU core per two integer cores. AMD paid out $12 million because they called these individual cores, and the case was decided against AMD because of the single FPU per core module: https://www.theregister.com/2019/08/27/amd_chip_compensation/ https://www.theregister.com/2019/08/27/amd_chip_compensation...
- monocasa 4y agoAnd they're not even the worse at that. The Ultrasparc T1 only had the one FPU shared among it's 8 cores. But I guess $12M is just the high end of nuisance money for AMD.
- paulmd 4y ago> and the case was decided against AMD because of the single FPU per core module: this has always been a massive oversimplification and misrepresentation from the AMD fanclub. the case was decided because of shared resources including the L2 and the frontend (fetch-and-decode, etc) which very legitimately do impact performance in a way that "independent cores" do not. Citing the actual judgement: > Plaintiffs allege that the Bulldozer CPUs, advertised ashaving eight cores, actually contain eight “sub-processors” which share resources, such as L2 memory caches and floating point units (“FPUs”). Id. ¶ 37–49. Plaintiffs allege that the sharing of resources in the Bulldozer CPUs results in bottlenecks during data processing, inhibiting the chips from “simultaneously multitask[ing].” Id. ¶¶ 38, 41. Plaintiffs allege that, because resources are shared between two “cores,” the Bulldozer CPUs functionally only have four cores. Id. ¶ 38–43. Therefore, Plaintiffs claim the products they purchased are inferior to the products as represented by the Defendant. Id. ¶ 39 This is completely correct: the chip only has one frontend per module which has to alternate between servicing the two "cores" and this does bottleneck their independent operation. It is, for example, not the same thing as a "core" used on Phenom and this significantly impacts performance to a hugely negative extent when the "second thread" is used on a given module. It's fine to do it, this same approach is used in SPARC for example, but SPARC doesn't market that as (eg) a "64 core processor", they market it as "8 cores, 64 threads". But AMD wanted to have the marketing bang of having "twice the cores" as intel (and you can see people representing that even in this thread, that programmers bought AMD for compiling because "it had twice the cores", etc). And that is not how anyone else has marketed CMT before or since, because it's really not a fair representation of what the hardware is doing. Alternately... if that's a core then Intel is definitely a core too, because basically CMT is just SMT with some resources pinned to specific threads, if you want to look at it like that. After all where is the definition that says an integer unit alone is what constitutes a core? Isn't it enough that there are two independent execution contexts which can execute simultaneously, and isn't it a good thing that one of them can use as many resources as possible rather than bottlenecking because of an execution unit "pinned" to another thread? If you accept the very expansive AMD definition of "core" then there's lots of weird stuff that shakes out too, and I think consumers would have found it very deceptive if Intel had done that like AMD, that’s obviously not what a “core” is, but it is if you believe AMD. AMD did a sketch thing and got caught, end of story. No reason they should call it anything different than the other companies who implement CMT. I hate hate hate the "AMD got skewered because they didn't have an FPU" narrative. No, it was way more than the FPU, and plaintiffs said as much, and it's completely deceptive and misrepresentative to pretend that's the actual basis for the case. That's the fanclub downplaying and minimizing again, like they do everytime AMD pulls a sketchy move (like any company, there have been a fair few over the years). And that certainly can include El Reg too. Everyone loves an underdog story. Companies getting their wrists slapped when they do sketchy shit is how the legal system prevents it from happening again and downplaying it as a fake suit over crap is bad for consumers as a whole and should not be done even for the “underdog”. The goal shouldn’t be to stay just on the right side of a grey area, it should be to market honestly and fairly… like the other companies that use CMT did. Simple as. To wit: NVIDIA had to pay out on the 3.5GB lawsuit even though their cards really does have 4GB. Why? Because it affected performance and the expectation isn't mere technical correctness, it's that you stay well on the right side of the line with your marketing's honesty. It was sketch and they got their wrist slapped. As did AMD.
- sylware 4y agojez... this web site content is really good. I even can view it cleanely and properly with a noscritp/basic (x)html browser like wikipedia. (irony ahead) What I will be able to complain about then?! :)
- Tempest1981 4y agoWhat does the title mean: "Crash Modernization"?
- projektfu 4y agoModernizing very fast and suddenly, under duress. adjective - "marked by a concerted effort and effected in the shortest possible time especially to meet emergency conditions" - Merriam Webster dictionary.
- nkurz 4y agoCrash here means something like "speedy" or "rushed". It refers to AMD's attempt to modernize their architecture in a hurry, and doesn't have anything to do with how recovers from or deals with crashes. I was also initially confused.
- leoc 4y agoNote also that that the expression should be read as "crash (modernisation program)", not as "(crash modernisation) program"
- Tempest1981 4y agoThanks -- all I could think of was crash dumps. Time for a vacation.