- Joined
- May 29, 2005
A couple key parts of the Ars article linked above that I agreed with:
That is pretty much what I have been thinking. People keep saying that this chip is made for the future, the future is more going to depend on how much/if developers move away from single-threaded coding and code to scale to multiple cores. It also seems that Piledriver would/could be a much better solution as it should be able to have its own FPU separate to assist in calculations (or to put them off to a discrete card -- although for games that isn't much of an option unless you would have a card akin to a Physx card just for calculations...)
For game developers, there's an added wrinkle to using the GPU for computation: games already use the GPU for graphics. Moving workloads away from the CPU just means overtaxing the GPU.
AMD's dreams may come true, but the change won't happen during Bulldozer's life. The software of today benefits from strong single-threaded performance, and it benefits from giving the CPU plenty of floating point resources. The same will be true of the software of tomorrow. Piledriver, Bulldozer's follow-up, will also be too soon for this kind of software. So will Piledriver's 2013 successor, Steamroller, and its 2014 follow-up, Excavator. Innovation and progress in the computer world is fast in some regards, but extremely conservative in others; just look at the number of people still using the decade-old Windows XP. The kind of revolution that AMD is counting on could easily be ten years away, if it happens at all.
Intel's approach—to have fewer, wider cores (and, with HyperThreading, to share entire cores between threads)—will continue to give its processors the lead in most workloads for the foreseeable future. It will continue to be a much better match to the software that actually exists, rather than the software that AMD would like to exist.
That is pretty much what I have been thinking. People keep saying that this chip is made for the future, the future is more going to depend on how much/if developers move away from single-threaded coding and code to scale to multiple cores. It also seems that Piledriver would/could be a much better solution as it should be able to have its own FPU separate to assist in calculations (or to put them off to a discrete card -- although for games that isn't much of an option unless you would have a card akin to a Physx card just for calculations...)
Longer term, AMD has started talking up Bulldozer's first revision, Piledriver. Due next year, AMD projects that Piledriver will be about 10 percent faster than Bulldozer currently is. Piledriver will change some of the execution units to support additional floating point instructions, but is not expected to be a major overhaul of the processor's design. Where the 10 percent gain comes from is unclear (you don't gain 10 percent improvements on existing workloads just from adding support for extra instructions), but fixing some of the obvious problems—slow cache, insufficient execution resources—could be the answer.