Slashdot Mirror


Intel Launches Power-Efficient Penryn Processors

Bergkamp10 writes "Over the weekend Intel launched its long-awaited new 'Penryn' line of power-efficient microprocessors, designed to deliver better graphics and application performance as well as virtualization capabilities. The processors are the first to use high-k metal-gate transistors, which makes them faster and less leaky compared with earlier processors that have silicon gates. The processor is lead free and by next year Intel is planning to produce chips that are halogen free, making them more environmentally friendly. Penryn processors jump to higher clock rates and feature cache and design improvements that boost the processors' performance compared with earlier 65-nm processors, which should attract the interest of business workstation users and gamers looking for improved system and media performance."

18 of 172 comments (clear)

  1. revolutionary? no, but still noteworthy by Anonymous Coward · · Score: 3, Informative

    While Penryn is a small increase in performance, it is not a big change in the architecture. Instead of upgrading to Penryn, customers can expect Nehalem, the next major revision in the Intel architecture, was responsible for the release in 2008.

    At the Intel Developer Forum in San Francisco in September Intel showed, and said it would be a better yield per watt and better system performance through its Quick Path Interconnect system architecture. Nehalem chips will also provide a memory controller integrated and improved communication between system components.

    1. Re:revolutionary? no, but still noteworthy by Azuma+Hazuki · · Score: 5, Insightful

      I am a dedicated AMD fangirl...every computer I've ever built had an AMD chip in it. But Intel really hit it on the head with the Core 2 arch and I see no sign of them slackening. I am actually looking forward to Nehalem and its shrink (which is probably the next time I'll have the money to spend on anything not college or food/supply-related).

      If this is how it ends for AMD, this is how it goes. I'll be sad, and may buy AMD anyway for some other reason (even if it's just stubborn fangirlism) but I respect Intel's design team. Their ethics, no, but their design is top notch this time around.

      --
      ~Eien no Inori wo Sasagete~ Searching for my Hatsumi...
    2. Re:revolutionary? no, but still noteworthy by AvitarX · · Score: 4, Insightful

      One reason to buy AMD is that if they go out of business Intel may stop innovating.

      Even if you are getting a worse deal in the short run, an upgrade cycle or two in the future may be much worse (comparatively) if everyone goes Intel.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    3. Re:revolutionary? no, but still noteworthy by Pojut · · Score: 4, Informative

      Another good reason is that it is far cheaper (at least last time I checked prices) to go with AMD...especially if you aren't doing any gaming or audio/video work. While Core 2 blasts AMD out of the water, the price difference makes AMD a very smart buy for every-day use. For gaming, AMD's offerings still work great, and the money you save on the processor can instead be used towards a more powerful video card.

    4. Re:revolutionary? no, but still noteworthy by dreamchaser · · Score: 3, Interesting

      You should probably check the prices again with an eye towards price/performance ratios. AMD hasn't been cheaper for a long time. You can save a few bucks by settling for lower performance, but not enough to upgrade that video card or any other significant components.

    5. Re:revolutionary? no, but still noteworthy by necro81 · · Score: 3, Informative

      The biggest thing about Penryn is the move to 45-nm fabrication, and the technological advances that were required to pull it off. IEEE Spectrum has a nice, in-depth (but accessible) article on those advances. High-k dielectrics and new metal gate configurations will be how advanced ICs are produced from now on. It is as large a shift for the fabs as a new chip architecture is for designers.

    6. Re:revolutionary? no, but still noteworthy by ircmaxell · · Score: 5, Informative

      Ummmm.... Check this out... http://www23.tomshardware.com/cpu_2007.html

      This chart shows that in terms of Price/Performance for the average user, Intel has only two CPU's that can compete with AMD's leading X2 (non-FX) processor (the 6000+, which is the highest AMD they have benchmarked). The first is the E2160, and the second is the P4E 613.

      The field is LARGELY domainated (at the best scores that is) by AMD... Intel has 5 in the top 20, 1 in the top 10, and 0 in the top 5. AMD, conversely, has 2 x2's in the top 5...

      --
      If a man isn't willing to take some risk for his opinions, either his opinions are no good or he's no good
  2. Re:Still sticking by Waffle+Iron · · Score: 4, Informative

    It should've been replaced a long time ago with a pure RISC instruction set

    It was, when the Pentium Pro was introduced circa 1997. The instruction set the programmer "sees" is not the instruction set that the chip actually runs.

  3. x86 already has elements of RISC & PowerPC is by Blahbooboo3 · · Score: 4, Insightful

    I believe that x86 already has many of the benefits of RISC chips incorporated into them. Way back in 1995 http://en.wikipedia.org/wiki/X86#Chronology.Intel added to the Pentium Pro a RISC core. From the Wiki article, "During execution, current x86 processors employ a few extra decoding steps to split most instructions into smaller pieces, micro-ops, which are readily executed by a micro-architecture that could be (simplistically) described as a RISC-machine without the usual load/store limitations."

    As for PowerPC Macs, I doubt it. The switch to Intel is what made most new Mac users switch because there was no longer a risk of not being able to run the one Windoze program they might need. If Mac ever went to a non-mainstream CPU again it would be a big big mistake.

  4. Re:Can somebody explain by compumike · · Score: 5, Informative

    The energy required to switch a capacitor from zero to Vdd volts is 1/2*C*Vdd^2.

    Smaller logic sizes can operate faster because the physical gate area of the transistor is that much smaller, so there's less capacitance loading down the piece of logic before it (proportional to the square of the scaling, of course). However, it also tends to be the case that the operating voltages scale down too (because they adjust the semiconductor doping and the gate oxide thickness to match), so you get an even better effect on energy required. Thus, scaling helps both with speed and operating power.

    The problem they're running into now is that at these smaller sizes, the off-state leakage currents are getting to be of the same magnitude as the actual switching (operating logic) currents! This happens because of the reduced threshold voltage when they scale down, so the transistor isn't as "off" as it used to be.

    That's why Intel has to work extra hard to get the power consumption down as the sizes scale down.

    --
    NerdKits: electronics kits for the digital generation.

  5. Re:Can somebody explain by Rhys · · Score: 5, Informative

    Smaller size means signals can propagate around the chip faster. It also means you need less signal-fixing/synchronization hardware, since it is simpler to get a signal synced up at a given clock rate. Smaller size generally means less power dissipated. Smaller feature sizes means the CPU is physically smaller (generally), so more CPUs fit on a silicon wafer. For each wafer they produce (a high but relatively fixed cost vs the number of CPUs on the wafer) they get more CPUs out (= cheaper). If a CPU is bad, that is a smaller percent of the wafer that was "wasted" on that CPU.

    --
    Slashdot Patriotism: We Support our Dupes!
  6. Re:Still sticking by jonesy16 · · Score: 5, Informative

    Actually, one of the reasons that Apple jumped off of the PowerPC platform was BECAUSE of their power inefficiency. The G5 processors were incredibly power hungry, enough so that they could never get one cool enough to run in a laptop and actually offered the Mac Pro line with liquid cooling. Compare that to the new quad-core and eight-core mac pro's and dual core laptops that run very effectively with very minimal air cooling.

  7. RISC vs. CISC by vlad_petric · · Score: 4, Informative
    That's a debate that happened more than 20 years ago, at a time when all processors were in-order and could barely fit their L1 on chip, and there were a lot of platforms.

    These days:

    • The transistors budgets are so high that the space taken by instruction decoders aren't an issue anymore (L1, L2 and sometimes even an L3 is on chip).
    • Execution is out-of-order, and the pipeline stalls are greatly reduced. The out-of-order execution engine runs a RISC-like instruction set to begin with (micro-ops or r-ops).
    • There is one dominant platform (Wintel) and software costs dominate (compatibility is essential).

    One of the real problems with x86-32 was the low number of registers, which resulted in many stack spills. x86-64 added 8 more general purpose registers, and the situation is much better (that's why most people see a 10-20% speedup when migrating to x86-64 - more registers). Sure, it'd be better if we had 32 registers ... but again, with 16 registers life is decent.

    --

    The Raven

    1. Re:RISC vs. CISC by TheRaven64 · · Score: 3, Interesting

      The transistors budgets are so high that the space taken by instruction decoders aren't an issue anymore (L1, L2 and sometimes even an L3 is on chip). Transistor space, no. Debugging time? Hell yes. Whenever I talk to people who design x86 chips their main complaint is that the complex side effects that an x86 chip must implement (or people complain that their legacy code breaks) make debugging a nightmare.

      Execution is out-of-order, and the pipeline stalls are greatly reduced. The out-of-order execution engine runs a RISC-like instruction set to begin with (micro-ops or r-ops). Most non-x86 architectures are moving back to in-order execution. Compilers are good enough that they put instructions far enough away to avoid dependencies (something much easier to do when you have lots of registers) and the die space savings from using an in-order core allows them to put more cores on each chip.

      There is one dominant platform (Wintel) and software costs dominate (compatibility is essential). Emulation has come a long way in the last few years. With dynamic recompilation you can get code running very fast (see Rosetta, the emulator Apple licensed from a startup in Manchester). More importantly, a lot of CPU-limited software is now open source and can be recompiled for a new architecture.

      x86-64 added 8 more general purpose registers, and the situation is much better (that's why most people see a 10-20% speedup when migrating to x86-64 - more registers) Unfortunately, you can only use 16 GPRs (and, finally, they are more or less real GPRs) when you are in 64-bit mode. That means every pointer has to be 64-bit, which causes a performance hit. Most 64-bit workstation spend a lot of their time in 32-bit mode, because the lower memory (capacity and bandwidth) usage and cache churn give a performance boost. They only run programs that need more than 4GB of address space in 64-bit mode. Embedded chips like ARM often do the same thing with 32/16-bit modes. If x86-64 let you have the extra registers with the smaller pointers you would probably see another performance gain.
      --
      I am TheRaven on Soylent News
    2. Re:RISC vs. CISC by vlad_petric · · Score: 4, Interesting
      High-performance computing isn't moving away from out-of-order execution any time soon. Itanic was a failure. The current generation of consoles are in-order, indeed, but keep in mind that they serve a workload niche (rather large niche in terms of deployment, sure, but still a workload niche).

      The argument that the compiler can do a reasonable job at scheduling instructions ... well, is simply false. Reason #1: The problem is that most applications have rather small basic blocks (spec 2000 integer, for instance, has basic blocks in the 6-10 instruction range). You can do slightly better with hyperblocks, but for that you need rather heavy profiling to figure out which paths are frequently taken. Reason #2: compiler operates on static instructions, the dynamic scheduler - on the dynamic stream. The compiler can't differentiate between instances of the instructions that hit in the cache (with a latency of 3-4 cycles) and those that miss all the way to memory (200+ cycles). The dynamic scheduler can. Why do you think that Itanium has such large caches? Because it doesn't have out-of-order execution, it is slowed down by cache misses to a much larger extent than the out-of-order processors.

      I agree that there are always ways to statically improve the code to behave better on in-order machines (hoist loads and make them speculative, add prefetches, etc), but for the vast majority of applications none are as robust as out-of-order execution.

      --

      The Raven

  8. CISC to RISC runtime translation by Z-MaxX · · Score: 3, Interesting

    An often overlooked benefit of the way that modern IA32 processors achieve high performance through translating the CISC x86 instructions into microcode instructions is that the chip designers are free to change the internal microcode architecture for every CPU in order to implement new optimizations or to tune the microcode language for the particular chip's strengths. If we were all coding (or if our compilers were coding for us) in this RISCy microcode, then we, or the compiler, would have to do the optimizations that the CPU can do in its translation to microcode. I agree that the Power architecture is pretty cool, but I'm tired of hearing people bash the Intel x86 architecture for its "obsolete" nature. As long as it is the fastest and best thing I can buy for a reasonable amount of money, it's my top choice.

    --
    Dr Superlove 300ml. I use my powers for awesome
  9. Re:Can somebody explain by enc0der · · Score: 4, Interesting

    Smaller size means faster but at the expense of more power. As a chip designer I can tell you that the smaller you go, the more leakage you have to deal with in the gates, and it goes up FAST. Now, with the new Intel chips, they are employing some new techniques to limit the leakiness of the gates, these techniques are not standard across the industry so it will be interesting to see how they hold up. I do not understand what you mean by signal-fixing/synchronization hardware. Design specific signal synchronization doesn't change over the different gate sizes. What changes is the techniques that are used as people find better ways to do these things. However, these are not technology specific and tend to find their way back into older technologies to improve performance their as well. In addition, cost is NOT always cheaper because die yield is generally MUCH LESS at newer technologies. For those on the bleeding edge. In addition, development costs go up because design specific limitations, process variance, and physical limitations cause designs to be MUCH HARDER to physically implement than at larger sizes. Things like electromigration, leakage power, ESD, OPC, DRC, and foundry design rules are MUCH worse. What is true is that these people want faster chips, and you can get that, as I said. Although the speed differences are not that amazing. Personally, I don't think the cost justifies the improvement in what I have worked on. Especially on power. Now, going out a few years from now, as they solve these problems at these specific gate geometries, THEN we will start to see the benefits of the size overall.

  10. Names of Rivers? by spineboy · · Score: 3, Interesting

    I'm just wondering which will end first - Moores law, or the number of river names left in Washington. For those of you who don't know, all of Intels chip names are named after rivers in Washington state.

    --
    ..........FULL STOP.