• What
    is this?

    You've landed on the AMD Portal on AnandTech. This section is sponsored by AMD. It features a collection of all of our independent AMD content, as well as Tweets & News from AMD directly. AMD will also be running a couple of huge giveaways here so check back for those.

    PRESENTED BY

There are two important trends in the server market: it is growing and it is evolving fast. It is growing fast as the number of client devices is exploding. Only one third of the world population has access to the internet, but the number of internet users is increasing by 8 to 12% each year. 

Most of the processing happens now on the server side (“in the cloud”), so the server market is evolving fast as the more efficient an enterprise can deliver IT services  to all those smartphones, tablets and pcs, the higher the profit margins and the survival chances.

And that is why there is so much interest in the new star, the “micro server”.  

The Demand for Micro-Servers

The demand for very low power server is, although it is high on the hype curve, certainly not imaginary. When you run heterogeneous workloads, for example a mailserver, an OLAP database and several web and fileservers, some of these workloads will be demanding heavy processing power, others will be close to idle. In that case it is best to buy a dual "large core" CPU (or better) server, install a hypervisor and cut the machine up in resource pools. As one workload demands high processing power, your hardware and hypervisor will deliver it. Single thread performance will determine for a large part whether a complex SQL query is responded in a fraction of a second or several seconds.  The virtualization layer gives you extra bonuses such as high availability, no more unplanned downtime etc.

If your web based workloads are very homogenous and you know how much horsepower your webapplication needs, things are very different. The virtualization layer is just adding complexity and cost now. In this case it is a lot more efficient to scale out than to divide your heavy server into virtual machines.  The single thread performance has to be good enough to respond to a request quickly enough. But throughput demands can be handled by adding a load balancer in front of low power servers. It is much easier to scale this way.

The problem is that the your average server is not well suited for these kind of homogenous workloads. Yes, servers have become a lot more efficient by including advanced power management features. The introduction of CPU C-states and more efficient PSUs are among the top of technologies that saved a lot of power. However, even the most modern servers are still needlessly complex with lots of disk, network and other interfaces. A useless interface wastes a few hundred of mwatt and a less efficient PHY (Copper 10 Gbit Ethernet for example) wastes a few Watt, but in the end it adds up. 

Low power server CPUs
POST A COMMENT

80 Comments

View All Comments

  • silverblue - Wednesday, June 19, 2013 - link

    The 14nm node has been delayed until 2015.

    AMD's power usage would be better if they didn't implement CnQ on a per-module basis. Sharing resources is one thing, but power circuitry? The dynamic L2 is a big step in the right direction though, especially considering there's up to 8MB of it. They could always go inclusive on the caches as they did with Jaguar.
    Reply
  • Klimax - Wednesday, June 19, 2013 - link

    14nm wasn't delayed. (Only desktop won't receive it) Reply
  • 1008anan - Tuesday, June 18, 2013 - link

    Johann, in the latest 500 supercomputer list, three supercomputer sport 22 nm Intel Ivy Bridge E5 Xeons, including the most powerful supercomputer in the world (which uses 32 thousand Ivy Bridge E5s). The Ivy Bridge E5s, although not yet listed on the Intel Price list, are already available to select customers. Ivy bridge E7s come out in weeks.

    AMD's Warsaw gross margins will be squeezed.

    Let us assume you are right about power efficient micro-servers. Here is the problem:

    --Haswell ultra low power Xeon E3s come out in weeks
    --Avoton is likely released by September.

    What do you think this will do to Seattle and Berlin CPU gross margins? Keeping in mind how much Global Foundries rips AMD off in fabricating? Seattle CPU gross margins will be reduced by the fact that they cannot process native X86 code.

    This said, Seattle and Berlin CPUs will do okay in the 2nd half of 2014 (doubt AMD will be able to sell them in mass before the 2nd half of 2014). The real Seattle killers will be ultra low power 14 nm broadwell E3 Xeons and airmont--avoton's 14 nm successor. Both should be available in Q4, 2014.

    In 2015, Intel will release microservers powered by 14 nm multisocket Xeon Phis. Not PCI express Xeon Phis, but microservers consisting entirely of Xeon Phis that are better at processing X86 code then any ARM Holding derivatives.

    The medium term Intel roadmap for new server chips, and server noncore functionality will be extremely difficult for AMD to compete against.
    Reply
  • JohanAnandtech - Thursday, June 20, 2013 - link

    Seattle is not build by Global Foundries and I can imagine that the R&D on Seattle is quite cheap. After all, it is not like AMD had to reinvent the A57 core. And a lot can happen in 3 quarters, so I don't think Seattle should be compared to Airmont. Reply
  • bji - Tuesday, June 18, 2013 - link

    I think AMD still has a chance. Intel's most recent releases have shown that the per-core performance increases are asymptotically reaching the fastest x86 is going to get. Haswell was insignificantly faster than Ivy Bridge, which itself was only marginally faster than Sandy Bridge. It's clear that the year-on-year speed increases are quickly going to approach zero.

    In this environment AMD has some room to catch up. If they can hold on for a few more years it should give them some time to improve until their IPC is as good as or so close to as good as Intel's as to not really matter.

    Depending on how you look at it, it either sucks or is great that x86 is approaching its performance limit. Most would say it sucks because they always want something faster (even if 99.9% of the time they don't actually need it!). I actually am kind of happy that things are slowing down considerably. Rather than focusing on performance for performance' sake, perhaps we can start focusing on the entire computing infrastructure and make it work better for people instead of just faster. Lower power devices, more ubiquitous devices, more useful, more user friendly ... these are all great trends, and it's where the future competition in the computing world will predominantly be.

    It reminds me of gaming consoles and their effect on games. I know alot of people dislike the fact that consoles set a performance standard that it was no longer beneficial for most games to go beyond, leading to a sort of performance stagnation. On the other hand, companies could spend more resources focusing on making better games and less on higher and higher detailed eye candy. I actually appreciate that because I think game play is more important than graphics.

    Anyway, I don't think you can start sounding AMD's death knell yet. They're going to reach near performance parity with Intel in a few years just because they have more headroom for performance improvement than Intel as we approach the limit. At that point, x86 won't really be getting significantly faster year by year but it sure will get cheaper. I am sure we can all appreciate at least that aspect of it.
    Reply
  • inighthawki - Tuesday, June 18, 2013 - link

    x86 is far from hitting its performance limit. The reason Intel's CPUs haven't drastically improved performance in the last few generations is because their efforts have been focused elsewhere, most namely the integrated graphics chip, which has made significant strides even since Sandy Bridge, and consumes a large portion of the die. Haswell put most of their focus on Iris and power consumptions. Ivy bridge was already fast enough for 99.99% of the userbase, so it makes strong business sense to focus efforts elsewhere, and utilize their transistors on more important matters.

    If Intel wanted to increase CPU performance, they could. But they have no reason to bother doing so. Other features are more important and their competition (AMD) is still a generation or two behind in performance. There's not a whole lot of pressure for faster CPUs.
    Reply
  • 1008anan - Tuesday, June 18, 2013 - link

    inighthawki is right. In addition to what you said, Intel was focused on reducing the TDP envelope of CPU cores rather than increasing the single threaded performance of CPU cores. Since Intel uses the same architecture for everything from E7 Xeons to ultra-low power Haswell SoCs that power tablets (two 256 bit SIMDs wide with FMA), the single threaded performance of E7 Xeons is reduced to fit Haswell and Broadwell into tablets.

    However, this will not last. Intel now has three X86 architectures:
    --main Core architecture
    --Avoton and Avoton successors
    --Xeon Phi (including multisocketed E5 and E7 versions)

    Intel will be able to focus on increasing the number of bits wide for the main core from 512 to 1024 for future micro-architectures, as well as improving macro fusion, branch predictors, buffer sizes (better unified reservation stations, instruction decode queues, reorder buffers) increasing the number of parallel execution ports, L1, L2, L3, etc.

    The reason why is that the successors of Avoton will focus on low TDP parts over time, freeing Intel to prioritize increasing single threaded performance on the main core. Similarly Xeon Phi's focus on improving multi-threaded performance allows the main core to focus more on single threaded performance.

    In any case I would argue that single threaded performance has improved more since conroe than you imply. Anand Shimpi explains why better than I could here:
    http://www.anandtech.com/show/6355/intels-haswell-...
    Reply
  • bji - Tuesday, June 18, 2013 - link

    You refuted your own point at the end when you said "There's not a whole lot of pressure for faster CPUs". This is exactly why x86 is asymptotically approaching its IPC limit. There simply are not enough dollars chasing increased x86 performance to justify the huge costs involved in advancing x86 performance significantly. With mobile markets eating away at desktop and laptop market share, the number of tasks that require ever increasing CPU performance dwindling, and the increasing cost of increasing x86 performance, there just isn't going to be enough money chasing improved x86 performance to justify the billions that it costs to make significant headway. Reply
  • inighthawki - Tuesday, June 18, 2013 - link

    I apologize if I misinterpretted your original point, but I was speaking explicitly from a technological perspective. There are plenty of ways to improve performance, just very little will to do so. You are correct on that one.

    However I'm not sure I agree that the reason is solely just a need to justify R&D costs. I think it's more simply that the performance is high enough that they have the opportunity to better spend their time on more important things. Take away the costs they've put in since Sandy Bridge associated with improving the integrated graphics performance and lowering power consumption and I bet they could've easily ended up with a chip that was at LEAST 50% faster than it is now. It's just that nobody really wants or needs that.
    Reply
  • bji - Wednesday, June 19, 2013 - link

    I think we are in agreement. And I must say, things sure are different than they were 15 years ago when the gigahertz wars were heating up. Back then there was almost nothing you could do with a computer that couldn't benefit from more speed. Now ... well it's easy to go 4 or 5 years without bothering to upgrade, and the year-on-year speed bumps are almost not noticeable. Reply

Log in

Don't have an account? Sign up now