Log in

View Full Version : CrunchGear Dishes on Intel's 45nm Penryn Processors


Jason Dunn
02-27-2008, 12:00 AM
<div class='os_post_top_link'><a href='http://www.crunchgear.com/2008/02/26/march-of-the-penryns/#more-22012' target='_blank'>http://www.crunchgear.com/2008/02/2...yns/#more-22012</a><br /><br /></div><em>&quot;Everybody&rsquo;s excited about Intel&rsquo;s new 45nm chip architecture and its first iteration, the Penryns. They&rsquo;re going to be in the MacBooks, they&rsquo;re going to be in your desktops, they&rsquo;re basically taking the joint over and everyone&rsquo;s pumped. You&rsquo;re probably wondering why. Isn&rsquo;t it just another bump in processor speed? No, it&rsquo;s a bit better than that - read on and find out why 45nm is a major step for Intel. First, it&rsquo;s important to understand what 45nm means. This new process is essentially a further miniaturization of transistor technology, which all computer chips are based on. 65nm has been the standard for a couple years now, and Intel&rsquo;s chips have been, in their multitudes, based on the same base-level recipe - or rather, on the same cake mold. The various versions - mobile, desktop, server, multi-core, all have the same underlying transistor technology, but customized for different tasks. In any case, 45nm is the new basic building block they&rsquo;ll be working with.&quot;<br /><br /></em><img src="http://images.thoughtsmedia.com//dht/auto/1204065025.usr1.png" alt="" /><br /><br />CrunchGear's Devin Coldewey gives us a layman's breakdown of what's coming with Intel's Penryn CPUs. Die-shrinks, meaning going from 65nm down to 45nm, is a very big deal - it's the &quot;tock&quot; in Intel's &quot;tick tock&quot; strategy; the major stroke. What we're going to see is higher clock speeds, lower power usage, more and faster L2 cache (which translates to enhanced performance), and new SSE instruction sets that will enhance multimedia encoding and playback. What surprises me the most? We're still not seeing a CPU with a dedicated h.264 encoding core (true hardware acceleration) - maybe there are a dozen technical reasons why that can't happen, but if not, it would sure be nice to see.