7 ms·
AMD ships 16-core x86 3ghz CPU
- ck2 14y agoA decade ago I figured we be at 10ghz by now, didn't count on more cores instead of faster. Of course you cannot compare 1ghz in 2003 to 1ghz in 2013, way more efficient per clock cycle with the right code.
- GotAnyMegadeth 14y agoA decade ago I figured we be at 100 cores by now, didn't count on using quantum computing instead of adding more cores. Of course you cannot compare 10 cores in 2013 to 10 cores in 2023, way more efficient per core with the right code.
- marshray 14y agoBut we are well over 100 cores right now ... on GPUs. Yes, they're sort of different animals. This is what change looks like. Our intuition can be correct yet we still have to be open enough to recognize it when we it actually happens. OTOH, quantum computers continue to not ship as a product.
- wmf 14y agoNot really; GPUs have have hundreds of "cores" but only 8-16 cores.
- bunderbunder 14y ago> didn't count on using quantum computing instead of adding more cores. And you probably still shouldn't. Quantum computing only provides a speedup for a very specific set of problems. For the vast majority of everyday computing tasks, quantum computing offers no practical advantage over classical computing.
- dillona 14y agoUnfortunately with clock speeds, we wind up bumping up against fundamental laws of physics. At 10Ghz, something moving at the speed of light can only go around 3 centimeters per clock cycle. Take out gate delays, and you wind up with something that just isn't practical.
- ck2 14y agoYou're thinking 2-dimensionally ;-) Our future CPUs should be tiny cubes, not flat chips. Distance to each point in 3 dimensions is shorter.
- miahi 14y agoYou cannot efficiently cool a cubical CPU.
- lovamova 14y agoMaybe it won't need cooling.
- xtc 14y agoNot yet.
- powertower 14y agonanotubes
- dsr_ 14y agoTake eight chips. Stack them, insert spacers and bridges from top to bottom, and connect them via BGA or pins or what-have-you on the very top and very bottom chips. Now turn them sideways, so they rest on the edges. Put the stack in a small ceramic container with copper bottom and top. Fill with a high efficiency thermal transfer fluid, and make sure the convection currents flow properly. There you go, small matter of engineering.
- miahi 14y ago
- bunderbunder 14y agoI suspect that even just looking at single-core performance it would be hard to make a 10GHz CPU that approaches what we're doing with 3GHz nowadays. Take Pentium 4 - which used the architecture Intel was working on when they were predicting that they'd have 10GHz CPUs by now. Passmark's score for a 3GHz Pentium 4 is 384. An i7-3940XM runs at 3GHz, and gets a score of 10,490. That's a quad-core computer, so I'm going to go ahead and be sloppy by dividing by 4 to get a score of 2622.5 per core. In other words, a single i7 core is doing almost seven times as much work per clock cycle. And assuming they only ramped up the clock rate, the P4 would have to be running at over 20GHz to match what the i7 is doing on a per-core basis. Given the heat dissipation problems that come into play with high clock rates, that seems like a doubtful proposition. In hindsight, it looks like Intel definitely made the right choice by dumping the NetBurst plan and instead letting clock rates stagnate (they've even retracted a bit from the high water mark) while designing the processor core to do a lot more with each cycle.
- 0xABADC0DA 14y ago> P4 would have to be running at over 20GHz to match what the i7 is doing on a per-core basis. Seems to me memory getting 10x more bandwidth and cache getting 8x larger probably accounts for the majority of the performance differences between these processors not instructions per cycle, which I think has gone up by more like 2x. So a Pentium 4 with current memory and cache would need to be more like 8 Ghz if it scaled linearly like that (P4 had ~3 instructions per cycle, i7 ~7-8). http://en.wikipedia.org/wiki/Instructions_per_second http://en.wikipedia.org/wiki/Instructions_per_second
- alanctgardner2 14y agoIt's really a shame how AMD's per-thread performance has been lagging Intel. Maybe it's just their postition as an also-ran in a basically monopolized market (desktop CPU manufacture), but I've always seen them as ahead of the curve. They were optimizing per-cycle performance with Athlon while Intel was still pushing higher clocks. They moved to 64-bit while Intel was still pushing higher clocks. Now that Intel has turned their attention more fully to optimizing their per-clock performance (and pulled ahead by a full generation in fab technology), AMD hasn't really had a leg to stand on. Price and low-power are OK, but ARM is already strong in those areas, and ARM servers are becoming more likely by the year. AMD needs something more transformative than massively-parallel chips and high frequencies. I know it's a long shot, but could they try to go the way Intel did with Itanium, and invent a new architecture/instruction set specifically designed for server workloads? People have broadly expressed interest in ARM, but the support isn't there right now. If AMD had a new RISC architecture with awesome support and incentives for developers to target it, they might be able to steal share from x64 and ARM chips.
- wtallis 14y agoAMD has already announced that they'll be selling ARM chips under the Opteron brand. They're going to be used in SeaMicro servers.
- alanctgardner2 14y agoI have heard about this, but AMD really needs to throw their weight behind getting important software stacks onto ARM. If they can't convince big players to ship ARM builds of software, they're not going to get the kind of market share they need.
- SwellJoe 14y agoLinux already runs on ARM, and there are multiple distros that support it. Most of the web runs on Linux, Apache, MySQL, and PHP/Python/Ruby/Perl, all of which run fine on ARM. I'd say that's a sizable server market that would already be happy on an ARM server. I would be. We run nothing on our servers that doesn't already compile on ARM. Then again, we've just switched to an entirely virtualized infrastructure running under KVM a few months ago, and ARM doesn't really have much in the way of hypervisor support. So, I guess there is some part of the software stack that ARM won't work for.
- swax 14y agoI want each process on my computer to have its own core.
- cpeterso 14y agos/process/thread/
- qdog 14y agoMaybe he doesn't use threading.
- cpeterso 14y agoI assume his processes have at least one thread.
- thebluesky 14y agoMaybe green threads
- swalsh 14y agoCan anyone with experience explain why the frequency of processors has basically stalled since hitting 3.x Ghz? I assume there is some kind of physical barrier, but i'm not sure what it is.
- anigbrowl 14y agoThey tend to overheat past that point in normal computers. Enthusiasts can get production chips running at up to 6GHz, but at that point they're having to use things like liquid nitrogen pumps. A passive radiator with an air fan can only conduct away so much heat. My newest PC (A core i7 or something, I forget exactly what now) has a heatsink that's bigger than my fist.
- zokier 14y agoI don't think the reason to use LN2 (liquid nitrogen) in extreme overclocking is because of the added heat generation. I bet water cooling (which is very "mainstream" compared to the more extreme solutions) could easily handle the extra heat. Afaik you actually need to reach very low temperatures to get the silicon work properly at the high speeds (I guess it has something to do with thermal noise and conductivity, but that's just guessing). And that is imho a sign that it's not just a power consumption / clockspeed tradeoff, but instead there are actually limits on how high you can go at room temperature.
- Jtsummers 14y agoTemperatures mainly. CPUs were approaching 4GHz a decade ago, but the power consumption and temperature output made higher speeds (and even those speeds) impractical. Multicore at those speeds would've (again) been power-wise impractical, so it made more sense to drop the speeds and have 2-4 cores until process improvements allowed clock speeds and core counts to both be higher.
- sliverstorm 14y agoMulticore at those speeds... In addition to power concerns of many fast cores on one chip, server chips (the multicore champions) tend to be larger dies, and place higher value on MTBF. I believe both of these factors work against super high frequency server offerings.
- zmmmmm 14y agoThis is a nice bump on what you can do currently with a standard monolithic server, which I think was 4x12 => 48 cores in the last generation. 64 high performance cores is pretty useful for a lot of modest sized big data computational tasks that otherwise would require you to step up to an entirely different (distributed) architecture.
- lorenzfx 14y agoI'm wondering where is AMD's counterpart to Intel's Xeon E3-12XX? ECC RAM, AES NI and a low price point and hopefully not too high idle power usage should make an attractive CPU. On a side note: does anyone know what happened to the "Zurich" 32XX Opterons?