Slashdot Mirror


Intel On Track For 32 nm Manufacturing

yaksha writes "Intel said on Wednesday that it has completed the development phase of its next manufacturing process that will shrink chip circuits to 32 nanometers. The milestone means that Intel will be able to push faster, more efficient chips starting in the fourth quarter. In a statement, Intel said it will provide more technical details at the International Electron Devices Meeting next week in San Francisco. Bottom line: Shrinking to a 32 nanometer is one more step in its 'tick tock' strategy, which aims to create a new architecture with new manufacturing process every 12 months. Intel is obviously betting that its rapid-fire advancements will produce performance gains so jaw dropping that customers can't resist."

139 comments

  1. The new ones are impressive by FlyByPC · · Score: 1

    I'm just finishing a rebuild of my system, going from an Athlon64X2 to a Core i7. 3DMark06 is downloading now; can't wait to see how well it does on that and Flight Simulator X.

    ...Now if they could only make some progress on coordinating RAID implementations across motherboards, so a MB swap doesn't have to mean that the path-of-least-resistance is a complete reinstall...

    --
    Paleotechnologist and connoisseur of pretty shiny things.
    1. Re:The new ones are impressive by afidel · · Score: 3, Informative

      I can't wait for the multichip Xeon's based on Corei7, Intel might finally have a chip that can compete with AMD in the database space next year. Oh and for your raid problem, use HP, a RAID array is portal across all systems and controllers that use the same generation HDD's. I have picked up an array out of a server, put it into a MSA and mounted it through an HBA with no problems then expanded the array online with additional disks to grow capacity =)

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    2. Re:The new ones are impressive by Anonymous Coward · · Score: 2, Informative

      Two words: software raid. You have 4 cores, chances are you will usually be IO bound, so the performance will be better than HW raid.

    3. Re:The new ones are impressive by earnest+murderer · · Score: 0

      Now if only Windows supported RAID in software.

      --
      Platform advocacy is like choosing a favorite severely developmentally disabled child.
    4. Re:The new ones are impressive by Anonymous Coward · · Score: 1, Informative

      Assuming you're on Linux, buy a processor with more cores, and use softraid. Autodetect = painless movement.

    5. Re:The new ones are impressive by jaxtherat · · Score: 4, Informative

      It does, here is a RAID 5 example: http://support.microsoft.com/kb/323434

      --
      http://www.zombieapocalypse.tv/
    6. Re:The new ones are impressive by Anonymous Coward · · Score: 0

      Is this a joke? software RAID is available on Windows from when, NT4? Where have you been all these years?

    7. Re:The new ones are impressive by afidel · · Score: 1

      If only software raid had battery backed write cache it might be an option for real production systems....

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    8. Re:The new ones are impressive by Anonymous Coward · · Score: 0

      battery backed write cache ? sure. its called a UPS.

    9. Re:The new ones are impressive by PiSkyHi · · Score: 2

      Know of any recovery CD/DVD for a Windows RAID 5 system when it won't boot anymore ? It happened to me on a system I did not set up.

      Linux has recovery CDs to the hilt - many with RAID XX support, so you can recover data even when your system won't boot. Under Linux, you can't use RAID5 for a boot device anyway, so it will boot. I thought this was also true of Windows, but this machine had it.

      Note: Hardware RAID is dead, long live RAID!

      Never use a motherboards SATA for RAID, buy a cheap SiI 3132 or SiI 3124 card.

    10. Re:The new ones are impressive by PiSkyHi · · Score: 1

      Use a big fat journal, no need for a big fat wallet.

    11. Re:The new ones are impressive by KingMotley · · Score: 1

      You are mistaken, windows does not support RAID-5 on the boot partition or where the OS is either. If it truly did have RAID-5 and the boot or OS partition was on it, then it was via hardware.

    12. Re:The new ones are impressive by KingMotley · · Score: 1

      BTW, you can move your drives from one motherboard to the next so long as the raid is/was done via an intel raid controller. I've moved my complete OS from other motherboard to another with a different chipset with no problems, and that was on a 4-drive raid-0.

      It was from a ICH6R to ICH8R I believe. Of course if you went from an nvidia/amd chipset to an intel one, then you can't. Unless the raid was done via an add-in card, of course.

    13. Re:The new ones are impressive by PiSkyHi · · Score: 2, Informative

      ... if you could call motherboard RAID hardware, then yes.

      As far as I can tell, its the worst kind of RAID and it has given software RAID a bad name.

      The motherboard doesn't have parity chips, its just a flag to Windows to handle the RAID5.

      This one went bad and not only marked it as degraded, but windows would not boot and the only tool we could find to get access to the data was a DOS boot floppy with the RAID drivers installed - but then, it didn't have permission to read the files, and the USB tools for moving the data somewhere from a DOS boot disk caused the system to hang.

    14. Re:The new ones are impressive by skolima · · Score: 1

      You are using RAID0, and on four drives at once? Is you data really that disposable?

    15. Re:The new ones are impressive by Kane+Devaid · · Score: 1

      RAID Kills Installs Dead.

    16. Re:The new ones are impressive by Firethorn · · Score: 2, Insightful

      Yes, but unless they've changed stuff lately, he can't use RAID 5 on his boot disk - only mirroring is supported, and only sorta at that.

      Though with the way SSDs are going, I'd seriously consider putting the OS on a SSD, then going with the RAID array.

      And have things really changed so much that true hardware RAID is slower? I'm aware that there are RAID devices that depend on the CPU much like winmodems did, but surely a good RAID card still beats software?

      --
      I don't read AC A human right
    17. Re:The new ones are impressive by josath · · Score: 2, Informative

      I usually make a small partition, say 20-50GB, for the system files, and run that in RAID-1 (mirroring) across all 3 disks. I also store any super important documents on this volume, because it essentially has 3 copies. Then I combine the other 90% of the space in a RAID-5, which is much less wasteful than mirroring.

      --
      sig? uhh, umm, ok
    18. Re:The new ones are impressive by Firethorn · · Score: 1

      Not a bad idea, but SSDs have reached usable sizes for ~$100 for 32GB, enough for an OS and most program files - just install the games, user directories, and other multimedia stuff to the raid system.

      Heh, I wonder how large and cheap a SSD made with a 32 nm process would be.

      --
      I don't read AC A human right
  2. Not surprising. by pclminion · · Score: 3, Interesting

    At WinHEC 2008 the Intel speakers continued to hint at the fact that they had operating, packaged cores at this size. On track for manufacturing? More like they've been making it for 9-12 months already. At any rate, it's cool, though not surprising.

    1. Re:Not surprising. by Devil's+BSD · · Score: 4, Insightful

      I think they meant more that they're on track to scale it up for mass production at volumes that will hopefully meet the demand. I'm glad they're on target, I'm looking forward to Westmere (the 32nm Core i7 that will hopefully make it to mobile platforms by the end of next year).

      --
      I'm the Devil the Windows users warned you about.
  3. Nm by Anonymous Coward · · Score: 5, Funny

    Newton-metres? You mean Joules?

    What could possibly make you confuse N which is a symbol for Newton with n which is a prefix for nano.

    You're definitely not geeky enough.

    1. Re:Nm by Anonymous Coward · · Score: 5, Funny

      It's nautical miles. The chips are gigantic. Marvels of engineering.

    2. Re:Nm by McWilde · · Score: 1

      As a measure of torque, the Newton meter is more common than the Joule.

      --
      Maybe
    3. Re:Nm by n3tcat · · Score: 1

      So quantum computing would be giving your bytes to a group of people and sending them across the chips without a routing map. They may or may not arrive at the end point before starving to death!

  4. And yet. by mail2345 · · Score: 1

    At some point, it will stop getting smaller.

    1. Re:And yet. by Anonymous Coward · · Score: 4, Funny

      At some point, it will stop getting smaller.

      As opposed to the more common problem where it stops getting bigger.

    2. Re:And yet. by Panspechi · · Score: 1, Funny

      That's what she said!

    3. Re:And yet. by andersa · · Score: 0

      At some point, it will stop getting smaller.

      That's the point where you have achieved 'significant shrinkage'.

    4. Re:And yet. by FTWinston · · Score: 1

      Indeed. They probably won't be able to get more than a few generations smaller before quantum fluctuations become too signficant. By the time your transistor is on the scale of only a few dozen atoms, its going to stop being a transistor some of the time, and do its own damn thing.

  5. Chipsets by lobiusmoop · · Score: 5, Interesting

    It's great that Intel are working on die shrinks for their processors, but I wish they would do the same for their support chipsets. It's annoying that on most laptops the northbridge for Atom processors uses more power than the processor does.

    --
    "I bless every day that I continue to live, for every day is pure profit."
    1. Re:Chipsets by Anonymous Coward · · Score: 5, Interesting

      This should be partially alleviated once the i7 architecture is fully adopted. Pretty much no more north bridge. That's probably why they're neglecting the current chip set technology with more aggressive updates.

      And who knows, if a better chip interconnect comes around in the next generation (unlikely, but possible), Intel could start putting more and more in the CPU package. Things like a Larrabee GPU and south bridge functionality (audio, networking, general I/O). System on a chip is common place in embedded systems now. If Intel wants to eat ARM's lunch they're going to have to adopt some of the same techniques.

    2. Re:Chipsets by zonker · · Score: 3, Insightful

      Very true. The problem is that chipsets don't sell computers like processors do. Joe Shopper at WalMart doesn't know what a northbridge is but he has some understanding of what a Core 2 Duo is.

    3. Re:Chipsets by Anonymous Coward · · Score: 5, Insightful

      That's entirely a marketing issue.

      Joe shopper doesn't know what a core 2 duo is any more than he knows what a northbridge is. The only difference between the two is there are millions of dollars poured into making sure Joe recognized the term "core 2 duo". He still doesn't know a damn thing about it.

      Computers are funny from a marketing standpoint. They are purchased by people that don't know anything about them. Sold by people that don't know much about them and supported by people that don't even speak the same language. (often literally).

      Even more interesting, they are the only consumer device I know of where there is very little difference between first and third party parts. Obviously the technical specs change, but the average computer buyer wouldn't know the difference if you highlighted it in red.

      Selling computers therefore is a the most perfect example of marketing at work. Your customer doesn't know ANYTHING about the product in question, and so wants the one that he's heard the most about. So the customer buys what is best advertised.

    4. Re:Chipsets by Yarhj · · Score: 1

      Interestingly enough, the primary goal of die shrinks is not better performance, but lower cost. If a given die can be shrunk by a factor of k, we can fit roughly k^2 devices on a wafer of the same size. If the smaller chips work just as well as the larger chips we can then turn around and sell them for exactly the same price. It's like printing money(Step 3: PROFIT!). Of course, there's the expense in R&D and equipment to consider as well (Step 2: ????), but the basic reasoning is sound. If our competitors are stuck with a bigger chip, we win. The largest semiconductor companies are pushing for 450mm Silicon wafers for the same reason.

      Of course, smaller dimensions do enable certain performance enhancements (maximum device frequency comes to mind), but it takes a lot of work to get these smaller devices working.

    5. Re:Chipsets by TheRaven64 · · Score: 1

      The divide between north and south bridges has not really existed for a few years, but there are quite a few things that are in the supporting chipset and not in the CPU for Intel systems. Compare this with a real low-power chip, like the OMAP3530, which has USB, and disk / flash controllers, a GPU and a DSP on die, and RAM and flash stacked on the package, so you don't need much else to make a complete system with a power dissipation of 1.8W (and faster than the computer my mother uses).

      --
      I am TheRaven on Soylent News
    6. Re:Chipsets by Anonymous Coward · · Score: 0

      Blue tooth and 802.11 are radio things
      Here's why the property areas cant be smaller
      . Radio requires capacitors , inductors crystals anbd internal wire routing and lengths necessary for the radio frequency band used .
        Making them physically smaller or larger changes their characteristics and renders them useless for the task. . This is not the case with Chips which are semiconductors. So making radio stuff smaller can be impossible as Inductors and capacitors and wiring and Crystals may need to be external to the device or be of a specific size inside the chip.

    7. Re:Chipsets by mgblst · · Score: 1

      Computers are funny from a marketing standpoint. They are purchased by people that don't know anything about them. Sold by people that don't know much about them and supported by people that don't even speak the same language. (often literally).

      Do you really think that is different to most things out there? TVs, Fridges, Cars, Phones.

    8. Re:Chipsets by Haley's+Comet · · Score: 1

      Obviously the technical specs change, but the average computer buyer wouldn't know the difference if you highlighted it in red.

      That's because the 'red' is covered by the 'white-out'.

      --
      The Illuminati would kill me, but I'm not rich enough to take notice of.
  6. Point of Diminishing Returns? by Anonymous Coward · · Score: 3, Interesting

    Am I the only one feeling we might have reached the point of diminishing returns, at least for desktops, in the last 2-3 years. All the shrinkage past 90 nanometers just feels underwhelming. Stuff beyond Pentium 3 has not been revolutionary, performance wise, for a desktop.

    1. Re:Point of Diminishing Returns? by sunami · · Score: 3, Interesting

      Yea, there's a pretty big wall that's been hit in terms of clock speed, which is why multiple core processors is the direction instead of ramping up speeds.

    2. Re:Point of Diminishing Returns? by Anonymous Coward · · Score: 2, Funny

      Tee-he-he-he, you said "shrinkage". (nothing to see here)

    3. Re:Point of Diminishing Returns? by ColdWetDog · · Score: 1, Informative

      Am I the only one feeling we might have reached the point of diminishing returns, at least for desktops, in the last 2-3 years. All the shrinkage past 90 nanometers just feels underwhelming. Stuff beyond Pentium 3 has not been revolutionary, performance wise, for a desktop.

      I see we haven't been using Adobe software. Or Windows. Or Crysis. Or Slashdot's CSS 'implementation'.

      But if browsing Usenet with Lynx is where you're out, more power to you.

      --
      Faster! Faster! Faster would be better!
    4. Re:Point of Diminishing Returns? by Anonymous Coward · · Score: 0

      Negative ghostrider, shrinking the minimum feature size reduces the required die size. Reducing the die size means more die per wafer for approximately the same processing cost. End result is more for less. Unfortunately the required immersion lithography is crazy tough, very expensive, and very low throughput. Good luck Intel.

    5. Re:Point of Diminishing Returns? by NerveGas · · Score: 2, Interesting

      Anything past the P3 may not have been revolutionary, but it's steadily progressed quite nicely.

      I have a dual 1.4GHz P3 system, and a 1.6GHz Core Duo. The Core Duo is *much* faster, and that chip is already outdated. Not to mention the fact that it's comparing the fastest P3s made to the lowest of the Core Duo lineup.

      People also forget about things that can't be measured in nanometers or gigahertz, like the advances that have greatly lowered leakage current. Without them, something like 85% of the power used in the 32nM chips would be leakage, and liquid cooling would be an absolute necessity.

      Also, these advances allow Intel to make modest chips VERY cheaply... like the Atom. I've got a micro-atx board with one on it, and considering that the entire board+cpu only cost $65, it is an AMAZING performer.

      --
      Oh, you're not stuck, you're just unable to let go of the onion rings.
    6. Re:Point of Diminishing Returns? by KingMotley · · Score: 1

      Actually, I've felt that way ever since the 486. When the first 486's came out, they ran at 25MHz. You could keep your entire system for years, and then upgrade it to the 100MHz 486DX4. That's a 4 fold speed increase without needing to change motherboards. Today, we are lucky if we see a 20% speed increase (above the inital released speeds) before the next bump requires a different chipset and motherboard.

      We just aren't seeing the large speed bumps like we used to. Instead of going from say 25Mhz to 33 (a 32% increase), we see 2.66 to 2.93 (a 10% increase).

    7. Re:Point of Diminishing Returns? by Anonymous Coward · · Score: 0

      Stuff beyond Pentium 3 has not been revolutionary, performance wise, for a desktop.

      Dual Core + 5x speed increase per core compared to typical PIII speeds makes a hell of a difference when you're doing something like rendering a DVD iso (e.g. music video compilation - fairly basic requirement) AND want to play some music AND have your web browser responsive. And there's still enough CPU left to rip a CD. On my previous PIII equivalent I could only do one or two of these things at once (and it took about 8 hours to render a 30minute VCD as opposed to 1-2 hours to render a 3 hours DVD now).
      This sort of requirement isn't particularly nerdy or specialist these days. Lots of people do basic video processing.

    8. Re:Point of Diminishing Returns? by Corporate+Troll · · Score: 1

      Slashdot's CSS 'implementation'.

      I know it's offtopic, but I don't think it's their "CSS implementation", but rather their Web 2.0 implementation with all the JavaScript that comes with it.

      On my Asus EEE PC 701, I pretty much always get the warning that a script is running and offers to kill it. I always do. On my wifes 5 year old PC, which is plently fast for pretty much anything we do, slashdot freezes the browser about 2 seconds for a reload. Annoying, but not that problematic. The behaviour with the EEE PC pisses me off though

    9. Re:Point of Diminishing Returns? by Daengbo · · Score: 1

      Really, though, that 486 to 486DX4 conversion was the point where multipliers came into the scene, and suddenly 4X the processor speed didn't equate to 4X the system speed because suddenly all the other components weren't keeping up and became the bottleneck. Do you remember how disappointing that was?

    10. Re:Point of Diminishing Returns? by Spatial · · Score: 1

      "Speed" as in performance? No. A 3Ghz P4 is a shitload slower than a 3Ghz Athlon X2, which in turn is a shitload slower than a 3GHz Core 2 Duo. The per-core speed of Desktop CPUs has never stopped increasing.

    11. Re:Point of Diminishing Returns? by TheRaven64 · · Score: 1

      Intel have a test system where they can simulate new architectures. It lets them adjust every parameter, so they can simulate things that aren't even remotely feasible. A few years ago, they simulated an infinitely fast CPU in it, and ran some benchmarks. The total system speed was around 3-4 times faster than it was with the original design. For any given computer, doubling the CPU speed means that, unless you upgrade a lot more than the CPU, all you've done is moved the bottleneck somewhere else. This is why the 486 was the last system to do that, and why there wasn't a DX5.

      --
      I am TheRaven on Soylent News
    12. Re:Point of Diminishing Returns? by darkwhite · · Score: 1

      Stuff beyond Pentium 3 has not been revolutionary, performance wise, for a desktop.

      It has. You've been living under a rock.

      --

      [an error occurred while processing this directive]
    13. Re:Point of Diminishing Returns? by BZ · · Score: 1

      Really? A 3-year-old Core Duo (don't recall the clock speed, but in the 1.5-2 GHz range) is about 10x faster than a P3-733 on cpu-bound (small amount of memory accessed, no disk access) code. That's single-threaded code, so only using one core. 2-3x of that is the clock speed, the rest is the better architecture and process. 3-5x performance gain at the same clock speed is pretty good, in my book.

      You're right that whole-system performance has not kept pace with that, but it never does.

    14. Re:Point of Diminishing Returns? by mrwolf007 · · Score: 1

      On my Asus EEE PC 701, I pretty much always get the warning that a script is running and offers to kill it.

      Same here.
      On a Phenom X4 9850!

    15. Re:Point of Diminishing Returns? by mrwolf007 · · Score: 1

      Nope, that point came with the 486DX2, which doubled the internal clock. Oddly enough the DX4 only trippled the internal clock (better actually, but weird marketing). Still my 486DX-40 (overclocked to 50Mhz) was faster often enough than a DX4-100.

    16. Re:Point of Diminishing Returns? by Anonymous Coward · · Score: 0

      All the shrinkage past 90 nanometers just feels underwhelming. Stuff beyond Pentium 3 has not been revolutionary, performance wise, for a desktop.

      Peformance wise these changes may not be astonishing, especially for everyday use, but there are major gains in terms of manufacturing costs and portable design. These die shrinks are enabling the netbook/nettop markets and will continue to enable prices to fall.

    17. Re:Point of Diminishing Returns? by Daengbo · · Score: 1

      I guess I wasn't clear -- It was late for me here. I meant the move to the X2 and X4 in the 486 was the introduction of multipliers which meant that any increases in processing power after that didn't feel as large as those that came before.

    18. Re:Point of Diminishing Returns? by toddestan · · Score: 1

      Well, instead we're seeing bumps in the number of cores. We went from a single core processor to a dual core, a 100% bump, and now quad-core is becoming mainstream on mid to higher end desktop systems, which is another 100% bump over dual core. And there are sockets like LGA 775 and AM2 where it's possible to all the way from a single core to a quad core processor without having to change your motherboard.

    19. Re:Point of Diminishing Returns? by badkarmadayaccount · · Score: 1

      What browser are you using? IE6?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    20. Re:Point of Diminishing Returns? by mrwolf007 · · Score: 1

      FF2.0.0.18 under Mandriva

  7. Captain Metric to the rescue by Anonymous Coward · · Score: 3, Informative

    For this reason the SI standard dictates that metric units such as "km" or "nm" are never capitalized, even on a sign that is written ALL-CAPS.

    1. Re:Captain Metric to the rescue by Stormx2 · · Score: 1

      Of course. Because capitalisation changes the meaning in some cases, e.g. nm -> Nm

    2. Re:Captain Metric to the rescue by Anonymous Coward · · Score: 0

      What you mean to say is that capitalism is unacceptable with the French system of measurements...

    3. Re:Captain Metric to the rescue by LiLWiP · · Score: 0

      You know what they say... Capitalization is the difference between "I helped my uncle Jack off a horse." and "I helped my uncle jack off a horse."

    4. Re:Captain Metric to the rescue by Anonymous Coward · · Score: 0

      Exactly...Could you imagine if there were slow traffic bays for the the next 10 Kelvin-Megas?

      I not sure I can even fathom the choas!

  8. What about AMD? by blackyottabyte · · Score: 1

    If Intel is able to shrink its die size every 12 months AMD is in trouble. A more efficient design is usually beaten by a less efficient design fabricated in less space. That is if you think AMD's design is still more efficient.

    1. Re:What about AMD? by vsage3 · · Score: 5, Informative

      If Intel is able to shrink its die size every 12 months AMD is in trouble.

      For what it's worth "tick-tock" is actually alternating between a new architecture and a process shrink every 12 months. "Q4" in the summary means Q4 2009.

      Am I the only one feeling we might have reached the point of diminishing returns, at least for desktops, in the last 2-3 years. All the shrinkage past 90 nanometers just feels underwhelming. Stuff beyond Pentium 3 has not been revolutionary, performance wise, for a desktop.

      I hate to be snarky but you sound like one of those people who bought the crap about the "Megahertz Myth". Processor clock rate has little to do with performance. I'll agree that pentium 4 was underwhelming, but Core was a huge hit and saw huge performance, especially toward the ones that were released in early this year that used the high k dielectric.

    2. Re:What about AMD? by benthurston27 · · Score: 1

      The "megahertz myth" is that processor clock rate has a lot to do with performance, It seems to me like his post suggests that he didn't buy into it not being impressed with the pentium 4. But the shrinkage is definitely important, as in being able to fit more than one of a modified older design like the pentium III on one chip.

    3. Re:What about AMD? by afidel · · Score: 4, Interesting

      Actually I think the biggest post P3 improvement has been the move to dual core as standard on the desktop in the last couple years. At least on Windows the non-blocking nature with a stalled thread is huge for overall system performance and UI snapiness. It's great to be able to get those benefits without a $200 motherboard and two CPU's =)

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    4. Re:What about AMD? by Firethorn · · Score: 1

      Being that I have a tendency to run a few pieces of software that'll peg a CPU to 100% today, going to a dual core processor was a 'I LOVE THIS!!!' moment.

      I went with a dual core for the higher individual core speed and that games were, on the whole, still not optimized for using multiple cores, so the best you could get is the game on one core and everything else on the second, which STILL wouldn't be strained. Of course, prices come down, performance goes up, software advances, I'd consider a quad today.

      --
      I don't read AC A human right
    5. Re:What about AMD? by Anonymous Coward · · Score: 0

      and even if the performance has not grown so much, the price index has dropped - a lot.
      you could have a dual core, 2ghz laptop for less than 500$; do THAT at the PIII age.

  9. Re:42 32 nm.. by Anonymous Coward · · Score: 3, Funny

    Intel: I'm a chip company. I make chips, that's all I'm programmed to do.
    AC: Were you any good?
    Intel: Are you kidding? I was a star. I could make a chip to any size. 30 nm, 32 nm, you name it. 31... But I couldn't go on living once I found out what the chips were for.
    AC: What for?
    Intel: MacBooks.

  10. Obligatory Shrinkage Comment by blackyottabyte · · Score: 1

    This is one case where shrinkage is damn good.

    Don't take that out of context.

  11. Oh, boy. Here comes the nostalgia again. by jcr · · Score: 1

    In my day, getting to one micron feature sizes was a big deal. And we were grateful!

    You kids get off my lawn!

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  12. Normal people don't need faster computers by EmotionToilet · · Score: 3, Insightful

    Faster computers are going to be generally irrelevant to about 85% of the population. They only really use computers for surfing the internet, checking e-mail, MS Office, iTunes, organizing photos, and playing The Sims occasionally. Most people play video games on consoles (PS3, WII, Xbox 360). There are few things that 90% of the population regularly do that require a faster computer. These advancements are going to affect businesses and scientists who need super computers to perform large amounts of computations, or servers that need to respond to heavy demands. The only thing, I think, that needs to be improved is the hard drive. Right now they're just way too slow.

    1. Re:Normal people don't need faster computers by Anonymous Coward · · Score: 0

      640 kib should be enough to prove anyone wrong when they make stupid remarks like this.

      Sure, YOU may not need a "really really" fast computer. But you'll still buy something running a newer intel cpu the next time you need to update your sims gaming machine, because "why not? It runs better"

    2. Re:Normal people don't need faster computers by smilindog2000 · · Score: 3, Insightful

      Good point. With solid-state drives coming down the pipe, even that bottle-neck will be somewhat relieved for what most people do (lot's of disk reads, few writes). I write programs to help designers place and route chips. The problem size scales with Moore's Law, so we never have enough CPU power. I'm part of a shrinking population that remains focused on squeezing a bit more power out of their code. I wrote the DataDraw CASE tool to dramatically improve overall place-and-route performance, but few programmers care all that much now days. On routing-graph traversal benchmarks, it sped up C-code 7X while cutting memory required by 40%. But what's a factor of 7 now days?

      --
      Beer is proof that God loves us, and wants us to be happy.
    3. Re:Normal people don't need faster computers by Singularitarian2048 · · Score: 3, Funny

      Soon enough people will have robots in their homes, doing chores. Very fast computers will be needed for that.

    4. Re:Normal people don't need faster computers by NerveGas · · Score: 4, Insightful

      A surprising number of people that I know - and not just tech-savvy people - do video compression, either for converting camcorder movies into DVDs, creating slideshows, or using DVDshrink. And those are apps where more CPU is always good...

      Just wait until HD camcorders are more prevalent, and you have people that want to convert their home movies into X.264 Bluray discs...

      --
      Oh, you're not stuck, you're just unable to let go of the onion rings.
    5. Re:Normal people don't need faster computers by EmotionToilet · · Score: 1

      Actually I think even this statement is wrong. If I go to buy a new computer and I can buy a new model with a super fast processor for $1900, or a refurbished older model for $1300 that is slower, but more than fast enough for my needs, then I'll get the cheaper one and save myself $600. In fact, I did just that 4 months ago and completely love my iMac. :) A 2.4 ghz processor and 2GB ram is just fine with me. I don't need the 3.0 ghz one. It's not worth the extra $600. I use it mainly for internet and programming in Xcode and it does these things just fine. I may not need to upgrade my computer for another 5 to 7 years. If I do, it will only be so that I can get the Mac Pro with the 30" screen or for some new feature that Apple comes out with. :)

    6. Re:Normal people don't need faster computers by EmotionToilet · · Score: 3, Informative

      In my programming classes at UW-Milwaukee the professors emphasize that we should design our code to be easy to read/edit even if that means using up more computation cycles. This makes editing the code easier in the future, which is appreciated by future programmers who have to learn your code and can save the company some time and money. And since computation resources have become so cheap (practically unlimited for most applications) it doesn't really affect the performance of the program to a noticeable degree.

    7. Re:Normal people don't need faster computers by Anonymous Coward · · Score: 2, Funny

      If I go to buy a new computer and I can buy a new model with a super fast processor for $1900, or a refurbished older model for $1300 that is slower, but more than fast enough for my needs, then I'll get the cheaper one and save myself $600. In fact, I did just that 4 months ago and completely love my iMac.

      You got an Apple product cheaper? Amazing.

    8. Re:Normal people don't need faster computers by theheadlessrabbit · · Score: 2, Insightful

      was this professor involved with the design of vista at all?

      there is this thing called 'documentation' that you add to your code so other people can understand it.

      ignore your instructor. as a user, i very much appreciate whatever gains in efficiency i can get.

      --
      -I only code in BASIC.-
    9. Re:Normal people don't need faster computers by smilindog2000 · · Score: 2, Interesting

      The sad part is that improved runtime speed and code readability can be had together at the same time. The reason the DataDraw based code ran 7x faster was simple: cache performance. C, C++, D, and C# all specify the layout of objects in memory, making it impossible for the compiler to optimize cache hit rates. If we simply go to a slightly more readable higher level of coding, and let the compiler muck with the individual bits and bytes, huge performance gains can be had. The reason DataDraw saved 40% in memory was that it uses 32-bit integers to reference graph objects rather than 64-bit pointers. Again, C, C++, and most languages specify a common pointer size for all class types. If the compiler were allowed to take over that task, life would be easier for the programmer, and we'd save a ton of memory.

      But then again... what's a mere factor of 7X runtime with today's computers? With the low price of DRAM, who cares about 40%? It's easier to stick with the crud we've used since 1970 (C, and it's offspring) than to bother building more efficient languages. Language research has abandoned efficiency as a goal.

      --
      Beer is proof that God loves us, and wants us to be happy.
    10. Re:Normal people don't need faster computers by repvik · · Score: 2, Insightful

      Until the next version of Windows is out...

      Seriously though. Of course the top-of-the-line, state-of-the-art, bleeding-edge PC's are irrelevant for the general populace when they are released. That doesn't mean that they're irrelevant to the general populace in a year or two.
      When the next Windows is released, some new fancy games are released, websites are even more riddled with flash, java and whatever new tech they come up with to use more resources.

    11. Re:Normal people don't need faster computers by TheRaven64 · · Score: 3, Interesting

      General purpose CPUs are quite bad for video compression. A DSP or GPU is generally laid out in a way that maps more closely to the algorithms. I'd be interested to see what performance ffmpeg gets once they've finished optimising it for the DSP in the OMAP3530 (for reference, the entire BeagleBoard system built around one of these uses 1.8W - less than just the CPU of Intel's 'low power' systems and include the ARM Cortex A8 core, an OpenGL ES 2.0 GPU and a DSP).

      --
      I am TheRaven on Soylent News
    12. Re:Normal people don't need faster computers by jandrese · · Score: 1

      Huh? The cache only contains a set of what the processor already things it is likely to need. It's not like it's loading a fixed window of memory over the entire cache space. How C and other such languages organize their own memory space shouldn't matter much at all. Switching to 32 bit offsets instead of 64 bit pointers is fine so long as you never need to reference more than 4 billion records, but one application does not a whole industry make.

      --

      I read the internet for the articles.
    13. Re:Normal people don't need faster computers by Peter+La+Casse · · Score: 2, Insightful

      In my programming classes at UW-Milwaukee the professors emphasize that we should design our code to be easy to read/edit even if that means using up more computation cycles. This makes editing the code easier in the future, which is appreciated by future programmers who have to learn your code and can save the company some time and money.

      was this professor involved with the design of vista at all? there is this thing called 'documentation' that you add to your code so other people can understand it. ignore your instructor. as a user, i very much appreciate whatever gains in efficiency i can get.

      This is bad advice. Clear design and coding are extremely important in a nontrivial program. Once it's written, you can profile it to find out exactly where you need to improve performance. Documentation is necessary but not sufficient, and premature optimization makes programs less efficient not more.

    14. Re:Normal people don't need faster computers by smilindog2000 · · Score: 2, Interesting

      Check out the benchmark table at this informative link. On every cache miss, the CPU loads an entire cache line, typically 64 or more bytes. Cache miss rates are massively dependent on the probability that those extra bytes will soon be accessed. Since typical structures and objects are 64 bytes or more, the cache line typically gets filled with fields of just one object. Typical inner loops may access two of those object's fields, but rarely three, meaning that the cache is loaded with useless junk. By keeping data of like fields together in arrays, the cache line will be filled with the same field, but from different objects, often objects that will soon be accessed. This, plus the 32 vs 64 bit object references, and cache-sensitive memory organization (unlike malloc), leads to a 7X speedup in DataDraw backed graph traversals vs plain C code.

      Understanding cache performance is critical for fast code, yet most programmers are virtually clueless about it. Just run the benchmarks yourself if you want to see the impact.

      --
      Beer is proof that God loves us, and wants us to be happy.
    15. Re:Normal people don't need faster computers by Anonymous Coward · · Score: 0

      I was at a loss as to what refurbished computer could possible cost $1300, especially once I glanced 2.4 GHz. Then I saw that it was a Mac, and it all made sense.

    16. Re:Normal people don't need faster computers by ithmus · · Score: 1

      Faster computers are going to be generally irrelevant to about 85% of the population.

      85% of the population runs windows, and ordinary people will need faster computers to run Vista and Windows 7. These operating systems have a lot of services running in the background.

      Remember running DOS on a 486? That was snappy! Lets bring back the snap.

      --
      I'm supposed to be working right now.
    17. Re:Normal people don't need faster computers by blahplusplus · · Score: 2, Insightful

      Why don't you write an article about how to go about teaching them? I agree that "so many programmers are batshit stupid!" but what one doesn't understand is that most learning is unconscious, and the fact that you know it better then others means it's highly likely your interested in it for it's own sake. Many programmers don't know where to begin, I really wish everyone complaining about dumb programmers would write articles to teach them the tricks of the trade. If you don't they won't get passed on.

    18. Re:Normal people don't need faster computers by yoshi_mon · · Score: 1

      I'm fine with some code being very easy to read even at the expense of performance. But you seem to imply that doing so should always be the case. Which is a huge mistake.

      --

      Really, I know what I'm doing...Ohhhh, look at the shiny buttons!
    19. Re:Normal people don't need faster computers by frieko · · Score: 1

      http://en.wikipedia.org/wiki/Amdahl's_law

      GP is correct, it's highly counterproductive to put 1337 hax into every line of code you write. This is why you write clear, correct code and then run a profiler. Then 1337hax the few lines that eat the most cycles.

    20. Re:Normal people don't need faster computers by JWyner · · Score: 1

      And those video game consoles the "other 90%" use to play games process data with what? Tiny Gnomes?

      --
      "Owning a computer is like having your very own TV -- with a built in radio!" - Ed Helms
    21. Re:Normal people don't need faster computers by smilindog2000 · · Score: 1

      Not a bad idea, but where would I publish it? I could post it on my Dumb Idea of the Day blog, but no one reads it (which is ok with me). I would certainly be interested in writing an article about coding for cache performance.

      --
      Beer is proof that God loves us, and wants us to be happy.
    22. Re:Normal people don't need faster computers by BZ · · Score: 1

      While true, you do want to keep performance in mind when designing your _architecture_. If your program is algorithmically slow, or if it requires a virtual function call for any operation, then all profiling will show is time spent all over the map, because literally everything is slow.

    23. Re:Normal people don't need faster computers by blahplusplus · · Score: 1

      Check it out:

      http://accu.org/

      They also have a discussion list. I think it would be a good idea to see if anyones interested in a "wikibooks" project, i.e. people contribute small articles, and over-time the community edits it into something cohesive.

      http://en.wikibooks.org/wiki/WB:FB

      When dealing with teaching, one should teach from the ground up. I've seen way too many programming books that assume previous knowledge and most are really bad. I like the zero-to-hero mentality, where you take someone knowing nothing all the way through. But when you write an article that assumes previous knowledge, you outline for others where they should go, what they should read if they are just starting. Too much knowledge is too fragmented, most peoples knowledge is highly fragmented, they need to know all the necessary concepts in order to further understand and use someones understanding, each link in the chain should ideally be easily linked to and found. Since when most people need to start at the beginning and work their way up, and frequently go back and forth for areas they are weak in.

      I've been trying to find good 'self-teaching' resources for a while to take someone from absolutely zip understanding all the way through step-by-step, because much programming and programmers, unfortunately have started way too far up the abstraction chain and have little to zip understanding of what is going on.

      Andre lamothe has some interesting things going on here, as he too was frustrated by 'dumb developers'

      http://www.xgamestation.com/

    24. Re:Normal people don't need faster computers by NerveGas · · Score: 1

      Wake me up when software that normal folks has support for this.

      --
      Oh, you're not stuck, you're just unable to let go of the onion rings.
    25. Re:Normal people don't need faster computers by sjames · · Score: 1

      In most applications, maintainability is the more important factor. Even with that, there's a lot of room for improvement. Well thought out code can be efficient and maintainable. In some cases, just cleaning up older code to improve maintainability ends up making it more efficient as well.

      Too frequently code re-use is over-emphasized so you get a stack of objects that goes a bit like: (A) does something, (B) un-does about half of that and re-does it differently, (C) does a bit more and derives some information already available to A but not retained by B. Finally, (D) actually performs the operation using a subset of the parameters A passed to B throwing out most of the work done by B and C.

      Meanwhile, because of library reuse, actually understanding A's behavior requires understanding B and C even though they contribute nothing but unused computation, parameter munging, and additional opportunities to introduce an error.

      Not paying enough attention to keeping code tight means it will never run on the new cheap, small, reliable, and low power platforms becoming available. Instead, it needs big power hungry servers that sound like a turboprop and have a bazillion moving parts to break.

    26. Re:Normal people don't need faster computers by sjames · · Score: 1

      Another place where it gets interesting is when the objects are more than 64 bytes. In those cases, a simple re-ordering of the fields can double performance.

      Consider a common case of doubly linked structs. Prev and next pointers at the beginning followed by a bunch of other data. If your program needs to scan the list for cantidate objects for an operation, particularly where only a few of the structs will be operated on in a given pass, If the fields you check in the scan passes can be packed into the same cache line as the link pointers you can nearly double performance at no cost to readability.

    27. Re:Normal people don't need faster computers by smilindog2000 · · Score: 1

      Yep! If you talk to DSP guys, they do this kind of thing all the time. DataDraw allows me to specify which fields of a class I want kept together in memory, and by default, they're kept in arrays of individual properties. I was able to speed up random-access of large red-black trees in DataDraw 50% with this feature, simply because you almost always want both the left and right child pointers, not just one or the other.

      Nice to hear from a fellow geek who for whatever reason still keeps an eye on low-level performance.

      --
      Beer is proof that God loves us, and wants us to be happy.
  13. Intel by IDKmyBFFJill · · Score: 3, Funny

    It's all about splitting hair nowadays

  14. So long to the competition... by NerveGas · · Score: 4, Insightful

    Intel has always enjoyed a much better manufacturing technology than AMD. But, Intel made some stupid architectural decisions with the P4 architecture.

    Once Intel came out with the Core series, then the combination of a decent architecture and terrific fab capabilities really started eating away at AMD. This will only continue the rally.

    The sad thing is that this will actually be a step back in pricing... it's getting back to where AMD simply cannot touch the higher-end Intel territory, and so Intel is back to enjoying terrific profit margins on those chips.

    --
    Oh, you're not stuck, you're just unable to let go of the onion rings.
    1. Re:So long to the competition... by maxume · · Score: 1

      As long as Intel is willing to enjoy a lower profit margin on their middle of the road chips, who cares?

      I'm not a gamer, so my 2+ year old computer is fast enough about 98% of the time. I'm not willing to pay a great deal of money to bump that to 98.5%, or even 98.1%. I get that there are plenty of people who just need more speed, but that groups keeps getting smaller.

      --
      Nerd rage is the funniest rage.
  15. Smaller better? by Anonymous Coward · · Score: 0

    Could someone explain to me hoe smaller chips are better? Doesn't that decrease the surface area and make it even harder to dissipates heat from the chip?

    1. Re:Smaller better? by Kane+Devaid · · Score: 1

      The smaller the feature size, the faster the chip can be pushed. Alternatively, the chip can run at the same speed with less power. Die shrinks are the reason for the large speed increases all through the nineties. The problem is, the smaller you go the harder they are to make.

  16. Re:Oh, boy. Here comes the nostalgia again. by Anonymous Coward · · Score: 0

    What's a 'micron', USian?

  17. Re:Oh, boy. Here comes the nostalgia again. by jcr · · Score: 1

    What's a 'micron'

    It's a term used in semiconductor manufacturing to refer to one millionth of a meter.

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  18. So long to the competition...Race...relations. by Ostracus · · Score: 1

    I think AMDs strategy is overclocking and lots of it. Look at what it's introducing in it's latest and upcoming hardware. Features that make overclocking easier. Also I wouldn't count AMD out too soon. Amd is just one design correction away from having perfect hardware for HTPCs And their IGP is still better than Intels.

    --
    Shai Schticks:"You don't make peace with friends, you make peace with enemies"
  19. Amazing...Grace. by Ostracus · · Score: 1

    "Intel is obviously betting that its rapid-fire advancements will produce performance gains so jaw dropping that customers can't resist.""

    Two things. One it doesn't matter how awesome your hardware is. If the majority can't afford it then it doesn't matter? Second as Microsoft is learning prior success can be a barrier to future growth. How many are going to throw out their Core 2 Duos in order to have the most amazing hardware from Intel?

    --
    Shai Schticks:"You don't make peace with friends, you make peace with enemies"
  20. So can someone summarize the current state? by DG · · Score: 1

    I found out from my wife that our home server died and won't reboot. AMD Athlon 3200+ running Fedora.

    It is almost certainly a hardware problem, and that server has been running 24/7 for years now... time to upgrade.

    My hardware philosophy has been to buy big and milk it for a long time. You pay more up front for that power, but the fact that it has power means it doesn't get obsoleted immediately either.

    So then, cut through the marketing crap. Assume a desktop PC purchase in the May-ish time frame, to run Linux. What is likely to be the way to go from a hardware perspective?

    DG

    --
    Want to learn about race cars? Read my Book
    1. Re:So can someone summarize the current state? by Anonymous Coward · · Score: 0

      If you wanted something now, I'd say grab a Q6600. Undervolt and/or underclock it if you don't need so much power, but the quad-core and 8MB L2 gives some potential for next several years.

    2. Re:So can someone summarize the current state? by TheRaven64 · · Score: 1

      If it's left on all of the time, you might want to consider low power, rather than high speed. A 45W chip will use 395 kilowatt hours per year, which will cost me around around £60 (around $90, now the pound's collapsed against the dollar, around $120 two months ago) per year to run. Something like the BeagleBoard consumes only 1.8W. For a home server, you'd want something in the middle (actually, I'd like a BeagleBoard with 4 SATA connectors, but, sadly, it doesn't exist). Depending on how much you're taxing it, I'd be inclined to recommend the AMD Geode line - they're an order of magnitude more power-thirsty than ARM or MIPS offerings, but they're x86 and well-supported by commodity software.

      --
      I am TheRaven on Soylent News
    3. Re:So can someone summarize the current state? by jps25 · · Score: 1

      If it's running 24/7 and your old Athlon 3200+ was good enough, then pick any current dual or quad desktop CPU with the lowest energy usage.
      Pick a motherboard with an IGP and plenty of SATA2.
      Throw in 8 or 16GB RAM and a couple of hdds.
      Most importantly, check silentpcreview.com so you know which case to buy and how to silence it.

    4. Re:So can someone summarize the current state? by sssssss27 · · Score: 1

      I just rebuilt my server using an Intel Atom dual core and a 4 port SATA PCI card from my old server. I'm running Linux with three 750 GB HDDs in RAID-5. Have an 80$+ PSU and a case with a 240mm top fan so it's pretty quiet as well. I just rip all my media to it so I can access it from anywhere in my house or through the Internet. It's worked well for me.

    5. Re:So can someone summarize the current state? by b0bby · · Score: 1

      Newegg has an MSI Wind Atom based barebones box for $139 that looks perfect to me for a home server. I'm with the others here - go low power rather than high power.

  21. nm, not Nm by the_other_chewey · · Score: 1

    Stupidly uppercasing everything in a headline will regularly backfire if scientific units are used.

    What's meant here is nanometer, not Newtonmeter - which, by the way, is equal to Joule.

    And now here I am, unable to think of a good pun about a 32 Joule chip...

  22. Intel chip by Andypcguy · · Score: 1

    What about not only putting the more cores on die bit also RAM and the chipset. As said the motherboard would be different from anything we've seen so far. Would this result in any meaninful gains compaired to the cost and limites on options?

  23. Re:Oh, boy. Here comes the nostalgia again. by TheRaven64 · · Score: 1

    I have an issue of Byte up in my attic where the process shrink to 1 micron is the cover story. I read it a couple of years ago, around the time of the 65nm process shrink. It really gives you a sense of the speed at which process technology is improving.

    --
    I am TheRaven on Soylent News
  24. sometimes, yes, sometimes no by HelloKitty · · Score: 1

    premature optimization is sometimes as you say, bad. however there is an idea of mature optimization where you know something needs to be written in such a way as to be fast.

    say your task has to run in realtime, and it involves iterating over most of the machine's memory. if it doesn't run fast, you have a real problem.

    always choose the correct read/write patterns, the correct architecture, and then make that code as clear as possible...

  25. Jaw Dropping? by frenchgates · · Score: 1

    Can anyone remember the last time an incremental advance in chip speed was anything close to "jaw dropping?" Having been in this industry a while I can't count the number of times people like Steve Jobs and Andy Grove claimed speed increases of more than double with almost no apparent effect on anything but benchmarks. The early days of 3D accelerators was about the only time I really went "wow!"

    --
    Syntax error: loose != lose, affect != effect, then!=than
  26. It's a question of manufacturing capacity by brucmack · · Score: 1

    Really, this is just a matter of having limited manufacturing capacity. Every time they create a new manufacturing process, they have to upgrade a factory to use it. This puts the factory out of service for however long it takes to roll out the new tech, and costs billions of dollars in the process. In other words, even Intel doesn't have the resources to upgrade all of their factories at once.

    Instead, they take one or two factories running the oldest tech, and upgrade them. Once they are ready, they start manufacturing the high-end processors. The last-generation tech manufactures lower-end processors. The generation before that manufactures chipsets, graphics chips, etc. The generation before that manufactures DRAM / flash / whatever else is needed. This is just an example, I have no idea what the split is in reality.

    So from Intel's perspective, they are always using the newest manufacturing tech for their most important products (high performance, high profit margin). This in turn gives them the capital needed to develop their next manufacturing process, and the cycle continues...

    1. Re:It's a question of manufacturing capacity by tlhIngan · · Score: 1

      Instead, they take one or two factories running the oldest tech, and upgrade them. Once they are ready, they start manufacturing the high-end processors. The last-generation tech manufactures lower-end processors. The generation before that manufactures chipsets, graphics chips, etc. The generation before that manufactures DRAM / flash / whatever else is needed. This is just an example, I have no idea what the split is in reality.

      Actually, memory devices often use the most cutting-edge technology available, and can often be a half-generation or more ahead of what's used for a CPU. The reasoning is simple - memory devices have very high transistor density and they capitalize on the fact that memory devices have a very regular layout. In fact, when going up a technology level, a memory device is created because you want to pack in the transistors, and its trivial to test them in all sorts of conditions. (Think of it this way - you can get flash memory in 32GB sizes. Assuming MLC flash, that's 16 billion transistors, plus the support logic). CPUs and other ICs don't have such a high transistor density due to their "random logic" arrangement. The vast majority of transistors used on a CPU actually go towards the cache - and are so dense they take up only half the die space.

      Memory devices are silicon-limited - their storage capacity is limited by the silicon area you can use. CPUs are pin-limited - their functionality is limited by the number of pins their package has (and some pins have mutliple functions, as on many System-On-Chip). A die shrink that doubles the number of transistors means you get a doubling of storage capacity - and people want more RAM and more flash.

    2. Re:It's a question of manufacturing capacity by brucmack · · Score: 1

      You're correct, I forgot about Intel being a big player in the SSD market. A quick search shows that their flash memory fabs run on different node sizes though (50 nm, 34 nm coming) so I guess those fabs are outside of their processor rotation.

  27. Every 24 months, not 12 by brucmack · · Score: 2, Informative

    Just to clarify: the tick-tock strategy means that one year gets a new architecture, the next year gets a new manufacturing process, and the cycle repeats. This means that there is a new architecture and new manufacturing every 24 months, not 12, and in alternating years.

  28. I think you are probably right by Sycraft-fu · · Score: 1

    The whole separate northbridge thing is kind of a legacy idea. AMD ditched it some time ago, now Intel is ditching it. Well, that being the case, little point in pushing forward with advances on it, only to then deprecate it immediately after. It'll probably be till the next "tick" before it is totally gone, but it should happen soon.

    The other problem people have to remember is that they have a limited amount of the highest tech fabs. It isn't as though you flip a switch and the fab suddenly is on a smaller process, it takes a massive retooling effort, months of work. So if you have a limited amount you can crank out of this new tech, you do it where it matters most: The processor. That is your real bread and butter in terms of money. You have the other, lesser fabs do your other stuff.

    So as for the Northbridge, this should be solved soon. I can't imagine they will make any 32nm processors for desktop or laptop that aren't based on the Core i7 architecture. As for die shrinks in general, I think you can always expect other chips (northbridge/southbridge network, flash, etc) to be on a process that's at least one generation out of date of their current one.

  29. winning via nm process, not design optimizations by Locutus · · Score: 1

    I was looking at the range of low power CPUs and noticed that Intel's Atom seemed to do ok compared to the other low powered chips but then noticed that all the other chips were being built on a 65nm process while Intel had the Atom on the 45nm process. Looking at Intels standard "Core" processors showed that their newest CPUs were also on the 45nm process but not the majority of them.

    This was a few months ago but it made me wonder why all the other low power CPU manufacturers were able to get the power and performance from 65nm while Intel had to jump to the newest and smallest process(45nm) for the Atom to get in the ballpark on power and performance. And they had to be eating into production space for the high profit high performance larger CPUs they'd just released on the 45nm process.

    They seem to have a strategy of winning by using their ability to shrink the process instead of optimizing the designs. It's a much much more costly exercise and if anyone else with massive amounts of process experience steps in to manufacturer for those with better chip designers, they'll not be gaining much more than a few months. And this push to low power and high performance is also bringing ARM into play with their Cortex A8 and multi-core Cortex A9 processor. It's amazing what a Cortex A8 can do on 3W.

    LoB

    --
    "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  30. Re:Oh, boy. Here comes the nostalgia again. by DragonWriter · · Score: 1

    What's a 'micron', USian?

    Its a common term for what would, in normal SI parlance, be a "micrometer", because "micron" predates the adoption of the SI system, and "micrometer", in English at least, has a well established meaning referring to a particular kind of measuring device.

  31. Quibble: "OR", not "WITH"... by Anonymous Coward · · Score: 0

    Emphasis mine:

    ... one more step in its 'tick tock' strategy, which aims to create a new architecture with new manufacturing process every 12 months.

    No, Intel aims to create a new architecture *OR* a new manufacturing process every 12 months. NetBurst to Core 2 in 2006, 65 nm to 45 nm in 2007, Core 2 to Core i7 in 2008, 45 nm to 32 nm in 2009.

    Alternating between architecture and process.

  32. Too true.. by crovira · · Score: 1

    I first learned the importance of getting things right. (A payroll program that gets the wrong answers gets the doors torn off the front of cookie factory. [That was my predecessor's mistake. :-])

    Then I learned the importance of getting them to run fast. (I had a twelve hour window for calculation that suddenly got chopped in six as the company spread over a wider geographic area. The company bought their competitor. Now I had more impatient people to deal with [See previous 'font door' problem.])

    Squeaked by and the machine eventually got upgraded with a mainframe.

    I eventually learned to write Smalltalk (interpreted once, cached compiled code) that could outperform any C or C++ code by exploiting the structure of the problem. (I had people generating huge reports multiple times because they couldn't get it through their thick skulls that the program was not malfunctioning, it has actually finished.)

    First, do it right.

    Then do it fast.

    Lastly do it small. (RAM is simultaneously the most expensive part of a system and if you know how to program, since time is money, the cheapest.)

    --
    MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
  33. Its a question of how you beak up code/processing. by crovira · · Score: 1

    O-O code can be optimized by knowing how (and therefore where) to cut up your code.

    The code itself doesn't need to be any different, but how and where you cut it up can make an enormous difference in performance.

    If you can take advantage of RAM to cache intermediate results of seek (find/get) operation, you can get incredible speed out of otherwise 'dead code'.

    --
    MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
  34. re: eggs in a basket? by Rage+Maxis · · Score: 1

    or make a jaw-dropping investment with such potential for failure it will bring us back to the electronic stone age.

    what does Intel have that Ford didn't before?

    --
    --- ask me about nihilism, I will have nothing to tell you.
  35. Re:42 32 nm.. by badkarmadayaccount · · Score: 1

    I want that in a Terry Pratchet book!

    --
    I know tobacco is bad for you, so I smoke weed with crack.