Slashdot Mirror


How Much Smaller Can Chips Go?

nk497 writes "To see one of the 32nm transistors on an Intel chip, you would need to enlarge the processor to beyond the size of a house. Such extreme scales have led some to wonder how much smaller Intel can take things and how long Moore's law will hold out. While Intel has overcome issues such as leaky gates, it faces new challenges. For the 22nm process, Intel faces the problem of 'dark silicon,' where the chip doesn't have enough power available to take advantage of all those transistors. Using the power budget of a 45nm chip, if the processor remains the same size only a quarter of the silicon is exploitable at 22nm, and only a tenth is usable at 11nm. There's also the issue of manufacturing. Today's chips are printed using deep ultraviolet lithography, but it's almost reached the point where it's physically impossible to print lines any thinner. Diffraction means the lines become blurred and fuzzy as the manufacturing processes become smaller, potentially causing transistors to fail. By the time 16nm chips arrive, manufacturers will have to move to extreme ultraviolet lithography — which Intel has spent 13 years and hundreds of millions trying to develop, without success."

362 comments

  1. Don't make them smaller by AhabTheArab · · Score: 5, Funny

    Make them bigger. More space to put stuff on them then anyway. Tostito's Restaurant style tortilla chips can fit much more guacamole and salsa on them than their bite size chips. Bigger is better when it comes to chips.

    1. Re:Don't make them smaller by PatrickThomson · · Score: 1

      Distant parts of the chip then have a communication lag, but yes, this will really help. Certainly much less lag than communicating with something outside the die.

      --
      I am one of many. My idea is not unique, nor do I expect my voice alone to sway you. I speak in a chorus of opinion.
    2. Re:Don't make them smaller by Anonymous Coward · · Score: 2, Insightful

      It's not about communication lag, it's about cost. Price goes up with die area.

    3. Re:Don't make them smaller by Anonymous Coward · · Score: 0

      I very nearly gave an EE response to why smaller and closer is better before realizing your statement was an obvious joke. My brain isn't working today.

    4. Re:Don't make them smaller by ibwolf · · Score: 4, Interesting

      Distant parts of the chip then have a communication lag, but yes, this will really help. Certainly much less lag than communicating with something outside the die.

      Wouldn't that suggest that three dimensional chips be the logical next step. Although heat dissipation would become more difficult, not to mention the fact that the production process would be an order of magnitude more complicated.

    5. Re:Don't make them smaller by TheDarAve · · Score: 5, Informative

      This is also why Intel has been investing so much into in-silicon optical interconnects. They can go 3D if they can separate the wafers far enough to put a heat pipe in between and still pass data.

    6. Re:Don't make them smaller by Anonymous Coward · · Score: 0

      Wouldn't that suggest that three dimensional chips be the logical next step. Although heat dissipation would become more difficult, not to mention the fact that the production process would be an order of magnitude more complicated.

      IBM has been working on that. That story is two years old.

    7. Re:Don't make them smaller by mrsteveman1 · · Score: 0

      Have some guacamole, you'll feel better.

    8. Re:Don't make them smaller by Xacid · · Score: 2, Insightful

      Built in peltiers to draw the heat out of the center perhaps?

    9. Re:Don't make them smaller by mlts · · Score: 1

      I'd like to see more work with peltiers, but IIRC, they take a lot of energy to do their job of moving heat to one side, something that CPUs are already tight on.

    10. Re:Don't make them smaller by Anonymous Coward · · Score: 0

      Communication plays a massive part in modern processors. The bus line lengths cause sync issues we never had to worry about a few years ago. Faster clock ticks also causes issues with changing state. When signals are fast, the high/low voltages stop appearing as on/off, but start to exhibit themselves as ramps. Add this to communication sync, and you have a real problem. This is why they don't make faster and faster processors like years gone by, there are properties of physics getting in the way of desired engineering. It's far easier to put lots of cores onto a die than make a screaming CPU.

    11. Re:Don't make them smaller by Andrewkov · · Score: 1

      Yep, common people, work smarter, not smaller.

    12. Re:Don't make them smaller by rimcrazy · · Score: 4, Interesting

      Making 3D chips is the holy grail of semiconductor processing but is still beyond reach. They've not been able to lay down a single crystal second layer to make your stacked chip. They have tried using amorphous silicon but the devices are not near as good so there is no point.

      We are already seeing the outcrop of all of this, as next years machines are not necessarily 2x the performance at the same cost. I really think that money would be better spent helping all of you coders out there in creating a language/compiler programing paradigm that can use 12 threads efficiently for something beyond rendering GTA. I certainly don't have the answer and given that that problem has not been solved yet, neither does anybody else at this time.

      Its a very very hard problem. It is going to be interesting here in the next few years. If nothing changes, your going to have to start becoming accustom to the fact that next years PC is going to cost you MORE not less and thats really going to suck.

      --
      "TV, a medium as it is neither rare nor well done." Ernie Kovacs
    13. Re:Don't make them smaller by Anonymous Coward · · Score: 0

      Wouldn't that suggest that three dimensional chips be the logical next step.

      No. It would suggest that massively parallel processors are the next logical step. You don't need every part of the chip communicating with every other part of the chip. In fact, probably more than 99% of the connectivity in modern architectures isn't being utilized. The smart design is the GPU design. It is time for a paradigm shift. We need to stop focusing on speed and start focusing on parallel processing. I am not talking 16 cores, or even 512 cores. I am talking 65K or 1M cores. Imagine the power of a 1M core machine. It would almost certainly begin to rival the power of the human brain.

    14. Re:Don't make them smaller by RulerOf · · Score: 1

      money would be better spent helping all of you coders out there in creating a language/compiler programing paradigm that can use 12 threads efficiently for something beyond rendering GTA.

      From what I've heard, the number of cores you throw at GTA doesn't matter, it still runs like crap. ;)

      --
      Boot Windows, Linux, and ESX over the network for free.
    15. Re:Don't make them smaller by Anonymous Coward · · Score: 0

      You're right. I also get dia herra when I eat mexican food.

    16. Re:Don't make them smaller by Yvan256 · · Score: 1

      Wouldn't that suggest that three dimensional chips be the logical next step?

      Yes it does. And then after that it's the robotic arm, the explosions everywhere and the "come with me if you want to live".

    17. Re:Don't make them smaller by Bigjeff5 · · Score: 1

      We are already seeing the outcrop of all of this, as next years machines are not necessarily 2x the performance at the same cost.

      I don't know how long you've been buying computers, but it has never been the case of "2x performance every year". The best it ever was was every 18 years or so, processing power doubled, and that was bumped back to about ever 2 years back in the late 80's/early 90's. But even that has never meant 2x all around performance. You might be able to crunch numbers 2x as fast after two years (never one), but there have always been bottlenecks - like RAM and hard drive speed - which have kept it down to around 50% all around performance every couple years.

      --
      Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
    18. Re:Don't make them smaller by Bigjeff5 · · Score: 1

      Damnit, missed it in preview - 18 months not 18 years.

      --
      Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
    19. Re:Don't make them smaller by CaliTinFoilHat · · Score: 1

      Blackman's Law of Limiting would surely apply to three dimensional chips as it does to cells. Three dimensional chips would necessarily be very small.

    20. Re:Don't make them smaller by Syberz · · Score: 1

      Wouldn't it be simpler to make the chips larger and instead work on scaling down the board on which the chip sits? Bigger surface for the chip would allow more transistors and making the motherboard components smaller would allow more room for the larger chips.

      I'm just wondering what the point is of making the chips smaller and smaller when the rest of the hardware isn't following suit.

      --
      ~Syberz
    21. Re:Don't make them smaller by quo_vadis · · Score: 5, Informative

      You are incorrect about the reason for lack of 3D stacking. Its not that we cant stack them. There has been a lot of work on it. In fact, the reason flash chips are increasing in capacity is because they are stacked usually 8 layers high. The problem quite simply is heat dissipation. A modern CPU has a TDP of 130W, most of which is removed from the top of the chip, through the casing, to the heatsink. Put a second core on top of it, and the bottom layer develops hotspots that cannot be handled. There are currently some approaches based on microfluidic channels interspersed between the stacked dies, but that has its own drawbacks.

      --
      Legally obligatory sig : My opinions are my own... etc etc
    22. Re:Don't make them smaller by Anonymous Coward · · Score: 0

      Mmm, late 80s, early 90s were very much a "double power every year" period. Which is why you preferred to replace every 3 years because a 3 year old PC was nearing an order of magnitude slower then a brand new one. Remember, we were jumping from 8088 to 8086 to 80286 to 386 to 486 back during that time period. And the 86/286/386 jumps were pretty huge.

      It was definitely starting to slow down to 15-18 months by the end of the 90s though.

      Now it's more like every 3-4 years before single-core speed doubles. Which is one reason why multi-core has been the way forward.

    23. Re:Don't make them smaller by grumpyman · · Score: 1

      Intel should follow suit and make the chips in 3D like the Tostito scoop - that is smaller than regular chips but hold as much if not more salsa.

    24. Re:Don't make them smaller by AhabTheArab · · Score: 1

      Now THAT is thinking outside the bun.

    25. Re:Don't make them smaller by jgagnon · · Score: 1

      Makes me wonder if there would be a way to use the generated heat to power a cooling unit. *face thinking*

      --
      Remember to maintain your supply of /facepalm oil to prevent chafing.
    26. Re:Don't make them smaller by jgagnon · · Score: 1

      The trick, obviously, is coming up with algorithms that can manage and maintain that level of parallelism. There are very few applications today that can maintain decent utilization of a 8 cores, let alone hundreds, thousands, or millions. This sort of technology would be FAR more useful on servers. Even at the current rate of growth, the need for dozens of cores on a desktop is decades out, at least.

      --
      Remember to maintain your supply of /facepalm oil to prevent chafing.
    27. Re:Don't make them smaller by Yold · · Score: 1

      that money would be better spent helping all of you coders out there in creating a language/compiler programing paradigm that can use 12 threads efficiently for something beyond rendering GTA

      There are already dozens of such languages and paradigms. The simple fact is, most applications don't need multiple threads of execution. The gains aren't worth the potential headaches, at least not for typical productivity applications (think Excel). On the other hand, games can make much better use of multiple cores... so I don't see why you are knocking them as trivial examples of parallel computing.

      The biggest performance bottleneck is still harddrives. So rather than focusing on faster CPUs, I'd love to see fast SSDs come down in price. I also can't wait until 16 gigs of RAM is standard.

    28. Re:Don't make them smaller by pclminion · · Score: 2, Informative

      A peltier gets cold on one side and hot on the other. Where are you going to put the hot side, since you're trying to put the thing in the middle of a block of silicon?

    29. Re:Don't make them smaller by CAIMLAS · · Score: 2, Informative

      The biggest performance bottleneck is still harddrives. So rather than focusing on faster CPUs, I'd love to see fast SSDs come down in price. I also can't wait until 16 gigs of RAM is standard.

      Agreed, except I'd like to disagree on your preference: I'd love to have slow SSDs come down in price and go up in capacity. It will be Good Enough, or at least significantly better.

      I mean, seriously: does the common desktop really need secondary storage which has higher throughput than the majority of DDR memory? There are SATA 6GB/s disks out there with >400MB/s rates, whereas DDR 400 only maxed out at 400MB/s. That's freaking INCREDIBLE.

      Even introducing slower 200MB/s SSDs at a lower price than current 400GB models w/ higher capacity would be significantly appreciated.

      That said, SSDs are going down in price - enough that the demand has increased again, pushing memory prices up in the past week (meh, look at Newegg if you don't believe me. 2x2GB DDR3 Crucial was $42 last week; this week it jumped up significantly for the same part #.)

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    30. Re:Don't make them smaller by The+Hatchet · · Score: 1

      Not only that, but silicon based opitical lasers could easily output significantly more information at a faster rate, meaning more of the pins can be used to provide power. Even all of them if they can make the lasers and photoresistors small enough and have the pins for power then input and output in a separate connector.

      And heat dissipation and power needs are hopefully declining as we can make transistors run on lower voltages. Imagine if we could make transistors operate within just a few millivolts. Then running my powerhorse beast of a box would not only stop using so much energy, but would no longer be responsible for heating my apt. in the winter. In the case of lower power use, and therefore lower heat production, you could layer processors easily. The main barrier there is the development of vertical wires in the processor, but progresss is moving fast in that area.

      I would also like to see better utilization of multiple cores and GPUs. Because I have 2 GTS 250s waiting for a version of autodesk inventor that can utilize them for rendering. Instead I just watch my 8 threads max out for a couple hours, or a couple days depending on the job. If my GPUs were put into use, it would take maybe a half an hour for the most intensive renderings I have developed. No real reason that there can't be better utilization of multi-threading. The coding behind it isn't exactly that difficult, it just requires putting forth some extra time. That, and bigger/faster solid state drives. I hate having only a 750 gb hd that costs like 60 bucks and stops working after a couple of years. 750 is like nothing, considering they can put 64 GB of data onto a chip half the size of a fucking dime. If they could take that storage density and scale it up to the size of an SSD, you could have a few terabytes of incredibly fast hard drive.

      --
      Where is the mod rating for "scary"? Also, ...
    31. Re:Don't make them smaller by rimcrazy · · Score: 2, Interesting

      No, you are incorrect. You are talking about stacked gates. That is significantly different than what I am talking about which is making entire stacked devices where you have a second level of additional devices including sources and drains as well as gates. Work has been tried with amorphous silicon with mixed results, no of which amount to much.

      You are correct in that the power density issue trumps all other concerns.

      And in the end economic issues will trump everything.

      --
      "TV, a medium as it is neither rare nor well done." Ernie Kovacs
    32. Re:Don't make them smaller by Retric · · Score: 1

      That's how heat pipes work.

    33. Re:Don't make them smaller by The+Hatchet · · Score: 1

      Sure, a lot of productivity programs don't need multiple cores, but they also don't use that much processing power relatively to begin with. Running 50 instances of microsoft word doesn't even show a noticeable increase in use on my system. There are, however, many programs that could significantly improve performance by multi-threading, and max out a single process. Solid modeling programs, building modeling programs, fluid dynamics and stress analysis, rendering, format conversion, and so on. Also, programs that have to do a lot of processing in a short time for some task, could be threaded out to speed up response time. Wouldn't hurt anyone. But gaming is certainly not the only good use. I know Autodesk inventor uses all 8 of my threads to render, but it doesn't use my graphics cards. For a rendering of a video animation, my graphics cards would be able to solve a frame in a couple seconds, unlike my 8 threads, which take about a minute to do it. I would love to utilize my multi-GPU system so that the renderings run faster. 2 days is just too long for a 1280x720 30 second rendering of a complex mechanical system.

      But yes, for general purposes and processes that don't use a lot of power, hard drives are the biggest bottleneck. Also, my computer has 12 GB ram. It ain't 16, but I have only maxed it out a few times. In 6 sticks, 2 triple channel kits, DDR3 at 2000hz I believe, I built it a good 10 months ago now.

      --
      Where is the mod rating for "scary"? Also, ...
    34. Re:Don't make them smaller by ChefInnocent · · Score: 1

      I think Excel could definitely gain by going multithreaded. I'm running it in the background right now, and it runs like a 2 legged dog on a lake of molasses. If they could intelligently break down the calcs into linear algebraic equations, or run multiple non-dependent cells over the same function concurrently, that would save a bunch of time. Of course, it might help if I stopped using Excel as a giant calculator with many lines of the same function with different inputs. It may also be their "security model" that's preventing me from writing to multiple cells within a function, thus limiting my ability to optimize.

    35. Re:Don't make them smaller by Dylan16807 · · Score: 2, Insightful

      DDR, along with almost all desktop memory, has a 64-bit interface. So DDR 400 is at 3200MB/s, and if you go dual-channel you get 6400MB/s. Still, having bulk storage only an order of magnitude below main memory is wonderful.

    36. Re:Don't make them smaller by Rival · · Score: 2, Funny

      A peltier gets cold on one side and hot on the other. Where are you going to put the hot side, since you're trying to put the thing in the middle of a block of silicon?

      Easy -- just put two peltiers together, hot sides facing each other. Problem solved! ;-)

    37. Re:Don't make them smaller by Khyber · · Score: 1

      Actually, yes.

      Micro peltier coolers, facing inwards for their heat side, with a micro heatpipe between.

      We've been working on microfluidics for a while.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    38. Re:Don't make them smaller by majid_aldo · · Score: 1

      If nothing changes, your going to have to start becoming accustom to the fact that next years PC is going to cost you MORE not less and thats really going to suck.

      grammar errors:
      - youre -> you're
      - accustom -> accustomed
      - years -> year's
      - thats -> that's

      --
      --- widget evolution: enhanced, plus, super, ultra, extreme, exxxtreme, ultra-extreme, ..etc.
    39. Re:Don't make them smaller by Anonymous Coward · · Score: 0

      There are plenty of good techniques to do multi-threaded programming well. It takes a while for software to shift in that direction but I don't think this is a big problem.

      I see the biggest problem with multi-threaded programming is mathematics. There is a limit on how much you can do in parallel when you have data dependencies. There are some algorithms that can be split up to do work in parallel but there are others that cannot.

      As a software engineer I hate the move to parallelism. I don't mind the challenge but this can only be a short-term solution. It pushes most of the problem to software where there is only so much we can do. Unlike clock speed where we ran into physical limitations, in parallelism we run up against mathematical limitations.

    40. Re:Don't make them smaller by networkBoy · · Score: 1

      no.
      It would be impossible.
      There is no realistic way to drop a Si layer on top of metal, then dope it properly.
      see, the thing is, a chip is built on the Si wafer basically setup as a field of npn wells and pnp wells, then the metal interconnects these wells in the appropriate way to make a functioning circuit. To go 3D you would need to add another layer of Si, and that is not really possible.
      -nB

      --
      whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
    41. Re:Don't make them smaller by Anonymous Coward · · Score: 0

      I think this statement is actually revealing the most important problem with shrinking chips (let alone going 3D):

      “What’s started to happen is that shrinking is going to keep going on, but the speed of the transistor is not going up as quickly as it used to. The most critical thing is they’ve stopped taking less energy to switch,” - ARM’s chief technology officer, Mike Miller

      CPU transistors are using the same energy now regardless of their size; that means if we doubled the number of transistors (even with the same die size using a smaller process) we double the power requirements...this is a bit of a spanner in the works for mobile low power computers; and there does not really seem to be a clear way around this at the moment (well they go on to talk about smart power management inside their processors to disable and enable needed transistors but this is not really a solution IMHO).

      Desktop users may not be as affected, but it looks like we are going to be dealing with some pretty elaborate cooling systems over the next decade.

    42. Re:Don't make them smaller by OrangeCatholic · · Score: 1

      >There are SATA 6GB/s disks out there with >400MB/s rates,

      Right, that's why the charts top out at 158, Enterprise 2010 chart tops out at 200 and it's all SAS.

      Caught reading the specs again?

    43. Re:Don't make them smaller by OrangeCatholic · · Score: 1

      >Even at the current rate of growth, the need for dozens of cores on a desktop is decades out, at least.

      When you're applying an effect in Photoshop, don't most of the effects only depend on the pixels near it? So Photoshop should be scalable to number of cores equal to the number of pixels. No fancy programming needed, just break up the work into chunks.

      Video editing would be the same way.

      Most other productivity apps - those involving text - are usually focused on interrupts from the user, network or I/O, so they wouldn't benefit much at all, except maybe in rendering.

    44. Re:Don't make them smaller by gfody · · Score: 1
      --

      bite my glorious golden ass.
    45. Re:Don't make them smaller by Anonymous Coward · · Score: 0

      A "side" doesn't necessarily need to be a rectangular block. It could for instance be a dumbbell shape with one side in the chip and the other outside.

    46. Re:Don't make them smaller by TheTurtlesMoves · · Score: 1

      I really think that money would be better spent helping all of you coders out there in creating a language/compiler programing paradigm that can use 12 threads efficiently for something beyond rendering GTA..

      I have zero problems using all 512 cores on our cluster. I also have no problems using all 6 cores at home too. We have been doing parallel programing for decades. If the coder can't code for it, the problem is between the seat and the keyboard.

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    47. Re:Don't make them smaller by Anonymous Coward · · Score: 0

      3D chips? I don't want to have to wear 3D glasses to install a CPU!

    48. Re:Don't make them smaller by w0mprat · · Score: 2, Insightful

      ... I really think that money would be better spent helping all of you coders out there in creating a language/compiler programing paradigm that can use 12 threads efficiently for something beyond rendering GTA.

      The entirety of programming is we know it is stuck in a single threaded paradigm and making the shift to massively parallel computing requires a huge shift in thinking.

      This is so hard because our technique, languages and compilers all have their roots in a world that barely even multi-tasked let alone considered doing anything in parallel for performance.

      Every coder that ever learnt to code, coded for kicks or money, learnt this way, and they still do.

      We've come all this way without ever having to think in parallel. I stopped developing in 2003, having never had to really consider parallelism.

      Even in 2010, as kids today start learning programming linearly still, and you go a long way before having to consider a second thread.

      I think calling it a whole new paradigm is not doing the change required justice. It's about re-learning and re-thinking everything.

      Frankly every day I think it's a fucking miracle that software as a whole performs as well as it does, and that our civilizations infrastructure can be use this technology, and that Moore's law hasn't stopped it's inexorable march yet.

      It all works result of a brute force of millions of smart people problem solving line by line, getting it to compile, run and work without crashing too often. Software development now sees teams of hundreds of developers, open source projects can have thousands. One should be forgiven for thinking programming itself hasn't improved terrifically. Advances in software are still largely coming with throwing human resources at problems.

      Clearly then, the deficiencies are in software, not hardware.

      I won't shed a tear when Intel can no longer make progress with it's enormous investment in producing silicon based chips, and may have to consider graphene et al. But it's far from the end of the story. Silicon is only one element on the periodic table after all.

      --
      After logging in slashdot still does not take you back to the page you were on. It's been that way for 20 years.
    49. Re:Don't make them smaller by w0mprat · · Score: 1

      Stacks 2,3,4 or more layers deep you are talking about nanometers deep. Now I'm not sure what the thermal conductivity of a chip is, but that is a very short distance for heat to conduct through. I really don't see how there could be too much of a problem conducting the heat out of lower layers.

      Of course the issue is the power density, watts per square cm, goes way up as you start stacking. The problem is not in the chip so much, but in the cooling attached to it. Although I think heatpipe technology has the chops to deal with it here.

      --
      After logging in slashdot still does not take you back to the page you were on. It's been that way for 20 years.
    50. Re:Don't make them smaller by BraksDad · · Score: 1

      Can you say "Borg Cube?"

      Now bow to your new overlord chips.

      --
      Slowly waving my hand - "This is not the sig you are looking for."
    51. Re:Don't make them smaller by CAIMLAS · · Score: 1

      Someone hasn't been paying attention...

      For starters, OCZ, Intel, and Crucial/Micron have had the better performing SSDs for some time now, and they're not even on your review's list.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    52. Re:Don't make them smaller by Anonymous Coward · · Score: 0

      It might be simpler, but it isn't necessarily cheaper. Higher integration does help with costs at the system level, but it may be offset by the chip-level cost. The larger the die, the lower the yield, for a given "defect per unit area". In effect, you are buying by the wafer-- lower yield ends up being higher cost per *working* chip. I've severely oversimplified this explanation, but those are a couple of the major factors being considered.

    53. Re:Don't make them smaller by thedanyes · · Score: 0

      While I agree with your main statement: (Larger, cheaper SSDs would be nice even if we had to live with them being a bit slower), your estimates of hard disk and SSD speeds are pretty far off.

      Yes, the SATA 6Gb/s standard supports up to about maybe 600MB/s in practical operation. No, mechanical hard disks do not approach 400MB/s (let alone >400MB/s). The fastest mechanical hard disks on the market right now might get you 170MB/s maximum in a sequential benchmark (read: not a real-world scenario), and only when reading from the fastest part of the disk.
      http://hothardware.com/Reviews/WD-VelociRaptor-600GB-Fastest-HD-Ever/?page=6

      The fastest SATA SSDs are pushing maybe 300MB/s in these benchmarks, and usually only for read speeds. The reason people are seeing such disproportionate performance improvements with SSDs is access latency. The fastest hard disk might have 6.0ms average latency. SSDs are usually below 0.1ms.

    54. Re:Don't make them smaller by Anonymous Coward · · Score: 0

      I really think that money would be better spent helping all of you coders out there in creating a language/compiler programing paradigm that can use 12 threads efficiently for something beyond rendering GTA. I certainly don't have the answer and given that that problem has not been solved yet, neither does anybody else at this time.

    55. Re:Don't make them smaller by Xacid · · Score: 1

      You'd use them to transport high temperatures from inside to the outside. Geometrically this should be possible if you're creative.

    56. Re:Don't make them smaller by Anonymous Coward · · Score: 0

      DDR 400 refers to 400 Mbits/s PER PIN. Since a DIMM is usually 64-bits that actually means max transfer speed of 3200 Mbytes/s (where M unfortunately in this case refers to 1e6 not 2^20).

    57. Re:Don't make them smaller by GWRedDragon · · Score: 1

      Some problems are inherently easy to make parallel, some can be easily made parallel up to a certain point but not further (such as separating discrete tasks), while others are extremely difficult to parallelize at all. Parallel is not a panacea, and no 'paradigm shift' will change that.

      Of course, there is nothing wrong with making sure that possible avenues of parallelization are taken advantage of where they exist, but that is hardly everywhere.

  2. The Atoms by Ironhandx · · Score: 5, Interesting

    They're going to hit atomic scale transistors fairly soon from what I can see as well, the manufacturing process for those is probably prohibitively expensive but that is as small as they can go(according to our current knowledge of the universe at least).

    I can't imagine Intel has all of its eggs in one basket on Extreme Ultraviolet Lithography though. Something thats been in development for even 5 years and doesn't show any concrete signs of success should at least have alternatives developed for it. After 5 years if you still can't say for certain if its ever going to work, you definitely need to start looking in different directions.

    1. Re:The Atoms by Lunix+Nutcase · · Score: 4, Funny

      Something thats been in development for even 5 years and doesn't show any concrete signs of success should at least have alternatives developed for it.

      You haven't followed much of the history of Itanium's development have you?

    2. Re:The Atoms by Ironhandx · · Score: 1

      No, I really haven't. I tend not to pay much attention to things that are released more than 2 years after their original announced release date.

      Though, I have to point out I didn't advocate terminating a project after 5 years of zero results(a la Itanium) just looking in additional directions and not keeping all the eggs in the questionable basket.

    3. Re:The Atoms by Lunix+Nutcase · · Score: 1

      You seem to miss the point. You imagine that Intel doesn't point all of its eggs in one basket. The development of Itanium disproves that notion as they had no other real alternatives being developed at the same time.

    4. Re:The Atoms by mrsteveman1 · · Score: 1

      You haven't followed much of the history of Itanium's development have you?

      I saw the movie though, Leo dies at the end.

    5. Re:The Atoms by Anonymous Coward · · Score: 0

      It's people like you that caused Duke Nukem Forever's cancellation. They realized there were just too many of you stupid people who would not play the game just because it was delayed for around a decade.

    6. Re:The Atoms by grahamsz · · Score: 1

      Yeah, it's really hurt them. They've been wildly unprofitable since then

    7. Re:The Atoms by bill_mcgonigle · · Score: 1

      They're going to hit atomic scale transistors fairly soon from what I can see as well

      Yeah, there was an article here in the spring on atomic computing, where I did a little math on it. I was surprised, but it worked out that in roughly a decade Moore's Law would get down to atomic transitors if reducing the part size was the method employed.

      I had always presumed before that it would never run out, but it's going to have to zig sideways if that's going to be true.

      Google recently bought that company working on packet switched CPU's - I guess I really don't care at all about transistor count, just performance - alternates to the superscalar approach would be fine too.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    8. Re:The Atoms by Griffon26 · · Score: 1

      The article calls it "a (...) partnership to develop EUV". That's not just product development.
      5 years is not a long time at all if you include the research period (and I don't mean general research in the area, but focused research/feasibility studies).

    9. Re:The Atoms by alen · · Score: 1

      i remember reading a long time ago that 90nm or 65nm would be impossible due to physics and science

    10. Re:The Atoms by Lunix+Nutcase · · Score: 1

      Because I made either the claim that it hurt Intel or it made them unprofitable? Oh wait...

    11. Re:The Atoms by QuantumLeaper · · Score: 1

      No, it around 4nm is the limit, since the electrons will do whatever the hell they want too. I remember reading a electronics magazine from the early 80s that stated that 50MHz was going to be impossible because of noise. I don't think we will hit a limit for quite a while, whenever there is some sort of limit, we figure a way around it.

    12. Re:The Atoms by Ironhandx · · Score: 2, Insightful

      Theres a difference here... those reports were about being practically impossible, not theoretically impossible, on the going below the atomic scale you're hitting the theoretically impossible(given current understandings) point along with the practically impossible. We've had the theory for atomic size transistors for quite a while, its the practical that really needs to catch up.

    13. Re:The Atoms by Patch86 · · Score: 1

      Yeah, there was an article here in the spring on atomic computing, where I did a little math on it. I was surprised, but it worked out that in roughly a decade Moore's Law would get down to atomic transitors if reducing the part size was the method employed.

      Which raises the perfectly relevant point that reducing transistor size is not the only method of increasing processing speed, and so keeping up with Moore and his Law.

      Fundamental changes to the architecture would be a nice place to start. Just because Intel feel irrevocably tied to i86 it doesn't make it the only option. Maybe when the last of the other tricks have been exhausted (in the best possible way- clinging to i86 has caused Intel to advance the chip fabrication industry to the limits of modern science) we might finally be forced to abandon this giant tombstone of an architecture that has been hanging so around our collective necks.

    14. Re:The Atoms by cheesybagel · · Score: 1

      The other alternatives to EUV (like e-beam) have low productivity. It takes a long time to etch a chip with those techniques. Intel has bet on EUV for a long time now. Since EUV failed to be on time, they had to use techniques such as immersion lithography and double patterning which they had previously derided as overly expensive.

    15. Re:The Atoms by hankwang · · Score: 5, Informative

      I deal with EUV lithography for a living. Not at Intel, but at ASML, the world's largest supplier of lithography machines and the only one that has actually manufactured working EUV lithography tools.

      Something thats been in development for even 5 years and doesn't show any concrete signs of success should at least have alternatives developed for it. After 5 years if you still can't say for certain if its ever going to work, you definitely need to start looking in different directions.

      You are misinformed. On our Alpha development machines, working 22 nm devices were already manufactured last year. (source) We are shipping the first commercial EUV lithography machines in the coming year (source, source) A problem for the chip manufacturers is that the capacity on the alpha machines is rather low and needs to be shared among competitors.

      There is a temporary alternative; it is called double patterning (and triple patterning, etcetera). The first problem is that you need twice (thrice) as many process steps for the small features, and also proportionally more lithography machines that are not exactly cheap. The second problem is that double patterning imposes tough restrictions on the chip design; basically you can only make chips that consist mostly of repeating simple patterns. That is doable for memory chips, but much less so for CPUs. Moreover, if you want to continue Moore's law that way, the manufacturing cost will increase exponentially, so this is not a long-term viable alternative.

      You can bet that the semiconductor manufacturers have looked for alternatives. But those don't exist, at least not viable ones.

    16. Re:The Atoms by cheesybagel · · Score: 1

      Things are made of molecules. Which are made of atoms. Which are made of quarks. So is the atomic scale really the smallest we can go?

    17. Re:The Atoms by jgagnon · · Score: 1

      There is nothing inherently inferior about x86 compared to any other instruction set or architecture. Intel has proven time and again that they can push incredible performance with it. And, by the way, Intel did try to move away from it with Itanium and VLIW technology.

      --
      Remember to maintain your supply of /facepalm oil to prevent chafing.
    18. Re:The Atoms by Ironhandx · · Score: 1

      Someone mod this guy up, this is quite interesting.

      I have to say, I wasn't aware of someone succeeding where intel failed. I assumed that intel would have simply licensed the tech from anyone that had by now. Then again, just last year means that the licensing talks could easily still be going on. I'm going to keep an eye on this from now on. Thanks!

    19. Re:The Atoms by Ironhandx · · Score: 1

      Quarks we can't really manipulate at all yet and while theres some string and quantum theory for how none of it is even approaching the realm of solid like the atomic stuff has been for many years now. We can barely detect quarks and theres god only knows how many potential different kinds of quarks and particles theorized about that we can't even **detect** yet.

      My point is we're running out of the remotely testable area into the "Well, maybe if this was like this and that was like that then this thing here would do this and the whole thing would go *pzzt*" realm of science.

      It may not be the smallest we can eventually go, but the next level is going to required a bare minimum of decades just to build the test facilities to get the direction we need to go in. The LHC is just a starting point. Which means that most of that stuff is practically impossible to most anyone alive today and theoretically impossible for the most part as any theories on the subject currently really only have enough evidence with them to be hypothetical rather than theoretical. Unless there are some fantastic medical advances, likely no one living today will be alive by the time we can make use of it, and none but the very young will even be alive to see the hypothetical solidify into more useful theories.

    20. Re:The Atoms by Anonymous Coward · · Score: 0

      You can't exactly compute something using the state of a transistor that will flip randomly due to your having merely observed it. So yes, there is definitely a limit.

    21. Re:The Atoms by rienafairefr · · Score: 1

      EUV lithography is not abandonned, far from it. Evolution is good (ie, not so bad), even if the available tools are quite slow yet, but they're just prototypes. EUV needs a lot of work, and intel spent a lot in trying to continue DUV litho (double patterning, optics, mask corrections, etc etc), so they are not the best prepared with euv. intel is not alone in making chips in the world, also, you know. e beam lithography with multiple beams is also tried in a lot of stuff, and might reach maturity before euv, who knows. also other techniques (bottom up) to advance moore's law are explored. Not all hope is lost. If you'd see the amount poured in R&D just so that peformance always rise and price always fall, it is obscene :-)

    22. Re:The Atoms by Anonymous Coward · · Score: 0

      They have to add extra silicon to translate an archaic CISC instruction set with a ridiculous memory model to boot into an internal RISC instruction set in order to "push incredible performance with it"; that means more design work, more silicon, and more chance for defects (=lower yield).

      How is that not inherently inferior?

      And yeah, they tried Itanium, so GP's point of them feeling tied to x86 is wrong. But this "all architectures are Turing-complete, so the suckingest one we can find must be OK" is bullshit.

    23. Re:The Atoms by hankwang · · Score: 3, Informative

      I wasn't aware of someone succeeding where intel failed. I assumed that intel would have simply licensed the tech from anyone that had by now.

      IMEC is not the only ASML customer who has played with one of the two EUV Alpha tools, but it's the only one I could find with a quick Google search that has published the results. IMEC is a research institute. Other customers (actual chip manufacturers) have little to gain by disclosing to the competition exactly how much progress they have made.

      Then again, just last year means that the licensing talks could easily still be going on. I'm going to keep an eye on this from now on.

      Licensing is not the business model. The article suggests that Intel develops these machines ("fancy camera's") themselves, but in reality, they simply buy the machines from one of the three manufacturers (ASML, Nikon, and Canon). We spend an R&D budget of 500 M€ per year to develop these machines; Intel's R&D costs are likely mostly in the design of their chips and optimizing process parameters to squeeze as much as possible out of their fabs.

    24. Re:The Atoms by hankwang · · Score: 3, Informative

      I forgot to add a disclaimer: the opinions expressed are mine and not necessarily my employer's, etcetera.

    25. Re:The Atoms by Khyber · · Score: 1

      Except wasn't the rumor now being circulated that Gearbox picked up the IP?

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    26. Re:The Atoms by Khyber · · Score: 1

      Have you guys managed to make silicon LEDs with incredible output per watt yet or are we still hosed and stuck with sapphire wafer substrates?

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    27. Re:The Atoms by Fulcrum+of+Evil · · Score: 1

      It really did hurt them. Or were you not paying attention? AMD managed to leapforg them for a few years and intel basically adopted their strategy for a 64 bit ISA

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    28. Re:The Atoms by Ironhandx · · Score: 1

      Ahh, I assumed it would be a licensing model for intel to incorporate the tech into their manufacturing processes more completely but I guess buying the machine works just as well for them. Most of their R&D costs would go into making things like that super expensive fancy camera produce something that does what they want it to(and the design of the thing it produces etc of course)

      I have to admit I'm a little surprised to see Canon on that list though. I've heard so little about Canon lately they were sort of pushed into the back of my head towards the list of "tech companies circling the drain", though as I've heard so little this probably isn't even close to being the case

    29. Re:The Atoms by petermgreen · · Score: 1

      Things are made of molecules
      Some things are made up of molecules, others aren't (or are one big molecule depending on your point of view)

      ICs are generally built on one big crystal (a large lattice of atoms all bonded), we add impurities to parts of this crystal to change it's electrical properties (by creating either free electrons in the conduction band or holes in the valance band) and add layers of other things on top of it to make our circuit.

      Electronics is really all about controlling the movement of free electrons or holes (generally each atom of dopant produces either a free electron or a hole) within said crystal.

      Maybe computing inside an atom will be possible at some point but if it is it will be a totally new technology, not electronics.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    30. Re:The Atoms by Anonymous Coward · · Score: 0

      I worked at Intel in the late 90's on EUV (EUV-LLC time). I distinctly remember the mantra "On the floor in '04". Well, we're still waiting. Nice progress on the tool, source & process, but it appears to be at least 3 years away from HVM.

    31. Re:The Atoms by drsmithy · · Score: 1

      Which raises the perfectly relevant point that reducing transistor size is not the only method of increasing processing speed, and so keeping up with Moore and his Law.

      Despite frequent misrepresentation, Moore's law is specifically about transistors, and says nothing about overall, or general, computing performance.

      In other words, you have it backwards.

    32. Re:The Atoms by wen1454 · · Score: 2, Informative

      The computational power of the human brain, which uses only 25 watts, is estimated to be between 10^13 and 10^23 instructions per second [1]. This means the human brain is 100 to 10^12 times more powerful than a high-end desktop. So computers still have a way to go before they could possibly approach any physical limits.

      1. Merkle, 1989: 10^13-10^16 IPS; Maravec, 1997: 10^14 IPS; Thagard, 2002: 10^23 IPS; Modha, 2009: 3.8*10^16 IPS.

    33. Re:The Atoms by TheTurtlesMoves · · Score: 1

      So what is the UV source (Excimer laser?) and what optical elements are you using. Its it mostly reflective or are there materials sutable for deep UV? Sorry but the website is the typical marketing tripe.

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    34. Re:The Atoms by hankwang · · Score: 1

      I have to admit I'm a little surprised to see Canon on that list though. I've heard so little about Canon lately they were sort of pushed into the back of my head towards the list of "tech companies circling the drain"

      Canon had only 9% market share in 2009; indeed they don't seem to do well at the moment. However, 2009 numbers are probably distorted by the recession.

    35. Re:The Atoms by hankwang · · Score: 1

      So what is the UV source (Excimer laser?)

      Like Intel and others buy lithography machines from ASML and competitors, we buy our (E)UV sources from other companies as well; Cymer, Ushio, and Gigaphoton are producers of such sources. (source). The idea is that you hit a suitable material with a gigantic laser pulse or electrical discharge, thereby heating it to something like 10^5 kelvins such that it starts emitting EUV radiation, along with loads of other wavelengths that you have to filter out. (at 10^5 K, the thermal radiations peaks at about 25 nm). Here is an old (2006) article about EUV sources.

      and what optical elements are you using. Its it mostly reflective or are there materials sutable for deep UV?

      Deep UV usually means 190 nm, for that there are lenses. In EUV (13 nm), mirrors are used. The reason for the large jump in wavelength is that inbetween, there are neither suitable mirrors, nor lenses; at least so I believe.

      the website is the typical marketing tripe.

      I think the ASML website has white papers with more technical background, but you can find more information in patents and proceedings from semiconductor-industry conferences. I'm not allowed to tell you anything here that is not already published. :-)

      (Opinions are mine, not ASML's)

    36. Re:The Atoms by Ironhandx · · Score: 1

      OH theres definitely a ways to go and new configurations and methods to discover but the size of the transistors themselves, which is what I'm referring to, will be down to the 1-10 atom range pretty soon. The speed can continue to increase after they hit that wall, but the transistors won't be getting any smaller.

      Also, the human brain weighs around 2kg, so you would actually need those 100 processors to make up the same weight since most of them, even the dual cores, are around 15-20 grams.

    37. Re:The Atoms by TheTurtlesMoves · · Score: 1

      Thanks--all very helpful and interesting.

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    38. Re:The Atoms by gbeagle2112 · · Score: 1

      Within our current understanding of quantum chromodynamics (field theory of the strong interaction - i.e. the interaction between quarks) color confinement means effectively you cannot have 'free' quarks. Of course you can have color-neutral bound states of quarks, but so far the only stable quark bound state is the proton*. Assuming QCD is more or less correct the smallest bit we can work with is effectively protons and electrons. *The neutron is only stable within an atomic nucleus. Free neutrons will decay into a proton.

    39. Re:The Atoms by wen1454 · · Score: 1

      Yes, but that is 100 processors with no hard disk, RAM or motherboard.

    40. Re:The Atoms by stevesliva · · Score: 1

      Something thats been in development for even 5 years and doesn't show any concrete signs of success should at least have alternatives developed for it. After 5 years if you still can't say for certain if its ever going to work, you definitely need to start looking in different directions.

      You are misinformed. On our Alpha development machines, working 22 nm devices were already manufactured last year. (source) We are shipping the first commercial EUV lithography machines in the coming year (source, source) A problem for the chip manufacturers is that the capacity on the alpha machines is rather low and needs to be shared among competitors.

      Yeah, I think the OP has a little intuition of the relatively common situation where an ailing older technology's flaws are somewhat obvious and well publicized for years and years, but the older technology staggers on far far longer than expected. For both the reason that EUV has been slow to mature, and that 193nm has been surprisingly resilient. It's wrong to conclude that EUV will never be practical, just that one should be very careful about declaring when it is necessary.

      A similar situation is going on with the broader issue discussed here-- the eventual replacement of CMOS with some other technology. People are eager to declare the death of CMOS and the need for diamond substrates or nanotubes or whatever, but CMOS will stagger along much longer than the advocates of the new technologies hope because it is easier to extend CMOS than it is to make something truly different more mature and practical.

      --
      Who do you get to be an expert to tell you something's not obvious? The least insightful person you can find? -J Roberts
    41. Re:The Atoms by dullnev · · Score: 1

      There is nothing inherently inferior about x86 compared to any other instruction set or architecture....

      ORLY? "The x86 architecture used in most PC systems poses particular difficulties to virtualization" http://en.wikipedia.org/wiki/Hypervisor

    42. Re:The Atoms by jgagnon · · Score: 1

      And linked to from that same article:

      http://en.wikipedia.org/wiki/Intel_VT-x#Intel_Virtualization_Technology_for_x86_.28Intel_VT-x.29

      Seems like they fixed it easily enough...

      --
      Remember to maintain your supply of /facepalm oil to prevent chafing.
    43. Re:The Atoms by Anonymous Coward · · Score: 0

      goddamn linux faggot, gtfo and go fuck a penguin. dumb bitch.

    44. Re:The Atoms by Anonymous Coward · · Score: 0

      Can I ask then why is it that a hybrid approach isn't taken for processors? Is it too difficult to run the process of double patterning the cache at 22nm and then run the processor side at 32nm? Since about half of the chip these days is cache I don't really understand why this couldn't be made to work other than you have all of the cost of 22nm at 32nm processor performance. Since the bottleneck in pretty much all processors is memory bandwidth it feels like this would be a substantial improvement.

    45. Re:The Atoms by LordVader717 · · Score: 1

      It depends on what you consider impossible to mean. Atomic scale electronic devices are certainly feasible, but it certainly won't be the kind of electronics or processes that Moore would have been thinking of. Atomic distances are around 0.1 nanometers, so a 22nm cell is about 200 atoms wide. And a cell contains multiple components, so the actual elementary components are even smaller.
      Matter doesn't behave deterministically on these scales. But boolean logic requires it. There are theoretical ways to work around this, but it would certainly be a radically different way of designing electronics. In other words it won't be a classical transistor.

      Computers will continue to get better and faster, but Moore's original law about transistor density won't be able to stand for very long any more.

  3. Why do they need to? by Revotron · · Score: 4, Funny

    Why does Intel need to push the envelope that hard and that fast just to create a product that will, in the end, have extremely low yield and extremely high cost?

    Just so they can adhere to some ancient "law" proposed by one of their founders? It's time to let go of Moore's Law. It's outdated and doesn't scale well... just like the x86 architecture! *ba-dum, chhh*

    1. Re:Why do they need to? by mlts · · Score: 4, Interesting

      At the extreme, maybe it might be time for a new CPU architecture? Intel has been doing so much stuff behind the scenes to keep the x86 architecture going, that it may be time to just bite the bullet and move to something that doesn't require as much translation?

      Itanium comes to mind here because it offers a dizzying amount of registers, both FPU and CPU available to programs. To boot, it can emulate x86/amd64 instructions.

      Virtual machine technology is coming along rapidly. Why not combine a hardware hypervisor and other technology so we can transition to a CPU architecture that was designed in the past 10-20 years?

    2. Re:Why do they need to? by Andy+Dodd · · Score: 2, Insightful

      The problem is that x86 has become so entrenched in the market that even it's creator can't kill it off.

      You even cited a perfect example of their last (failed) attempt to do so (Itanic).

      --
      retrorocket.o not found, launch anyway?
    3. Re:Why do they need to? by Anonymous Coward · · Score: 0

      Less power, and faster can still be a money maker to off set the research and production costs.

    4. Re:Why do they need to? by Lunix+Nutcase · · Score: 1

      Itanium comes to mind here because it offers a dizzying amount of registers, both FPU and CPU available to programs.

      And it's been such a smashing success in comparison to x86, right?

    5. Re:Why do they need to? by ibwolf · · Score: 1

      You are right in that a new architecture could offer improved performance, however it is a one shot deal. Once you've rolled out the new architecture there will be a short period while everything catches up and then you are right back to cramming more on the die.

    6. Re:Why do they need to? by timeOday · · Score: 1

      Yeah, progress is such a hassle.

    7. Re:Why do they need to? by maxume · · Score: 1

      Each time they shrink the die size, they reduce the number of silicon in the chip, lowering the cost of the silicon in the chip, lowering the cost of the chip.

      If they had not successfully increased yield on past technology generations, do you think chips today would still be cheaper and faster?

      --
      Nerd rage is the funniest rage.
    8. Re:Why do they need to? by T-Bone-T · · Score: 2, Insightful

      Moore's Law describes increases in computing power, it does not proscribe it.

    9. Re:Why do they need to? by mlts · · Score: 1, Insightful

      Very true, but it eventually needs to be done. You can only get so big with a jet engine that is strapped onto a biplane. The underlying architecture needs to change sooner or later. As things improve, maybe we we will get to a point where we have CPUs with enough horsepower to be able to run emulated amd64 or x86 instructions at a decent speed. The benefits will be many by doing this. First, in assembly language, we will save a lot of instructions because programs will have enough registers to do actions at once, rather than keep shuttling data to and from RAM to complete a calculation. Having few access to and from RAM will speed up tasks immensely because register access is so much faster. Take a calculation that adds up a bunch of numbers. The numbers can be loaded into separate registers, added, result dropped back into RAM. With the x86, it would take a lot of load and stores to do the same thing.

    10. Re:Why do they need to? by mlts · · Score: 4, Insightful

      x86 and amd64 have an installed base. Itanium doesn't. This doesn't mean x86 is any better than Itanium, in the same way that Britney Spears is better than $YOUR_FAVORITE_BAND because Britney has sold far more albums.

      Intel has done an astounding job at keeping the x86 architecture going. However, there is only so much lipstick you can put on a 40 year old pig.

    11. Re:Why do they need to? by the_fat_kid · · Score: 0

      "However, there is only so much lipstick you can put on a 40 year old pig."

      Hey, you insensitive clod, that's my wife!

      --
      -- Sig under construction...
    12. Re:Why do they need to? by Twinbee · · Score: 1

      And if we did, are we talking about 2x speed returns very roughly, or even up to 20x?

      --
      Why OpalCalc is the best Windows calc
    13. Re:Why do they need to? by Anonymous Coward · · Score: 0

      >However, there is only so much lipstick you can put on a 40 year old pig.

      The same might be said of UNIX. Or more recent clones of said 40 year old porcines.

    14. Re:Why do they need to? by Joce640k · · Score: 1

      Itanium failed because it used a VLIW architecture - great for specialized processing tasks on big machines but for general purpose computing (ie. what 99.9% of people do) it wasn't much faster than x86.

      Are computers really 'too slow' now? It seems to me that an x64 desktop at 3GHz is fast enough for just about anything a normal person would do. The only "normal task" I can think of that's too slow at the moment is decoding x264 video on netbooks and they're better off with a little hardware decoder tacked on than a mega-CPU upgrade.

      Games are more constrained by RAM and GPU than CPU at the moment. RAM and GPUs are catching up fast and game logic is a good target for parallel processing - more cores is the way to go (by that I mean "will be cheaper/easier than making the existing cores faster").

      For almost everything else, more cores and better software would give much more of a boost then making individual cores faster.

      At the end of the day the deciding factor will be simple economics: If a process/factory costs $X then Intel has to sell $Y chips to justify it.

      Expensive chips are going to be an increasingly harder sell. I can get a decent quad core for $100 now and soon it will be more like $50.

      If only 0.005% of people are buying the $1000 chips then the factories aren't going to be built.

      --
      No sig today...
    15. Re:Why do they need to? by psbrogna · · Score: 1

      The point of a new architecture would be for it NOT to be a one shot deal and that it would give you ample room for evolution before hitting physical limitations at least for a few "generations". The problem of stepping sideways is the risk. You don't have to look too far on /. to find other examples of civilization being irrationally tied to a legacy they're unwilling to walk away from even if by doing so they accept mediocre technology.

    16. Re:Why do they need to? by pitchpipe · · Score: 1, Troll

      However, there is only so much lipstick you can put on a 40 year old pig."

      Hey, you insensitive clod, that's my wife!

      Sarah Palin is your wife!?

      --
      Look where all this talking got us, baby.
    17. Re:Why do they need to? by imgod2u · · Score: 3, Informative

      Because nowadays, the ISA is really very little impact on resulting performance. The total die space devoted to translating x86 instructions on a modern Nehalem is tiny compared to the rest of the chip. The only time the ISA decode logic matters if for very low power chips (smartphones). This is part of the reason why ARM is so far ahead of Intel's x86 offerings in that area.

      Modern x86, with SSE and x86-64, is actually not that bad of an ISA and there aren't too many ugly workarounds necessary anymore that justify a big push to change.

    18. Re:Why do they need to? by Anonymous Coward · · Score: 3, Informative

      We already have this. All current x86's have a decode unit to convert the x86 instructions to micro-ops in the native RISC instruction set.

    19. Re:Why do they need to? by Anonymous Coward · · Score: 0

      It's not just lipstick. These new chips are a whole new animal. Intel just has to dress up each new generation to look like a pig the software, but they run just as fast or faster than any other animal out there that looks more like what it is.

    20. Re:Why do they need to? by QuantumLeaper · · Score: 2, Informative

      Moore's Law has nothing to do with computing power, but with the NUMBER of transistors on a piece of silicon. Which he said would double every 2 years, which has be petty much true and will remain true for the next decade most likely.

    21. Re:Why do they need to? by cowscows · · Score: 1

      So basically you're saying that since whatever you move to will one day fall to obsolescence, you might as well stick with your current system that's already basically obsolete?

      --

      One time I threw a brick at a duck.

    22. Re:Why do they need to? by ultranova · · Score: 1

      At the extreme, maybe it might be time for a new CPU architecture? Intel has been doing so much stuff behind the scenes to keep the x86 architecture going, that it may be time to just bite the bullet and move to something that doesn't require as much translation?

      No, because then the new architecture will become obsolete in a few years, which is too little time for OS and programs to catch on. Meanwhile you have a huge amount of legacy software that needs to be emulated, and the emulation needs help from hardware to be fast enough, so you can as well keep the whole thing x86/x64 compatible.

      Besides, the real problem is not the x86 architecture, but the Von Neuman architecture that's already causing a huge bottleneck and will only get worse as the number of cores grows. Eventually, we have to let it go and move to some more scalable one; what that might be I have no idea.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    23. Re:Why do they need to? by quo_vadis · · Score: 4, Informative

      Um, actually Intel has done a lot of work on the architecture and microarchitecture of its processors. The CPUs Intel makes today are almost RISC like, with a tiny translation engine, which thanks to the shrinking size of transistors takes a trivial amount of die space. The cost of adding a translation unit is tiny, compared to the penalty of not being compatible with a vast majority of the software out there.

      Itanium was their clean room redesign, and look what happened to it. Outside HPCs and very niche applications, no one was willing to rewrite all their apps, and more importantly, wait for the compiler to mature on an architecture that was heavily dependent on the compiler to extract instruction level parallelism.

      All said, the current instruction set innovation is happening with the SSE, and VT instructions, where some really cool stuff is possible. There is something to be said for the choice of CISC architecture by Intel. In RISC ones, once you run out of opcodes, you are in pretty deep trouble. In CISC, you can keep adding them,making it possible to have binaries that can run unmodified on older generation chips, but able to take advantage of newer generation features when running on newer chips.

      --
      Legally obligatory sig : My opinions are my own... etc etc
    24. Re:Why do they need to? by Anonymous Coward · · Score: 0
      Haha... this is a correct and predictable response

      I also would have accepted:

      Sarah Palin, or

      A 40 year old pig

    25. Re:Why do they need to? by WuphonsReach · · Score: 3, Insightful

      Itanium failed because it used a VLIW architecture - great for specialized processing tasks on big machines but for general purpose computing (ie. what 99.9% of people do) it wasn't much faster than x86.

      Itanium failed - because it could not run x86 code at an acceptable speed. Which meant that if you wanted to switch over to Itanium, you had to start from scratch - rebuying every piece of software that you depended on, or getting new versions for Itanium.

      AMD's 64bit CPUs, on the other hand, were excellent at running older x86 code while also giving you the ability to code natively in 64bit for the future. AMD's method took the market by storm and Intel had to relent and produce a 64bit x86 CPU.

      (There were other reasons why Itanium failed - such as relying too much on compilers to produce optimal code, cost of the units due to being limited quantity, and Intel arrogance.)

      --
      Wolde you bothe eate your cake, and have your cake?
    26. Re:Why do they need to? by tedgyz · · Score: 1

      Itanium comes to mind here because it offers a dizzying amount of registers, both FPU and CPU available to programs.

      And it's been such a smashing success in comparison to x86, right?

      Just because it hasn't been a success does not diminish it's intent. The reason it has not been a success is because there has not been a compelling need to migrate to a new architecture. As long as Intel keeps the x86 train going, people will stay on board.

      I would compare it to the IPv4 to IPv6 migration. Who is going to jump on that bandwagon?

      --
      "No matter where you go, there you are." -- Buckaroo Banzai
    27. Re:Why do they need to? by BitZtream · · Score: 1

      doesn't require as much translation?

      The translation isn't going away until everyone starts writing in microcode directly for the specific core its running on.

      There will always be translation somewhere along the way, that is after all, what a compiler does, its just a single pass that doesnt' change from run to run.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    28. Re:Why do they need to? by cheesybagel · · Score: 1

      Why does it "need to be done"? The most successful computer architecture next to X86 is S/360 which was designed in 1964. S/360 is still used in mainframes today.The third most successful architecture, ARM, has 16 registers just like X86-64.

    29. Re:Why do they need to? by rgviza · · Score: 1

      Isn't Itanium EOL'd or soon will be? Microsoft and some linux distros have already sunsetted it from a OS standpoint.

      I agree though, x86 needs to die. We need to clean house and start over. It will suck but it needs to happen in order to move general purpose computing forward.

      --
      Don't kid yourself. It's the size of the regexp AND how you use it that counts.
    30. Re:Why do they need to? by Chris+Burke · · Score: 2, Informative

      Intel has been doing so much stuff behind the scenes to keep the x86 architecture going, that it may be time to just bite the bullet and move to something that doesn't require as much translation?

      Actually, the vast majority of what Intel and AMD have been doing behind the scenes are microarchitectural improvements that would be applicable to any out-of-order processor regardless of ISA.

      There are some minor penalties to x86 that remain, but getting rid of them would be a very modest performance upside and is completely not worth ditching backward compatibility for.

      Itanium comes to mind here because it offers a dizzying amount of registers, both FPU and CPU available to programs. To boot, it can emulate x86/amd64 instructions.

      You don't actually need that many architected registers, and modern out of order processors have a similar number of physical registers anyway. Sure IA32 had way too few GPRs, but most of the time the 32 registers of most RISC machines aren't used. x86-64 has a good compromise, and IA64 has overkill.

      If you're going to ditch x86 and start with something new -- and hypothetically I completely agree it would be great -- at least pick a real RISC architecture, and not something that actually has a bigger manual than x86. The only thing worse than an ISA designed by 30 years of engineering pragmatism is one designed by a committee of compiler writers. :P

      Emulation of x86 was something that was touted but never performed well enough to actually satisfy customers who wanted to run x86 workloads. This is surprising only to people who think x86 chips are inherently slow. :P

      Virtual machine technology is coming along rapidly. Why not combine a hardware hypervisor and other technology so we can transition to a CPU architecture that was designed in the past 10-20 years?

      Because virtual machines don't actually let you do that. They only virtualize a few aspects of the ISA to make compartmentalization possible. The guest OS and applications are compiled to the underlying ISA. Virtualization is all about efficiency, and emulating foreign instruction sets is inefficient.

      --

      The enemies of Democracy are
    31. Re:Why do they need to? by MaskedSlacker · · Score: 1

      I think the word you're looking for is prescribe, maybe?

    32. Re:Why do they need to? by CAIMLAS · · Score: 1

      Let's be fair, here: it's not just Intel that has kept x86 going.

      In no small part, AMD has done a hell of a lot in this department, and if it had been left up to Intel, x86 would be dead (or stagnant) by now, as both VT and x64 came from AMD first, only to be later used by Intel due to licenses. Before AMD started making outside-the-box renovations, Intel was falling fairly flat on improvements and moving strongly towards the refinement stage for things like power management (which is awesome and beneficial, but not what you necessarily want if you want a large machine to do work).

      Companies like Via (with their public key cryptography in-CPU on the C7) have also done a fair amount to make x86 relevant.

      Frankly, I'd love to see a different architecture spring up. It's probably not going to happen - they'll find a way to keep x86 alive and in the forefront because it's Good to have a single hardware platform for all tiers of the market (mainframe through mobile).

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    33. Re:Why do they need to? by rienafairefr · · Score: 1

      It's not a law, it's a empirical observation of the semiconductors market at the time. Since then it's been changed a bit, and also mainly served to get investors on board (look ! we can make stuff smaller/better/stronger twice as more every two years !) It's been a way to break the product cycle (a chip can last decades, no reason to buy a new version of something if it's not cheaper/more performant, roughly). Without some kind of moores law, you couldnt have more performant stuff every year with lower price. every company selling you electronics gadget would be very sad.

    34. Re:Why do they need to? by mandolin · · Score: 1

      Going offtopic, but another good thing about CISC is that you can optimize such that the most common instructions have the shortest instruction lengths possible. This slightly reduces the disc space and memory used by programs.

    35. Re:Why do they need to? by evilviper · · Score: 1

      Intel has been doing so much stuff behind the scenes to keep the x86 architecture going, that it may be time to just bite the bullet and move to something that doesn't require as much translation?

      The things which Intel has been doing to x86 are the same things you'd need to do for ANY processor to get that kind of speed. For all the hype about ARM, they still don't come close to the DMIPS/MHz of the slowest x86 CPU today. Just try to name one CPU architecture that would do better, and then explain why Intel can't just roll those features into any x86 CPU.

      Honestly, if any existed, they'd be able to take over at least a few niches pretty quick.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    36. Re:Why do they need to? by RightSaidFred99 · · Score: 1

      I agree though, x86 needs to die.

      Based on what? x86 processor performance has been exceptional. It's the best there is, beating everything in either performance, price/performance, or power/performance.

      Anti-x86 hysteria is pretty ridiculous in the face of the fact of how much performance Intel and AMD have been able to eke out of it. It mostly seems to boil down to the vague, nonsensical blathering of "well, we could have something somehow better", much like the baseless hysteria that Microsoft has single-handedly somehow set back the IT industry 80 years (yes, somehow 80 years).

    37. Re:Why do they need to? by Anonymous Coward · · Score: 0

      right, because we all know the NUMBER of transistors on a chip does not correlate well with it's computing power, we just put extra ones there because Mr. Moore told us to. After all, he was the boss, it's his laws. But he's gone now, can we just get back to developing some game cartridges for my C-128 now. The C-64 is SO damn slow!

    38. Re:Why do they need to? by OrangeCatholic · · Score: 1

      The Von Neumann bottleneck is sort of inevitable. A campfire might be able to eat more logs than you throw at it, but it's still the brightest place in the field. And let's say you throw all the logs at it, now you run out of logs and feel stupid the other way.

      Example, for all the times you've gotten 12fps in a game, how many times has your cpu idled at near zero? Like right now?

      One part is always going to be faster than another. Except when CPU's finally top out, and that will be interesting.

    39. Re:Why do they need to? by Anonymous Coward · · Score: 0

      architecture != ISA

    40. Re:Why do they need to? by TheTurtlesMoves · · Score: 1

      I was under the impression that ARM does pretty well in mobile devices compared to x86.

      --
      The Grey Goo disaster happened 3 billion years ago. This rock is covered in self replicating machines!
    41. Re:Why do they need to? by w0mprat · · Score: 1

      Is there actually still a pig under that large blob of lipstick?

      --
      After logging in slashdot still does not take you back to the page you were on. It's been that way for 20 years.
    42. Re:Why do they need to? by Anonymous Coward · · Score: 0

      While other ISAs can't claim the popularity of x86+SSE, they have provisions for instruction extensions, even RISC ones-- in effect, there isn't necessarily a limit to the number of instructions. Granted, this goes against the RISC philosophy, but there's no such thing as pure RISC or pure CISC anymore anyway-- each has borrowed ideas from the other to get performance the pure versions can't get.

      Besides, before we hit any practical limits on these other ISAs, they will have versions with 64-bit instructions, which will have enough room for all the instructions you want, and enough bits to specify a lot more registers.

    43. Re:Why do they need to? by imgod2u · · Score: 1

      In microprocessor design, "architecture" is generally the name for the instruction set, that is, what is software visible. When you speak about implementation details, that would be the "micro-architecture".

    44. Re:Why do they need to? by CAIMLAS · · Score: 1

      It does - except when using the latest Atom CPU core (moorestown, I think?), which has two cores in teh same TDP as a Snapdragon single core CPU. Yes, that's for the entire Atom SoC, not just the CPU.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    45. Re:Why do they need to? by renoX · · Score: 1

      >The cost of adding a translation unit is tiny, compared to the penalty of not being compatible with a vast majority of the software out there.

      Sure, but it also use some power and is probably a good explanation why x86 use more power than RISCs: their ISA is better: more compiler visible register, fewer obsolete instructions == smaller 'translation engine' and less power used.

  4. Depends on your definition of "chip" by cormander · · Score: 0

    Referencing science fiction, Star Trek's Voyager was the first ship to utilize bio-neuric computer technology. I imagine that the cells in the sacks are smaller than any chip that the Enterprise D had. I would consider the cells in Bio-neuric computer technology as "chips", and it exists in our brains. We just don't know yet how to harness it. So yes, smaller computer chips are possible.

    1. Re:Depends on your definition of "chip" by Anonymous Coward · · Score: 0

      Returning from lah-lah trekkie fuckwit land for a moment... the cells of your brain are not smaller than current processors.

    2. Re:Depends on your definition of "chip" by Anonymous Coward · · Score: 0

      Dork alert! Dork alert!

    3. Re:Depends on your definition of "chip" by QuantumLeaper · · Score: 1

      Very true, also the brain is very slow compared to a computer. A 4004 is faster than the brain, but the brain is wired differently.

    4. Re:Depends on your definition of "chip" by Kvasio · · Score: 1

      I assume you based your statement on timing of doing calculations.

      Brain is way faster, but optimised for other tasks than math.
      Every fraction of second human brain processes all data input from receptors from entire body with signals about temperature, pressure, pain. Plus semantics, so called thinking, etc. Plus live hi-res video and audio processing and interpretation. Plus body organ functions control. 4004 would such heavily ...

    5. Re:Depends on your definition of "chip" by petermgreen · · Score: 1

      IIRC the headline figures for ICs are "feature size", that is the size of the smallest feature. The size of a complete logic gate will be significiantly bigger than that and afaict neurons do a fair bit more than your typical logic gate.

      More importantly though the brain is packed in 3D. ICs still generally only have a single layer of transistors.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  5. Maybe we will start seeing more cores? by mlts · · Score: 1, Interesting

    I have a feeling that once doing smaller and smaller lines becomes prohibitive, we will see a return to either revving up the clock speed (if possible), or adding more cores per die. Maybe even adding more discrete CPUs, so a future motherboard may have multiple CPUs on it similar to how mid to upper range PCs ended up with multiple procs present around 2000-2001.

    There are always more ways to keep going with Moore's law if one item gets near exhausted.

    1. Re:Maybe we will start seeing more cores? by Anonymous Coward · · Score: 5, Funny

      You have an uncanny ability to predict the present!

    2. Re:Maybe we will start seeing more cores? by Anonymous Coward · · Score: 0

      >There are always more ways

      You are extremely short-sighted. Growth is exponential only at the very beginning of natural processes. Every process reaches a plateau, that's simply how the universe works.

    3. Re:Maybe we will start seeing more cores? by phantomfive · · Score: 4, Insightful

      It has always been about making it smaller. Clock speed was able to increase because the chips got smaller. We were able to add more cores per die because the chips got smaller. Moore's law is about size: it doesn't say computers will get faster, it says they will get smaller.

      What we are able to do with the smaller chips is what's changed. Raising the clock speed worked for years, and that is the best option, but because of physical problems, in the latest generations we weren't able to do that. So the next best thing is to add cores. Now the article is suggesting we may not even be able to do that anymore.

      I will tell you I've been reading articles like this for as long as I've known what a computer was, so if you're a betting man, you would do well to bet against this type of article every time you read it. But in theory it has to end somewhere, unless we learn how to make subatomic particles, which presumably is outside the reach of the research budget at Intel.

      --
      Qxe4
    4. Re:Maybe we will start seeing more cores? by Abcd1234 · · Score: 3, Insightful

      Well done, you've just described... today!

      And today, we already know the problem with this approach: most everyday problems aren't easily parallelizable. Yes, there are specific areas where the problems are sometimes embarrassingly parallel (some scientific/number crunching applications, graphics rendering, etc), but generally speaking, your average software problem is unfortunately very serial. As such, those multiple cores don't provide much benefit for any single task. So if you want to execute one of these problems faster, the only thing you can do is ramp up the clock rate.

    5. Re:Maybe we will start seeing more cores? by Anonymous Coward · · Score: 0

      There is no financial incentive to create scalable parallel processors. They would essentially be putting themselves out of business.

    6. Re:Maybe we will start seeing more cores? by natehoy · · Score: 1

      Hey, give him some credit, he did a better job than the Golf Ball at Disney, and his post doesn't cost $75 a day to read.

      --
      "This post contains words, known to the State of California to cause thought. Wash brain thoroughly after reading."
    7. Re:Maybe we will start seeing more cores? by PRMan · · Score: 0, Troll

      And yet, when I run a batch file running all single threaded programs on Windows 7, it somehow uses both CPUs nearly identically, no parallel code required (in the programs themselves).

      --
      Peter predicted that you would "deliberately forget" creation 2000 years ago...
    8. Re:Maybe we will start seeing more cores? by Abcd1234 · · Score: 2, Insightful

      Trust me, what you're seeing is *not* what you think you're seeing. Windows isn't magically auto-parallelizing your code. That's a hot topic of research today, and it's really fucking hard.

    9. Re:Maybe we will start seeing more cores? by Chris+Burke · · Score: 1

      So if you want to execute one of these problems faster, the only thing you can do is ramp up the clock rate.

      The only thing you can do is increase single-thread performance, which isn't just about clock rate.

      --

      The enemies of Democracy are
    10. Re:Maybe we will start seeing more cores? by Abcd1234 · · Score: 1

      The only thing you can do is increase single-thread performance

      That's what I said. What part of "serial" don't you understand? If you're running multiple threads to achieve a job, you're doing that job in parallel.

      which isn't just about clock rate.

      Absolutely, it's also about cache performance, instruction pipelining, etc. But multicore *does not help*. At best, it could improve cache performance, as you could dedicate a single CPU to a single job, thus reducing cache contention between tasks.

    11. Re:Maybe we will start seeing more cores? by hitmark · · Score: 2, Interesting

      another problem is that adding cores is not as effective, right now, as upping clock speed.

      this may change however if the designs change from multiple universal cores to something more like a the cell cpu that powers the playstation 3, or maybe something like the the latest GPUs. Basically, a couple of universal cores like before (as they provide some benefit, if the os do a proper job in spreading processes across them) combined with multiple simpler cores that can be arranged like a assembly line. Then you stuff data in at one end, have each core do it assigned task in the chain, and have the result come out the other. With enough of them, one start to approach something like FPGA, giving each logical instruction in a program its own core.

      This is interesting in that a recent presentation i found the video of, stated that cpus these days slowed down mostly because it needed something from cache (usually because of a bad speculation during a IF or similar divergent routes in the code).

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    12. Re:Maybe we will start seeing more cores? by hitmark · · Score: 1

      question is, was one of the programs dependent on data coming from one or more of the others?

      if not, then the scheduler could multitask them easily. Something any computer have been able to do since the 90s at least.

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    13. Re:Maybe we will start seeing more cores? by Chris+Burke · · Score: 1

      That's what I said. What part of "serial" don't you understand?

      No, you said "the only thing you can do is increase clock rate", which is wrong. But because I did in fact understand your usage of "serial", I was able to make the proper correction.

      Absolutely, it's also about cache performance, instruction pipelining, etc.

      Well then don't say the only thing you can do is increase clock rate if you know that's not true. ;)

      But multicore *does not help*. At best, it could improve cache performance, as you could dedicate a single CPU to a single job, thus reducing cache contention between tasks.

      Yes, I was implicitly agreeing with you there. However if you do have multiple tasks such that cache contention exists, then you actually are going to benefit from multicore. Only in the case where there is only one task and there is completely negligble amount of interference from the OS timer interrupt routine etc is it not helpful. Which still represents a significant class of workloads, so the point your were trying to make stands.

      --

      The enemies of Democracy are
    14. Re:Maybe we will start seeing more cores? by Anonymous Coward · · Score: 0

      Windows is bouncing your process between cores when it schedules it. This is common on laptops as a heat mitigation technique.

    15. Re:Maybe we will start seeing more cores? by Anonymous Coward · · Score: 0

      I am sorry, but from personal experience I completely disagree. Nearly every software problem I have ever dealt with is composed of several small serial parts (input and output), and some kind of loop or set operation. Almost all of them could be written as some sort of map-reduce problem (read parallel). The only issue with making these implementations parallel is that the overhead of doing so makes the problem slower for any problem below a certain size.

    16. Re:Maybe we will start seeing more cores? by RockModeNick · · Score: 1

      A friend of mine once told me nearly this exact same thing when I called him and asked what's up: "I have a feeling that once doing smaller and smaller lines becomes prohibitive," Only when he said it, the rest of the sentence was "I'm just going to have to suck it up and buy some more coke."

  6. I miss the pressure AMD used to put on Intel by xxxJonBoyxxx · · Score: 1

    I miss the pressure AMD used to put on Intel. When Intel had an agile competitor often leaping ahead of it chip speeds shot up like a rocket - seems like they've been resting on their laurels lately...

    1. Re:I miss the pressure AMD used to put on Intel by localman57 · · Score: 1

      Really? I got a Core i5-750 in January, and I have been happier with it for the money than any chip I've ever had.

    2. Re:I miss the pressure AMD used to put on Intel by Revotron · · Score: 5, Insightful

      The latest revision of my Phenom II X4 disagrees with you. The Phenom II series is absolutely steamrolling over every other Intel product in its price range.

      Hint: Notice I said "in its price range." Because not everyone prefers spending $1300 on a CPU that's marginally better than one at $600. It seems like Intel has stepped away from the "chip speed" game and stepped right into "ludicrously expensive".

    3. Re:I miss the pressure AMD used to put on Intel by Lunix+Nutcase · · Score: 2, Interesting

      The only Intel chips that are $1000+ are those that are either a few months old and/or are of the "Extreme" series. The core i7-860s and 930s are under 300 bucks and pretty much the entire core i5 line is at 200 or less.

    4. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      So you haven't really done any research there? Intel's i5 750 and 760 "steamroll" all the Phenom II X4 CPUs in the price range. Don't trust me, trust benchmarks.

      --
      U+F8FF
    5. Re:I miss the pressure AMD used to put on Intel by PitaBred · · Score: 1

      The problem is that the Intel motherboards are more expensive, and they lock you into your chip "class". You can't upgrade to an i7 from an i5 in some cases.

    6. Re:I miss the pressure AMD used to put on Intel by Anonymous Coward · · Score: 0

      Depends on the task. Some friends and I make videos and I encode the result to AVCHD using x264. At that the Core i7 is 50% faster than a Phenom II at the same clock speed. If it weren't for the video encoding I'd definitely buy AMD, but when I bought my current PC in January the Core i7 860 was an obvious choice since I got a lot of extra performance for a little extra money and today it's as fast as an equally clocked Phenom II X6.

    7. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      The price difference is negligible between AMD and Intel boards, unless you are attending the race to bottom, where AMD rules. You also can't upgrade from an AM2 to AM3 CPU on a AM2 board. The talk about upgrading is meaningless in a broader sense too: Why would you buy something not optimal just so that you can upgrade it later? It's false economy, get the best you can afford now, and a whole new rig with whole new tech a few years later.

      --
      U+F8FF
    8. Re:I miss the pressure AMD used to put on Intel by Rockoon · · Score: 4, Informative

      What are you talking about? AM2 boards support AM3 chips.

      You also present a false dichotomy, because upgrading isnt ONLY about buying suboptimal hardware and then upgrading it later. Anyone who purchased bleeding edge AM2 gear when it was introduced can get a bios update and then socket an AM3 Phenom II chip. They still only have DDR2, but amazingly Phenom II's support both DDR2 on AM2 and DDR3 on AM3.

      So that guy who purchased a dual-core AM2 Phenom when they were cutting edge can now socket a hexa-core AM3 Phenom II.

      Its amazing what designing for the future gives your customers. Intel users have only rarely had the chance to substantially upgrade CPU's.

      --
      "His name was James Damore."
    9. Re:I miss the pressure AMD used to put on Intel by Rockoon · · Score: 1

      So you haven't really done any research there? Intel's i5 750 and 760 "steamroll" all the Phenom II X4 CPUs in the price range. Don't trust me, trust benchmarks.

      Phenom II X6 chips with Turbo Core in the same price range would like to have a word with you about you cherry picking old X4 chips.

      --
      "His name was James Damore."
    10. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      You probably mean AM2+ boards. All AM2 boards definitely don't support AM3 CPUs, feel free to check the manufacturer sites.

      For the false dichotomy part, you build up another in your case, too. In the last few years (AM2 and AM3 age), the quad cores haven't been too expensive compared to the dual cores. Your example user has made the wrong choice when buying the dual core in the first place; the combined price of the dual and the hexa core CPUs would have given him/her a nice time in multithreaded apps for the whole duration.

      --
      U+F8FF
    11. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      In what uses? X6 CPUs don't really deliver compared to i5, except in uses where you can really blast out all the cores, like vid encoding with certain programs.

      And the OP especially was telling how his/her *Phenom II X4* beats everything Intel has to offer in its price range, which is blatantly false. LTR.

      --
      U+F8FF
    12. Re:I miss the pressure AMD used to put on Intel by Anonymous Coward · · Score: 0

      [quote]You also can't upgrade from an AM2 to AM3 CPU on a AM2 board.[/quote]
      You can -- so long as the board BIOS is properly updated, which many respectable board manufacturer do. For example, my AM2 (not AM2+) board from 2006 I bought with AthlonX2 3600+ had no problem with last year's Phenom-II X3 720. You just need to upgrade to the latest BIOS and make sure it supports the AM3 CPU you are upgrading to.

      The board vendor homepage should have CPU compatibility list for all boards and which version of BIOS you need for each CPU supported.

    13. Re:I miss the pressure AMD used to put on Intel by Anonymous Coward · · Score: 0

      I don't know about this...My last 2 phenom ii purchases were x4 940's at $108 shipped....what at ~ $110 from intel steamrolls this?

    14. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      So, how do you define "price range"? Is that the exact price?

      --
      U+F8FF
    15. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      Sorry, like I later mentioned, it's board-specific. Care to give the board model?

      --
      U+F8FF
    16. Re:I miss the pressure AMD used to put on Intel by Nadaka · · Score: 1

      Wrong again. The PII x4 955 is in the ~$150 price range, the i5 750 is in the $200 price range. The 750 is a bit faster, but it is 25% more expensive for less than 25% more performance.

      The latest generation of AMD chips also has adaptive clock speeds to improve performance on monolithic tasks, soon that will be available on the x4 chips as well as the x6.

      I am not going to argue that AMD chips are absolutely better, but in terms of price/performance they have very little competition from Intel. The i5 750 and i7 920 being the only real competition on price/performance.

    17. Re:I miss the pressure AMD used to put on Intel by Anonymous Coward · · Score: 0

      Well, according to cpubenchmarks.net the X4 965 is slightly better than the i5 750 but slightly worse than the i5 760, but is $20 less than the i5 750 and $30 less than the i5 760.

    18. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      "The 750 is a bit faster, but it is 25% more expensive for less than 25% more performance."

      Please show relevant benchmarks. I've done a lot of research on this, and i5 750 is a lot faster in pretty much everything else than gaming, where they are more or less equal (GPU performance is more important there).

      "The latest generation of AMD chips also has adaptive clock speeds to improve performance on monolithic tasks, soon that will be available on the x4 chips as well as the x6."

      And Intel's new chips use very aggressive load balancing with the new quads: For example, on a basically single-threaded load on one core the core is actually overclocked to get more speed. Both manufacturers have good tech in place, ATM Intel's seems better to me, according to benchies.

      Don't get me wrong, I don't advocate buying Intel just by the brand, either. It's all about the uses and budget; my budget at the moment would mean an AMD Athlon II X3 with nVidia GTX 460 1 Gb, as my main uses are gaming and programming. If I could raise my budget a notch, it'd be i5 760 with the same graphics card. Of course, I'm from Europe, so the price difference between i5 quads and Phenom II X4s is a lot less than let's say Newegg's prices in the USA.

      --
      U+F8FF
    19. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      Sorry, I meant *real world benchmarks*. Try Tom's Hardware for starters. Synthetic benchmarks just show how well the CPU is optimized for that benchmark; a benchie measuring encoding time for a certain vid with a program is whole different issue.

      --
      U+F8FF
    20. Re:I miss the pressure AMD used to put on Intel by 0123456 · · Score: 1

      So that guy who purchased a dual-core AM2 Phenom when they were cutting edge can now socket a hexa-core AM3 Phenom II.

      So you buy AMD's most expensive CPU and cripple it by sticking it on an antiquated board with slow memory. Makes perfect sense to me.

      Also, I've read that one of the reasons Phenom is slower than Intel's i-series CPUs is because having to support DDR2 as well as DDR3 slows down the memory controller.

    21. Re:I miss the pressure AMD used to put on Intel by tibman · · Score: 1

      I typically do the thing you just described people shouldn't do. Go highend for Mobo and low/middle for amount of RAM and graphics card. CPU is usually middle end. Then two years down the road i can double the ram and drop in a new vid card. If the computer gets around 3-4 years old, it probably needs a new powersupply. For some reason the PS blows around the 4 year mark.

      The new computer was primarily built because my older one didn't have the CPU extensions that games need these days, like SSE2. The newer computer is very nice, i have yet to be beaten into a L4D2 game (other than the first round where everyone must load together). Total price was ~950$ with lots of room to expand later (like that sexy 1090T).

      If i buy a whole new computer every two years, i'd end up with a pile of sub-optimal machines. But if i keep my machine upgraded, i can get a lot more life out of the machine and retire it when it can't be upgraded anymore. A few months ago i put an AMD HD 4650 into and older AthlonXP box (no PCIe, no sata, AGP 8x, single core proc at 2.2GHz). Plays L4D2 great. That $90 took a machine out of the closet and onto a desk where guests can play online.

      The way i look at, you can pay ridiculous prices for a box upfront.. or upgrade it as prices drop and resource demand increases. I prefer the upgrade option. It keeps me looking at computer parts too. If you don't stay on top of that stuff.. in two years you won't know what's worth a damn. It's also a great excuse to get into the case and clean it out a twice a year.

      --
      http://soylentnews.org/~tibman
    22. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      Interesting... Why the high-end mobo? Those cost substantially more than mid-range. For the other parts, your upgrade path is pretty much what I have been recommending too for those who want to do some upgrades: Don't upgrade the CPU, it's waste of money. If RAM is cheap at the moment, buy a bit more than you really need, otherwise buy more when it's cheaper (RAM prices at the moment are outrageous in Europe).

      I'm not sure where you got that 2 years figure though, as my current comp is 4 years old and just about to be replaced, it was high-mid-range when I bought it (so not too expensive, and bang-for-the-buck is good), and the upgrades have been a new HDD and going for 2 extra Gb of RAM (because I need to use Windows 7 for Visual Studio work now, and naturally I used it for some gaming too, alongside with my original Ubuntu+Wine setup).

      Your last paragraph is rather rephrasing common sense. Don't buy the latest stuff, as there's always a premium there. Wait a while, and the prices come down.

      --
      U+F8FF
    23. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      Ah, forgot to ask about the PSUs you are using... I've had a cheap one breaking down everything including the floppy drive in my comp, so after that I've only bought good PSUs from brands like Corsair, Cooler Master, and OCZ. No aging problems there, really (and that includes many many more comps than I've owned, as I've build for other people, too).

      --
      U+F8FF
    24. Re:I miss the pressure AMD used to put on Intel by xMilkmanDanx · · Score: 1

      Does that mean they're going at ludicrous speed?

    25. Re:I miss the pressure AMD used to put on Intel by Raenex · · Score: 1

      Total price was ~950$

      Which is pretty expensive for a computer these days. I recently built one from Newegg parts about six months ago for around $200 (motherboard, cpu, ram, case, and power supply). I don't use it for games, so I rely on the integrated graphics, but I could always throw in a cheap "last-gen" card if I wanted to, and still come nowhere near your price.

    26. Re:I miss the pressure AMD used to put on Intel by Chris+Burke · · Score: 1

      Why would you buy something not optimal just so that you can upgrade it later? It's false economy, get the best you can afford now, and a whole new rig with whole new tech a few years later.

      Why wouldn't you buy something optimal (which to me means the highest performance before the price for incremental performance increases drastically at the high end), and then upgrade it with something better later?

      I have an AM2+ board today, I plan on upgrading to an AM3 processor soon, and since the motherboard itself is not a significant performance limiter and the incremental price for DDR3 is too much in my estimation, I'm not actually losing anything significant and saving a lot of money.

      Also, in the broader sense beyond us enthusiasts, socket compatability and upgradability is a huge deal for OEMs. Being able to refresh a line with a new processor has many advantages.

      --

      The enemies of Democracy are
    27. Re:I miss the pressure AMD used to put on Intel by Revotron · · Score: 1

      I bought all my parts from Newegg in the US, hence I noticed a much larger price difference between the Phenom II and Intel's i5/i7 lineup.

      I'm also not advocating buying CPUs on budget alone - if you need the performance, then by all means pay a little extra for it. But what I fail to see in looking at the processors side-by-side is the price/performance. I don't see any sense in paying 8x more for a CPU that only runs at about 2x the speed.

    28. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      That's because the price you'll pay for two CPU is more than just getting a good one that'll carry you through the period. And you are limiting yourself to old tech: Who knows when AMD introduced AM4 socket, which is not backwards-compatible?

      --
      U+F8FF
    29. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      Ah, again I must apologize in this thread... Finnish Ultimate fighting tournament finals on TV, and a bit drunken wife on the phone...

      Apart from the obvious typos in the proper reply, I was "burned" by AMD socket 939. It didn't matter for me, as like I've said, I don't build computers for that upgradeability. I feel sorry for a couple for a couple of my mates who did the worse mistake by buying socket 754, which was pretty much dead once it was introduced. The lesson learned: Do not trust any platform to be for upgrades in the next two years.

      --
      U+F8FF
    30. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      Yes, the US is a bit different compared to Europe. Still, you might show some substantiation for those 2X performance vs. 8X prices.

      --
      U+F8FF
    31. Re:I miss the pressure AMD used to put on Intel by Anonymous Coward · · Score: 0

      AMD still puts the pressure on Intel. What does Intel even have to compete with Athlon II? If you build a (not super) cheap machine, it has an AMD CPU. I wonder how many people look at $200 Intel chips and then decide, "fuck it, an Athlon II is totally good enough for this job." And if you go down from there, the Atom comes into play.

      If you're build in the mid-range, the Core i5 and Phenom are still leap-frogging each other and the brand you pick this month might not be the same as what you picked last month. It's only up at the top (Core I7 vs Opteron) where Intel has had the chance to catch their breath .. and actually their CPUs up there are still improving so maybe they know something about the next Opteron that we don't.

      I just can't figure out what you're talking about; the competition is still vicious and expanded capabilities are still coming out. Intel just joined VIA in the crypto club, and when AMD joins (they'll have to, now) then Intel is going to have to make their stuff good. We're talking about features only about a year old (maybe less now that I think of it) and you say Intel is resting? This is a great time to buy a computer; the only better time is the future.

    32. Re:I miss the pressure AMD used to put on Intel by Chris+Burke · · Score: 1

      That's because the price you'll pay for two CPU is more than just getting a good one that'll carry you through the period.

      Um, the whole point is that extra price you pay for that "good" CPU is disproportionate to the amount of performance. The performance delta between that highest-performing chip and the optimally priced chip (which is still quite good) is much smaller than the performance delta between that highest-performing chip and the optimally priced chip of 2 years later.

      So you're paying a lot more for a negligible amount of increased longevity. You're not saving anything. You're paying more to have the best in the short term. If you want to do that -- and I've done it in the past -- then that's great, but don't kid yourself that it's more economical to do so.

      Who knows when AMD introduced AM4 socket, which is not backwards-compatible?

      Assuming it isn't, then all I've lost is a small percentage of performance in return for paying substantially less. Assuming it is, I can weigh the cost/performance advantage of switching to a new mobo and buying new RAM vs upgrading my existing system with the next generation of processor.

      Paraphrasing the other post:
      754/939 didn't last very long

      Yeah, AMD had problems getting their socket roadmap straight when they transition to K8. On the other hand, Socket A was around forever and I got many nice upgrades out of it. And once again they seem to have learned that socket compatibility is a good feature to have, partly because of the beating they took (from OEMs and enthusiasts) over the their socket problems.

      --

      The enemies of Democracy are
    33. Re:I miss the pressure AMD used to put on Intel by Cajun+Hell · · Score: 1

      X6 CPUs don't really deliver compared to i5, except in uses where you can really blast out all the cores, like vid encoding with certain programs.

      If you're not "blasting out all the cores" then you're not shopping for Phenoms or i5s anyway; you're shopping for Atoms or Semprons, or maybe Athlon IIs or i3s.

      What a dumb thing to say: "the Phenom X6 doesn't compete with the i5 because the Phenom is more powerful than what you need." I think it's doubly-ironic to make that kind of argument in favor of the guys who actually have hyperthreading, something my AMD e-peen misses.

      --
      "Believe me!" -- Donald Trump
    34. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      Blast out 6 cores has a lot different meaning than blasting out 4 cores. Please check out the tech Intel has in place to deliver good performance for a single-threaded app (overclocking the core on which the thread is running on). You build a straw man there: I never claimed that more cores would be worse if more cores would be needed, and neither did I claim that less cores is better if all the rest is the same. For your supposed quote about X6 vs. i5 vs. Phenom, I never said anything like that, another straw man. LTR.

      --
      U+F8FF
    35. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      Very good points. If you can follow me without quotes, I'll try to address them linearly:

      1. This point about the price /delta/ (nice word, I've never used it in this context) has been put to the past by the current pricing schemes. You don't pay much extra for a quad vs. a similar dual core (architectures and all in the equation). Do the math (I have done), and you'll end up in the negative side, if you go for something that you are really planning to upgrade in 2 years.

      2. Very well, that's the kind of math I've been doing for other people too for some years now. AM3 was outdated when it was introduced, because if you really want to get the best out of a new CPU architecture, you better make a socket that can match it for the best. Hence the two new sockets from Intel in a short time, after we thought that LGA 775 was never going to go away.

      3. Repetition of 2, but AMD must know that the next bigger step ("tock" in Intel's language) must mean a big change in the architecture. They can keep the next generation of CPUs compatible with the older boards, but that hampers the innovations they can make in the designs, and thus it probably lowers the performance. I don't trust either of the CPU manufacturers to stay on their PR-published road maps after a year or two, and thus I plan my builds so that I can get most of them out in the period they are supposed to deliver (for example) gaming performance for me, and then they are retired for other tasks.

      As a side note, I too loved Socket A, with my water-cooled Athlon M 2500+ running at 3 GHz just fine :)

      --
      U+F8FF
    36. Re:I miss the pressure AMD used to put on Intel by CAIMLAS · · Score: 1

      "Race to the bottom"?

      Feature for feature, you can find an AMD AM3 board for significantly less than an Intel board - often, the boards have more features (more SATA ports, for instance).

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    37. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      [citation needed]

      --
      U+F8FF
    38. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      Yeah, I agree. Whoever modded up the GP doesn't know a thing about the issue.

      --
      U+F8FF
    39. Re:I miss the pressure AMD used to put on Intel by Revotron · · Score: 2, Informative

      This review:
      http://it-review.net/article/hardware/cpu/Intel_Core_i7_980X,_Core_i5_650_and_Core_i3_530_review&3

      These processors:

      Core i7-980X
      http://www.newegg.com/Product/Product.aspx?Item=N82E16819115223

      Core i5-650
      http://www.newegg.com/Product/Product.aspx?Item=N82E16819115220

      Core i3-530
      http://www.newegg.com/Product/Product.aspx?Item=N82E16819115222

      Notice the performance of the 980X over the other two. There's no more than a 3x performance increase in media encoding. Compare the price tag differences, ranging from a six-fold increase over the i5 and an eight-fold increase over the i3.

      The kind of premium Intel charges for the "Extreme Edition" brand is ridiculous. Based on those specs alone and knowing the price of the two lower models, I wouldn't expect to be charged anything more than $600 for the i7.

    40. Re:I miss the pressure AMD used to put on Intel by Revotron · · Score: 1

      Legal disclaimer: My comments on performance are based on the assumption that the reviewers were utilizing all cores in the benchmark, and not running single-threaded benchmarks or locking out unused cores. The reviewers did not adequately explain the benchmarking procedures, so there's definitely some wiggle room for disagreement.

    41. Re:I miss the pressure AMD used to put on Intel by Chris+Burke · · Score: 1

      1. This point about the price /delta/ (nice word, I've never used it in this context) has been put to the past by the current pricing schemes. You don't pay much extra for a quad vs. a similar dual core (architectures and all in the equation).

      If this discussion was solely in the context of buying a dual-core processor instead of a quad-core, sorry, I missed it. Had I realized, I would have explicitly rejected that dichotomy. :)

      I was talking about actually finding the optimal price-point, graphing price/performance, and finding the farthest point on the performance axis before the slope of the line significantly increases indicating that you're getting very little return on your extra money. That math is still very relevant. And sure, it's going to point you at a quad-core processor today. But not the fastest one.

      Of course the funny thing is, I personally bought a dual-core processor when quad-cores didn't exist, and then I bought a quad-core and plugged it into the same board, saving a lot of scratch vs having to buy a new mobo. Go upgradability, huzzah!

      2. Very well, that's the kind of math I've been doing for other people too for some years now. AM3 was outdated when it was introduced, because if you really want to get the best out of a new CPU architecture, you better make a socket that can match it for the best. Hence the two new sockets from Intel in a short time, after we thought that LGA 775 was never going to go away.

      Ha, AM3 is hardly outdated, it's quite well suited to AMD's architecture. Intel had to switch away from 775, they completely changed their bus architecture -- to one very similar to AMD's. Which is why Intel had to change sockets in a necessarily non-compatible way, and AMD hasn't.

      3. Repetition of 2, but AMD must know that the next bigger step ("tock" in Intel's language) must mean a big change in the architecture. They can keep the next generation of CPUs compatible with the older boards, but that hampers the innovations they can make in the designs, and thus it probably lowers the performance.

      "Tocks" aren't necessarily big architectural changes necessitating a new platforms. They just aren't simply process shrinks. It's several iterations of tick-tock between major architectural revisions. AMD doesn't follow that pattern anyway.

      AMD is of course coming out with a major new architecture in the next few years, but (especially since current/power draws are now constrained by market segment so they're unlikely to get into a P4-like situation where they have to redesign the socket just to reduce power pin inductance) the major things choice of socket restricts are the external interfaces. So if they want to add more DRAM channels, or bridgeless PCIe, that'll require a new socket. However it's not difficult at all to fit that same processor into a socket that doesn't have those things. Which is what I'm betting you'll see -- processors for the new socket, and for the old.

      And then it'll be up to the consumer if it's worth getting the benefit of the new socket or not.

      --

      The enemies of Democracy are
    42. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      Yeah, and you just chose the CPUs no-one in the "know" would buy. 980X is for the AnalWare and equivalent horrendously overpriced prebuilts and the few stupid people they can snare just by being the fastest around here (which is probably true); i5 and i3 dual cores can't compete with AMD's offerings.

      Can we go back to i5 quads vs Phenom II X4?

      --
      U+F8FF
    43. Re:I miss the pressure AMD used to put on Intel by Anonymous Coward · · Score: 0

      have fun throwing out your current MB, CPU and RAM when intel releases their next semiannual LGA update, now with faster gigahertz! us AMD users will just drop the newest AMD processor into the standardized PGA socket and save hundreds over Intel's planned-obsolescence hardware.

    44. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      Hmm-ho, again thanks for the reply. I'll again address your points by numbering.

      1. Good for you. Did you really need the quad core? What are you using the computer for? Did you forget the longevity of LGA 775, where you can still do the same thing? Doesn't make sense to me, but CPUs are readily available.

      2. I'd suggest taking a hard look at CPU architecture development. By a friend, I happen to know something about it, and the pin layout (corresponding to power and data ports) is actually very important. If you don't think that AM3 was outdated when it came out, I'd suggest doing some research. This is not meant to offensive in any way, the CPU design just means that the pin layout has to live with the optimal physical construction.

      3. Your latter point about AMD's big change strikes true to me too, but as a solid-state physicist, I recognize the realities. AM3 is old now, and going past it requires changing the socket, or hampering the real performance just to be backwards-compatible.

      For your musings, Intel already made the thing, and it got good acceptance.

      Again, I'm not an Intel buff by any means, but as a computer building enthusiast, IMO they have been taking the more sensible way, dropping old crud and pushing aggressively forward.

      --
      U+F8FF
    45. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      Have fun lagging behind, AC!! LOL!!1!

      --
      U+F8FF
    46. Re:I miss the pressure AMD used to put on Intel by Revotron · · Score: 2, Informative

      You asked me to provide evidence supporting my claim of 2x performance gains and 8x the pricetag. I did exactly that. AMD and Intel may be in a tight race at the midrange ($140-$200) but the interoperability between AMD's three socket specs (AM2,AM2+,AM3) and the DDR2/DDR3 backwards compatability are what send AMD leaps and bounds ahead of Intel. From a holistic standpoint AMD's offering is alot more stable in the long-term, and this is how they steamroll over the competition.

      P.S. I got fed up with Intel when I found out I'd have to throw out my motherboard, CPU and RAM to move from a Core2 Quad to *any* of the i3/5/7 offerings. My motherboard, CPU and RAM were no more than two years old and yet somehow there was no financially sane upgrade path for ANY of the components. If I were to get an i3 or i5, that meant I most likely couldn't upgrade to an i7 later without chucking the entire motherboard. This is what ticks me off about Intel's business model.

    47. Re:I miss the pressure AMD used to put on Intel by amazeofdeath · · Score: 1

      So, do we get Phenom II X4 955 vs Intel i5 750 here?

      --
      U+F8FF
    48. Re:I miss the pressure AMD used to put on Intel by 5pp000 · · Score: 1

      Intel users have only rarely had the chance to substantially upgrade CPU's.

      Say what?? LGA775 was around for a loooong time (Pentium 4 through Core 2). I could put a 45nm chip in my LGA775 box; meanwhile my Socket 940 box is maxed out with a pair of 90nm Opteron 290s.

      I'm glad AMD set up a better upgrade path for AM2, but they really abandoned 940 users.

      --
      Your god may be dead, but mine aren't!
    49. Re:I miss the pressure AMD used to put on Intel by PitaBred · · Score: 1

      You buy a nice mobo because EVERYTHING else depends on it working right. Your machine will be faster, more stable, and more reliable with a proper motherboard that doesn't have quirks. You don't have to go gonzo, but never get the cheapest one you can find.

    50. Re:I miss the pressure AMD used to put on Intel by tibman · · Score: 1

      yeah! Hobobuild man. I support all builders of hobo boxen.. better than an emachine from walmart of something. I apologize.. drinking atm. But you are right.. that ~9%0$ machine was for gaming

      --
      http://soylentnews.org/~tibman
    51. Re:I miss the pressure AMD used to put on Intel by FlyHelicopters · · Score: 1

      You assume your time has no value in your calculations... The price of the Intel chips is cheap if you're using that raw power for a living, and you value your time almost anything north of zero.

    52. Re:I miss the pressure AMD used to put on Intel by Kjella · · Score: 1

      P.S. I got fed up with Intel when I found out I'd have to throw out my motherboard, CPU and RAM to move from a Core2 Quad to *any* of the i3/5/7 offerings. My motherboard, CPU and RAM were no more than two years old and yet somehow there was no financially sane upgrade path for ANY of the components.

      True. But is there one particular component there you really feel needs upgrading? More RAM you probably could add unless you're already maxed, motherboards haven't changed much. I suppose there's the new hex-core processors but the difference between a Core2 quad and i7 quad aren't enough to justify the CPU price I'd say. Or are you just on a two year upgrade cycle out of habit? I'd say that's way too early, then you underbought on your original purchase.

      Yes, you can put a AMD hex-core on your old AM2 board that used to house a dual core, but what's the memory penalty going to be like? I haven't seen a single benchmark site that's bothered to test the combination, that it works doesn't always equate to making sense. Over the years I have made exactly one CPU upgrade, from a Duron 700 to Athlon 1200. I suppose if I hadn't switched from AMD to an Intel Q6600 (because AMD had no quad offering at the time) there could be a second time, but... In most cases, by the time performance sucked so bad I wanted to upgrade too much had changed.

      --
      Live today, because you never know what tomorrow brings
    53. Re:I miss the pressure AMD used to put on Intel by Rockoon · · Score: 1

      For one thing, low end motherboards SUCK REALLY BADLY. You are essentially LUCKY if you get a $50 Motherboard that doesnt have quirky issues or downright failures.

      Also there is the feature-issue. My latest MoBo purchase included USB 3.0 and SATA 3.0 even though I strictly have no need for such things yet. This forward thinking means that when I finally pick up a high performance SSD, I am not going to be stuck choosing from or settle for the lower 3Gbit tier.

      MSI makes some quality boards in the $100 range (find their "Military Grade" lines), and ASUS makes some quality ones in the $125 range. I can't really comment on the others.

      I wish Soyo was still around making motherboard. They made some really good ones in the $50 range.. but perhaps thats why they went bankrupt.

      --
      "His name was James Damore."
    54. Re:I miss the pressure AMD used to put on Intel by sznupi · · Score: 1

      Accidentally, video encoding is pretty much the only semi-common task left where you want as much processing power as possible (within the constraints of given budget of course)

      --
      One that hath name thou can not otter
    55. Re:I miss the pressure AMD used to put on Intel by sznupi · · Score: 1

      The memory penalty argument can't really stand to much scrutiny - if it were such a big deal / making the whole thing not worthwile, there would be no point in buying new 6-core CPU vs. a new 2-core one, on a completelly "pristine" build, which slashes the bandwith per core by 3 already.

      --
      One that hath name thou can not otter
    56. Re:I miss the pressure AMD used to put on Intel by sznupi · · Score: 1

      Practically certain with popular boards (easy with "price search" services, they typically let you sort product categories by popularity) from big manufacturers; the ones which were always better to buy anyway.

      --
      One that hath name thou can not otter
    57. Re:I miss the pressure AMD used to put on Intel by sznupi · · Score: 1

      Yeah, for a long time...and with incompatible (but mechanically identical...) versions. Go ahead, try and put some Core arch CPU into P4 era motherboard.

      And 940 was mostly a server socket, a bit different realities.

      --
      One that hath name thou can not otter
    58. Re:I miss the pressure AMD used to put on Intel by sznupi · · Score: 1

      Hm, I guess one PC of my buddy, with AM2 board, apparently running for a few months with Phenom II X4, is some damn good practical joke, eh?

      And n-cores have prices pretty much determined via "multiply the price of one core in a dualcore CPU of similar clockspeed", and only for around a year, that's not what most of the world would call "not too expensive" even now, nvm "in the last few years"...
      Seriously, via what twists do you justify that buying something nice, but with an option of easily and inexpensively getting something much nicer (like...a CPUs which don't even exist now - cheap quadcore -> cheap octacore will be a nice upgrade, and at time when software will better utilise is), is "the wrong choice"?

      --
      One that hath name thou can not otter
    59. Re:I miss the pressure AMD used to put on Intel by sznupi · · Score: 1

      Negligible? Just by glancing at catalogue here (FYI, also in Europe...) - sure, the bottom of the line boards are pretty much the same, but even at this pricepoint AMD gives notably better overall performance; when moving slightly higher, AMD oferrings start to destroy Intel ones thanks to much better GFX at this point. For somewhat comparable GFX from Intel (in i-series), the price increase becomes much more notable / 2x from the level at which we started (funny, weren't motherboards supposed to be cheaper now that GFX is in the CPU?)

      Your talk, like that, about "race to bottom" or "why not trash what you have by the next upgrade?" is almost ingrate - sure, might not matter much to priviledged you, but matters to the world at large. There's somewhat more than 1 billion PCs out there - a lot of them old, and certainly still not available for everyone who'd want and could find a use from one (looking at mobile phone uptake, at close to 5 billion subscribers, gives a good idea...). Accidentally, AMD is notably more popular in "lesser" places among "lesser" people. It's a race to more.
      And Fusion will get interesting (look up recent demo from Computex; and remember it was run by the netbook / small laptop version)

      --
      One that hath name thou can not otter
    60. Re:I miss the pressure AMD used to put on Intel by sznupi · · Score: 1

      By that logic, it's pointless to buy (new) quad, six, or octa cores - after all, the most it will do is just cripple the memory and bus bandwiths, in comparison to what a simple (new) dualcore would get from a given (new) mobo.

      And if you only knew what things I have read...

      --
      One that hath name thou can not otter
    61. Re:I miss the pressure AMD used to put on Intel by Chris+Burke · · Score: 1

      1. Good for you. Did you really need the quad core? What are you using the computer for? Did you forget the longevity of LGA 775, where you can still do the same thing? Doesn't make sense to me, but CPUs are readily available.

      I didn't really need quad core, though it certainly comes in handy at times. Dual core is fantastic when you are running 1 CPU bound job and want other IO bound jobs to be highly responsive. Quad core is great for the times I'm doing 2+ jobs and still want other things to be responsive.

      The main thing though I wanted was a major upgrade to my CPU simply in terms of single-thread performance, and in the couple years that transpired between my last purchase there had been many advancements made. And then I looked at what was available, and a quad core a few speed grades from the maximum was the best bang for the buck.

      I don't know what you mean by "did I forget" the longevity of LGA 775. Yeah, you could have gone from a dual core to a quad core in that same package, which is great. My general point is upgradability is highly useful, not some AMD vs Intel cock measuring contest. The performance benefit of an on-die memory controller is huge, though, so in the case of Intel the benefit of moving past LGA 775 (which also gets you other massive improvements in CPU architecture too) is quite high. But for some people, especially before Nehalem came out, the ability to get a quad-core in the 775 package was economically attractive.

      Which I think is great. Why don't you?

      2. I'd suggest taking a hard look at CPU architecture development. By a friend, I happen to know something about it, and the pin layout (corresponding to power and data ports) is actually very important. If you don't think that AM3 was outdated when it came out, I'd suggest doing some research. This is not meant to offensive in any way, the CPU design just means that the pin layout has to live with the optimal physical construction.

      Looking hard at CPU architecture is what I do, thank you very much. And sub-optimal pin layout was why the 939 package didn't last that long. That's why you got burned by it. That was fixed, current CPU designs are not limited by the AM2/3 packages. The architecture of the CPUs is not held back by the package at all. The only significant reason to change is to add or change interfaces. Not to enable microarchitectural improvements.

      3. Your latter point about AMD's big change strikes true to me too, but as a solid-state physicist, I recognize the realities. AM3 is old now, and going past it requires changing the socket, or hampering the real performance just to be backwards-compatible.

      It's only going to hamper performance in the sense that the chip may have 3 or 4 DRAM interfaces, but the legacy package only supports 2. That's a real and significant tradeoff to make, to be sure. Within the context of having made it, the chip performance is not going to be hampered by the socket. The processors that go into the new package with the new interfaces aren't going to be hampered by being backward compatible.

      Again, I'm not an Intel buff by any means, but as a computer building enthusiast, IMO they have been taking the more sensible way, dropping old crud and pushing aggressively forward.

      As a computer architect, that strikes me as completely backwards. Intel's system interconnect was old crud, and they held onto that forever as the longevity of the 775 demonstrates. Their most recent package updates were necessary in order to support their new, non-shitty interconnect and the on-chip memory controller. Stuff AMD has had since early last decade, which is why they needed fewer updates (barring some early missteps of course).

      This idea you have that frequent package updates are necessary to maximize performance outside of interface changes simply isn't borne out by reality.

      --

      The enemies of Democracy are
    62. Re:I miss the pressure AMD used to put on Intel by sznupi · · Score: 1

      Well, that "common sense. Don't buy the latest stuff, as there's always a premium there. Wait a while, and the prices come down" is what it is all about. Get something nice, perfectly good enough & inexpensive, now; wait a while, and the prices for much better things come down (and new things could also be available; either way just in time for the software which might make good use of the upgrade)

      For various values of "a while" of course...but why hurry?

      --
      One that hath name thou can not otter
    63. Re:I miss the pressure AMD used to put on Intel by petermgreen · · Score: 1

      Afaict at least for desktops (laptops usually have the CPU soldered down so you can't upgrade it at all) there are two main platforms.

      The LGA1156 platform is the main one. It covers i3, i5 and i7 8xx. If you are upgrading from a dual-core to a quad-core and are using integrated graphics you will need to add a graphics card at the same time (you will also need a graphics card if building a quad-core system from scratch).

      LGA1366 is the high end platform used for the i7 9xx (and also some server/workstation chips) with more PCIe and more ram channels (which means higher max ram).

      So you should be able to upgrade your i5 to an i7-8xx but you can't upgrade to an i7-9xx (however the i7-870 beats everything in AMDs lineup in desktop workloads afaict).

      BIOS compatibilty may sometimes be an issue but that can be a problem on the AMD side as well. Afaict that is mostly a case of whether you buy your motherboard from a vendor who can be bothered delivering bios updates.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    64. Re:I miss the pressure AMD used to put on Intel by petermgreen · · Score: 1

      I don't see any sense in paying 8x more for a CPU that only runs at about 2x the speed.
      I do,

      For a desktop the question should be "is the extra performance worth the extra price". Depending on your workload and how much your time is worth a machine that is twice as fast may save you several computers worth of time.

      For a machine in a cluster (whether a compute cluster, a server cluster or whatever) the question should be the TCO/performance ratio of the machines. The TCO of a machine involves a lot more than just the performance of the CPUs (cost of other components in the machine, cost of hosting/powerwing the machine, cost of admins).

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    65. Re:I miss the pressure AMD used to put on Intel by petermgreen · · Score: 1

      Notice the performance of the 980X over the other two. There's no more than a 3x performance increase in media encoding.
      If we ignore the single threaded benchmark at the start and the PCmark at the end and focus on the three mulithreaded media benchmarks we get two ratios just over 3 and one just under 3

      So it's just under 9x the price for about 3x the performance (assuming media encoding is your application) which is somewhat different from the figures you stated originally.

      The kind of premium Intel charges for the "Extreme Edition" brand is ridiculous.
      The non-extreme 6-core isn't a whole lot cheaper and the dual-socket stuff with comparable (cores x clockspeed) is also just as expensive once you count the extra motherboard/case/psu cost. It's not the usual extreme edition case of paying a lot more for a slightly faster chip.

      Really comparing price/performance of processors alone is fairly meaningless. If you are buying for a situation where you are limited to one machine it should be a case of whether the time saved makes up for the extra cost. If you are buying for a situation where multiple machines will work together it's about the TCO/performance ratio of the complete machines.

      Lets look at the price of putting together a complete system (to be charitable i'll assume you are running linux and not paying any per-node licensing costs and that the rest of the system is being built on the cheap) based on the i3-530 and i5-980x

      (prices rounded to nearest dollar)
      CPU: $115 for i3-530 , $1000 for i7-980x
      HDD: $60 (for 1TB)
      Motherboard $65 for LGA1156, $130 for LGA1366
      case: $15 (much more if you want to rackmount the system)
      PSU: $15 (more if you want a decent brand that won't blow up on you)
      Graphics: $27 (not needed for i3)
      Ram: $48 (for 2x1GB)

      I make that a total of $314 for the i3-530 system and $1295 for the i7-980x system. So looking at overall system costs you are paying about four times as much for a system that is about three times as fast at video encoding. Depending on your admin and space costs that could easilly be a better deal for machines whose primary purpose is video encoding.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    66. Re:I miss the pressure AMD used to put on Intel by petermgreen · · Score: 1

      Can we go back to i5 quads vs Phenom II X4?
      Lets look at the i5-750 and the AMD Phenom II X4 965.

      Pros of the i5:
      You can upgrade to a quad-core i7 8xx. The only upgrade path for a Phenom II X4 is really a Phenom II X6 and IMO on the desktop faster cores are worth more than more cores
      From what i've read the i5 tends to have lower power consuption especially under idle
      According to toms hardware's performance index it is slightly faster

      Cons of the i5:
      PCIe is rather limited, you get 16 fast lanes from the CPU and 2-6 slow ones from the southbridge. With AMD the fast PCIe is determined by the northbridge, with intel you have to go up to LGA1366 (LGA1366 processors tend to be more expensive for the same performance than the LGA1156 ones) to get more fast PCIe.
      You HAVE to use a seperate graphics card, if you were planning to use one anyway this won't matter much to you but if you weren't it's an extra cost to add on.
      it is a bit cheaper
      LGA1156 motherboards seem to be a bit more expensive than AM3 ones

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    67. Re:I miss the pressure AMD used to put on Intel by Rockoon · · Score: 1

      Blast out 6 cores has a lot different meaning than blasting out 4 cores. Please check out the tech Intel has in place to deliver good performance for a single-threaded app (overclocking the core on which the thread is running on).

      Thats funny fan boy, because AMD has the same automatic over-clocking tech for low-thread workloads, IN THE 6 CORE CHIPS THAT YOU ARE DISMISSING.

      AMD calls it Turbo Core, and the consumer versions of the 6 core chips are named "1055T" and "1090T" where the T signifies this very tech you so ignorantly didnt know the 6 core chips had. We know you are a fanboy because you insist on commenting on AMD's 6 core chips while knowing literally nothing about them other than that they are 6 core, and from AMD.

      --
      "His name was James Damore."
    68. Re:I miss the pressure AMD used to put on Intel by Rockoon · · Score: 1

      i5 750 non-gaming benchmarks?

      The Phenom II x6 1055T scores 5153, sells for $200 (491 systems benchmarked)
      The i5-750 scores 4211, sells for $195 (3098 systems benchmarked)
      The Phenom II x4 965 scores 4261, sells for $177 (2574 systems benchmarked)

      So there we have a SIGNIFICANTLY better benchmark on AMD for $5 more, and SLIGHTLY better benchmark for $18 less.

      ..and unlike most benchmarks, these
      (A) include benchmarks of many systems across many motherboards and memory sticks,
      (B) do not include any overclocking (the site keeps overclocked benchmarks separate and those can be viewed too),
      (C) the benchmarks are very detailed and if you have the passmark benchmark program, can compare systems in all catagories to see whats better and whats not,
      and most importantly
      (D) these systems are not chips "donated" by manufacturers, so no conflicts of interest.. they are chips from stocks available to and sold to consumers, and benchmarked by consumers.

      --
      "His name was James Damore."
    69. Re:I miss the pressure AMD used to put on Intel by ion.simon.c · · Score: 1
    70. Re:I miss the pressure AMD used to put on Intel by sznupi · · Score: 1

      This one was determined by external factors anyway; memory mostly. Too soon for DDR2, but when DDR1 was nearing it end. Not a hard thing to predict / times of viability of given memory tech seem to be slightly longer recently.

      --
      One that hath name thou can not otter
    71. Re:I miss the pressure AMD used to put on Intel by Thundersnatch · · Score: 1

      I was talking about actually finding the optimal price-point, graphing price/performance, and finding the farthest point on the performance axis before the slope of the line significantly increases indicating that you're getting very little return on your extra money. That math is still very relevant. And sure, it's going to point you at a quad-core processor today. But not the fastest one.

      It's funny. I do the same thing often the server space, but include total system costs, including chassis, memory, lifetime power & cooling costs, lifetime warranty and maintenance costs. These costs actually dominate the raw chip costs to such a degree that it almost always makes sense to buy the fastest processor you can and fully load the chassis with as much memory, networking, storage, etc. as you can. Assuming, of course, your workloads can actually use all those resources. Thanks to virtualization, this is pretty much always true these days.

      I imagine this is why AMD has been so dominated by Intel in the server space in the last few years: a cheaper chip might make the TCO of a system 5% lower over 4 years. But if it is 30% slower, it's a bad deal.

  7. Didn't we learn about unbreakable limits by Anonymous Coward · · Score: 0

    When all those people died when steam engines could go faster than 25mph. And no aircraft has gone faster than the sound barrier.

    All these so-called rules and laws are meant to be broken.

    And the fact that Intel cant make something work after 13 years means nothing. They will surely make up for that with all the profits they make in the discrete graphics business.

  8. This question by bigspring · · Score: 2, Interesting

    I think there has been a major article asking this question every six months for the last decade. Then: surprise surprise, there's a new tech development that improves the technology. We've been "almost at the physical limit" for transistor size since the birth of the computer, why will it be any different this time?

    1. Re:This question by localman57 · · Score: 4, Insightful

      why will it be any different this time?

      Because sooner or later, it has to be. You reach a breaking point where the new technology is sufficiently different from the old that they don't represent the same device anymore. I think you'd have to be crazy to think that we're approaching the peak of our ability to solve computational problems, but I don't think its unreasonable to think that we're approaching the limit of what we can do with this technology (transistors).

    2. Re:This question by Anonymous Coward · · Score: 0

      Ah, you must be an economist. You see, here in the real world, we're bound by laws of physics. The laws of physics do not bend to moore's law, it's the other way around.

    3. Re:This question by MozeeToby · · Score: 1

      Eventually there's a theoretical limit, a limit that can't be exceeded without violating the laws of physics, specifically quantum mechanics. Once your transistors get close enough together, the probability of an electron tunneling from one side to the other gets high enough that it isn't possible to tell between your on and off states. We are rapidly approaching that limit even if all the manufacturing issues can be overcome (I believe it's somewhere around 5nm, but I could be wrong).

    4. Re:This question by bigspring · · Score: 1

      I have a fairly solid physics background and I understand that there is a physical limit for a reliable transistor. The problem is that it's not the same thing as the theoretical limit we currently have, nor is it the same as the physical limit for the size of a usable transistor. Our understanding of the science continues to progress and as we learn more and more about the principles we discover reasons why the the theory is wrong. Additionally, there are some very clever engineers working on the project who prove over and over again that they can improve on their current techniques, fabrication tools, and materials to push the theoretical limit. Then, where these things fail, there are even more folks standing by with ever more sophisticated error correction techniques to efficiently and consistently use transistors that are not physically reliable. Don't get me wrong, there will be a time when the our current transistor model will stop advancing. What I'm saying is that until the point where advances have actually ground to a halt, or hell, markedly slowed down, I don't want science and tech writers cramming stories down my throat about how we'll never see another significant advance in computing power.

    5. Re:This question by rienafairefr · · Score: 1

      nope, before that people were talking about problems of creating a transistor small, but due to other problems (short channel effects etc etc). Now, we are facing atoms, dude, atoms, not just problems that can be solved with careful engineering (and of which solutions were academically studied). Nowadays, reducing gate lengths to a couple of atoms is not feasible to have enough performances, period. physical limit, this time. before, it was a scare of not being able, but with good ideas over how to do it. Now we have no good idea to reduce silicon based transistor much more.

    6. Re:This question by Anonymous Coward · · Score: 0

      As feature size decreases you ALWAYS have to deal with new layers of additional constraints. Circut design nowadays is almost exclusivly about avoiding problems. Normal people sit on the edge and look down the hole and see all of these new issues layered on top of each other, throw up their hands and give up proclaiming the end is here. While the people actually doing the design work come prepared with shovels and trackhoe standing by but as well all know shrinks most certainly won't just continue on forever.

      I fear at some point in the not so distant future the long term reliability of components will really begin to suck as tolerances are narrowed soo much shit will start slipping past simulation.

      What circut designers really need to do is stop pushing electrons. photons, plasmons...ANYTHING but electrons!! We're not going to get signficiantly better performance or energy effeciency out of pushing electrons no matter how fricking small things get.

    7. Re:This question by petermgreen · · Score: 1

      If we assume feature size halve every two years then in a decades time our feature size will be down to 1 nanometer. Afaict this translates to about 2 atoms!

      Fundamentally electronics is based on the idea that we can treat a doped semiconductor as a homogenous material. At sizes in the single atoms this will make no sense anymore and below one atom I just don't see how you could make the features any smaller while continuing to have a crystal lattice structure.

      Within the next decade or so feature size decrease (which afaict is the main thing that has powered moores law) will no longer be an avenue open to us. Increasing clock speed is also likely to be hampered by speed of light issues.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  9. Plank's Law by cosm · · Score: 4, Funny

    Well I can say with absolute certainty that they will not go below the Planck length.

    --
    'We are trying to prove ourselves wrong as quickly as possible, because only in that way can we find progress.' RPF
    1. Re:Plank's Law by Anonymous Coward · · Score: 0

      That's what you say now. Great hubris, our scientists have!

    2. Re:Plank's Law by imgod2u · · Score: 1

      *For classical computation

    3. Re:Plank's Law by Yvanhoe · · Score: 2, Insightful

      At 10^-35 meters, that leaves us a lot room...
      And being certain about something that comes from uncertainty principle makes me feel confused...

      --
      The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
    4. Re:Plank's Law by Idiomatick · · Score: 1

      I heard some constants these days may vary.

    5. Re:Plank's Law by pclminion · · Score: 1

      Well I can say with absolute certainty that they will not go below the Planck length.

      If the number of transistors goes up by a factor of 2, then the characteristic feature size must go down by a factor of 1.414 (sqrt(2)) in the same period of time. How many such periods would it take to reduce from a feature size of 2e-8 m (20 nm) to 1.6e-35 (Planck length)? Well, that's log(2e-8/1.6e-35)/log(1.414) = 180 doubling periods. Each period is 18 months, so it would take 270 years to get there. I'm seriously hoping that in the next 270 years we'll figure out something besides silicon transistors.

    6. Re:Plank's Law by Anonymous Coward · · Score: 0

      There's always Hyperspace.

    7. Re:Plank's Law by Anonymous Coward · · Score: 0

      You never know until you know less.

  10. Quantum Computing by Anonymous Coward · · Score: 0

    Perhaps as we get closer to these physical limits of classical computing we'll start to see more and more money invested in quantum computing research.

    1. Re:Quantum Computing by psbrogna · · Score: 2, Insightful

      I'd settle for less bloat-ware. Back in the day amazing things were done with extremely limited CPU resources by programming closer to the wire. Now we have orders of magnitude more resources but most programming is done at a very high level with numerous layers of inefficiency which negates, possibly more than negates, the benefits of increased CPU resources. Yes, yes- I wax a little "in my day/up hill both ways, etc." but do the benefits of high level programming and efficient use of resources have to be mutually exclusive?

    2. Re:Quantum Computing by xMilkmanDanx · · Score: 1

      It's actually more a question of economics.

      In the old days, adding processing power was expensive so spending more dev time on optimization/running faster but harder to program languages made sense. Now, it's cheaper to throw more power at a problem than to spend 10-100x the dev time.

    3. Re:Quantum Computing by ePhil_One · · Score: 1

      I'd settle for less bloat-ware. Back in the day amazing things were done with extremely limited CPU resources by programming closer to the wire

      Thus leading to the year 2000 debacle. Things go a lot faster when you assume great swaths of stuff, don't do bounds checking, leverage hardware quirks, etc.

      Not that software development hasn't lagged behind hardware development and there are great steaming piles of bad software out there (Really, you query the entire database contents out then search the results in software?), but there's also some good reasons why its more bloated. Security, error checking, bounds checking, transportability, etc all cost

      --
      You are in a maze of twisted little posts, all alike.
    4. Re:Quantum Computing by Anonymous Coward · · Score: 0

      Modern C++ compilers do a pretty good job optimizing such a high-level language.

      If you actually meant interpreted languages, then yes of course it's mutually exclusive. Running the compiler *every time you run the program* sucks a lot more CPU power than just running the program itself. And that includes Java's VM, although it's by far the best of the bunch, having had a decade more optimization done on it than most others, and almost two decades more than C#.

    5. Re:Quantum Computing by ChrisMaple · · Score: 1

      If you're doing serious scientific or engineering computing (SPICE for example), most of the old programs are still available and still run. They run faster on modern hardware.

      Several things make modern programs seem slower. One is that expectations have increased; few people remember waiting several seconds for WordStar to respond while it accessed the floppy. Another is eye candy, which is very costly in terms of performance. Another, surprisingly, is better coding: Each time a programmer goes back over old code and fixes an error that only occurs for special inputs, testing for those special inputs takes time.

      Another factor is that a modern computer is often very busy. The OS might be spending hours each day doing various sorts of cataloging and backup, so if you're batch processing a few dozen 4000x3000 photos while using realplay, firefox may seem to respond slowly.

      --
      Contribute to civilization: ari.aynrand.org/donate
  11. Plan the dark areas around the defects by grahamsz · · Score: 2, Interesting

    Larger dies generally cost more because it's more likely that they'll have a defect. I haven't done any chip design since college (and even then it was really entry level stuff) but if you could break the chip down into 10 different subcomponents that need to be spaced out, you could put 100 of those components on the chip and then after manufacture you could select the blocks that perform best and are defect free, spacing your choices accordingly.

    I'm pretty sure chip makers likely already

    1. Re:Plan the dark areas around the defects by cheesybagel · · Score: 1

      They do this already. This technique works best on highly redundant and homogeneously distributed components such as cache memory blocks. However if by some stroke of bad luck the error is in the control unit you are toast.

    2. Re:Plan the dark areas around the defects by treeves · · Score: 1

      Larger dies generally cost more because it's more likely that they'll have a defect.

      That and more importantly, the fact that you get fewer chips per wafer with larger die.
      Costs are close to the same per wafer (only litho exposure steps take longer with more die and this not usually gating) but if you double the number of chips per wafer by making them half as large (70% shrink in each axis) you effectively cut their cost in half. (except for the amortized capital expense of all the new scanners etc. you need to make and inspect the smaller features).

      EUV lithography is still being worked on and not just by Intel. It's getting closer all the time.

      --
      ...the future crusty old bastards are already drinking the Kool-Aid.
    3. Re:Plan the dark areas around the defects by Anonymous Coward · · Score: 0

      I haven't laughed this hard in weeks.

  12. Oh no.... by AnonymousClown · · Score: 1
    First the car analogy. Then the pizza analogy. Now, the taco chip analogy.

    At some point, we're going to see an argument that starts out with "It's like a Nazi eating a Tostito with ..."

    At least a Tostito is a chip.

    --
    RIP America

    July 4, 1776 - September 11, 2001

  13. Ummm... it's called x64. by Joce640k · · Score: 0, Troll

    Intel and AMD have both been producing it for a number of years now.

    --
    No sig today...
    1. Re:Ummm... it's called x64. by Anonymous Coward · · Score: 0

      x64 is just extensions to x86. It's actual architecture sign is x86_64. It still is fundamentally x86 just with a few modifications to add on 64-bit.

    2. Re:Ummm... it's called x64. by Bigjeff5 · · Score: 1

      Were that the case, x64 would not be backwards compatible with x86.

      It is compatible, however, because it's really just a set of instructions added on to x86. The core is still x86. The only reason it's called x64 instead of x86_64 (which is what it actually is) is because AMD beat Intel to the punch on that one, and it's their baby that went to market. Intel is stuck with what AMD gives them on that score.

      --
      Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
    3. Re:Ummm... it's called x64. by Anonymous Coward · · Score: 0

      Umm, no. x64 isn't that different from x86. It basically is just taking the x86, adding a few instructions and the brains to be able to handle 64-bit integers, but it's basically a x86 chip.

  14. Nothing new here, move along... by axafg00b · · Score: 1

    Actually, the issue of decreasing linewidths has been a major concern ever since UV lithography came into play. The progress is really amazing. It was a big deal in the late '80s to get under 100nm, now there is consistent production at 32nm. There have been research programs investigating X-Ray lithography and electron-beam lithography, but I don't think any of these have panned out for mass production. Now, another concern is electron leakage from these tinier linewidths. Sure, high-K materials help, but there is still some loss.

    --
    I think, therefore I am - Rene Descartes; I yam what I yam, an' that's what I yam - Popeye
    1. Re:Nothing new here, move along... by EmagGeek · · Score: 1

      There was a lot of electron beam lithography research going on when I was in grad school. One of the major hurdles was that every time someone slammed a door somewhere else in the building, it would vibrate the fixtures enough to ruin the device, despite the best efforts to shield the fixture (and the building, and the room, and the stand, and everything else) from vibration.

    2. Re:Nothing new here, move along... by WuphonsReach · · Score: 1

      There have been research programs investigating X-Ray lithography and electron-beam lithography, but I don't think any of these have panned out for mass production.

      From the reading I did earlier this week, you are correct. Those 2 methods worked, but they were expensive. What has caught on instead is "double-patterning" (and possibly triple/quad patterning). Double-patterning gives you the same feature size as the more advanced methods, but for a lot less cost.

      (Assuming that I understood the articles correctly. Definitely do a search on double-patterns/patterning.)

      Hynix was talking 22nm recently for SSD silicon.

      --
      Wolde you bothe eate your cake, and have your cake?
    3. Re:Nothing new here, move along... by ePhil_One · · Score: 1

      Chip fab in space up next

      --
      You are in a maze of twisted little posts, all alike.
  15. This is what reversible computing is for, right? by TimFreeman · · Score: 2, Interesting

    The article mentions "dark transistors", which are transistors on the chip that can't be powered because you can't get enough power onto the chip. This is the problem that reversible computing was supposed to solve.

  16. 3D chips to keep the scale going by RichMan · · Score: 1

    Current technology is based on a single planar layer of silicon substrate. A chips is built with a metal interconnect on top. But the base layers are essentially a 2D structure. We are already postprocessing things with thru vias to stack substrates into a single package. The increases density from the package perspective.
    Increasing technologies in stacking will keep Moors law going for another decade (as long as you consider Moor's law to be referencing density in 2D).

    1. Re:3D chips to keep the scale going by Anonymous Coward · · Score: 0

      Increasing technologies in stacking will keep Moors law going for another decade

      Skynet agrees... keep working on those 3d chips.

  17. or WIMAX by Anonymous Coward · · Score: 0

    or WiMAX

  18. "Extreme Ultraviolet" by markbark · · Score: 1

    because "X-rays" is such an UGLY word....

    1. Re:"Extreme Ultraviolet" by sunbane · · Score: 4, Informative

      Because X-rays are .01 - 10 nm light and EUV is 13.5nm light... so nothing to do with the word, as much as engineers like to label things correctly.

    2. Re:"Extreme Ultraviolet" by erice · · Score: 1

      EUV is 13.5nm, X-rays are generally thought of 10nm and smaller. http://hyperphysics.phy-astr.gsu.edu/hbase/ems3.html

      It is close and this region is sometimes referred to as "soft" X-rays but there is nothing incorrect about the "UV" moniker. It also helps to distinguish EUV from actual X-ray lithography, a largely abandoned approach which used wave lengths on the order of 1nm. http://en.wikipedia.org/wiki/X-ray_lithography

    3. Re:"Extreme Ultraviolet" by Steve525 · · Score: 2, Insightful

      because "X-rays" is such an UGLY word....

      There's actually some truth to this. Originally it was called soft x-ray projection lithography. The other type of x-ray lithography was a near contact shadow technique using shorter (near 1nm) x-rays. To distinguish the two techniques they changed the name from soft x-ray to EUV.

      This was also done for marketing reasons. X-ray lithography had failed (after sinking a lot of $$ into it), while optical lithography had successful moved from visible to UV, to DUV. By calling it EUV it sounds like the next logical step, instead of being associated with the failure that was x-ray lithography.

      (Actually, x-ray lithography didn't really truly fail. It does work, but optical surpassed it before it was ready, so it became pointless)

  19. GPUs work kind of like this by Sycraft-fu · · Score: 3, Informative

    Since they are so parallel they are made as a bunch of blocks. A modern GPU might be, say, 16 blocks each with a certain number of shaders, ROPs, TMUs, and so on. When they are ready, they get tested. If a unit fails, it can be burned off the chip or disabled in firmware, and the unit can be sold as a lesser card. So the top card has all 16 blocks, the step down has 15 or 14 or something. Helps deal with cases were there's a defect, but overall the thing works.

  20. I'd say you haven't by Sycraft-fu · · Score: 4, Interesting

    For one, Itanium is still going strong in high end servers. It is a tiny market, but Itanium sells well (no I don't know why).

    However in terms of the desktop, you might notice something: When AMD came out with an x64 chip and everyone, most importantly Microsoft, decided they liked it and started developing for it, Intel had one out in a hurry. This doesn't just happen. You don't design a chip in a couple months, it takes a long, long time. What this means is Intel had been hedging their bets. They developed an x64 chip (they have a license for anything AMD makes for x86 just as AMD has a license for anything they make) should things go that way. They did and Intel ran with it.

    Ran with it well, I might add, since now the top performing x64 chips are all Intel.

    They aren't a stupid company, and if you think they are I'd question your judgment.

    1. Re:I'd say you haven't by BitZtream · · Score: 2, Informative

      They developed an x64 chip (they have a license for anything AMD makes for x86 just as AMD has a license for anything they make) should things go that way.

      Actaully, no they don't.

      There are certain things they share licenses for, but thats mostly related to Intel wanting to be able to fill government contracts that require multiple vendor sources.

      It does not cover everything that is x86, which is why the two companies regularly sue each other over silly shit.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    2. Re:I'd say you haven't by Anonymous Coward · · Score: 0

      Remember how Pentium 3's were than Pentium 4's at the same clock speed. Remember Rambus? Intel's made it's share of boneheaded moves.

    3. Re:I'd say you haven't by Anonymous Coward · · Score: 0

      should have read "were faster than"

    4. Re:I'd say you haven't by vidnet · · Score: 1

      Itanium is still going strong in high end servers. It is a tiny market, but Itanium sells well

      While I didn't find figures for "going strong" and "sells well", parent is apparently along the right lines. I had no idea that Itanium now sells enough to be profitable!

    5. Re:I'd say you haven't by Tablizer · · Score: 1

      What this means is Intel had been hedging their bets...They aren't a stupid company...

      Or perhaps one can say that they do stupid more efficiently
         

  21. Would it really help though? by Sycraft-fu · · Score: 1

    It seems to be almost an article of faith with geeks that if only we didn't have that nasty x86 we could have so much better chips. However the thing is, there ARE non-x86 chips out there. Intel and AMD may love it, others don't. You can find other architectures. So then, where's the amazing chip that kicks the crap out of Intel's chips? I mean something that is faster, uses the same or less power and costs less to produce (it can be sold for more, but the fab costs have to be less). Where is the amazing chip that uses a bunch less silicon but does the same work?

    You can't find one, and there's a reason for that. The API of the chip is just not such a big deal these days. For a lot of reasons you can have many kids of APIs and it doesn't really increase the complexity of the chip by a lot, nor mess with performance.

    I'd love to see that I'm wrong about this, I'd love to see a desktop CPU (remember that's what we are talking about here, not embedded stuff) that can outperform an i7 with less silicon and less power, but I haven't and I don't think I will.

    1. Re:Would it really help though? by powerlord · · Score: 1

      ARM seems to be trying to be that Architecture (it certainly is gaining traction in the "low battery" market).

      But that may be a niche where 10 hour Laptop life is important.

      --
      This space for rent. All reasonable inquiries will be entertained at proprietors discretion.
    2. Re:Would it really help though? by Sycraft-fu · · Score: 1

      But here's the thing with that:

      1) It is an embedded chip. Architecture may make a big difference in the ultra low end, when the chips are tiny and not that capable. That is not the market x86 is in. How does it scale to regular desktop and laptop processors?

      2) Are they more powerful with less power usage? Less power usage isn't the issue, there are plenty of lower power CPUs. The issue is can you actually do the same amount of computation, but do it using less energy, less silicon, with a non-x86 architecture? IBM and Motorola can't, maybe ARM can but not that I've seen so far.

      If you can't do that, then you don't have any example of architecture mattering with regards to performance in the desktop (and I include regular laptops here since the use the same basic chips) sector.

    3. Re:Would it really help though? by Anonymous Coward · · Score: 0

      ARM does have a better power/computation ratio than Intel. However they are doing less while using much less power, rather than doing more with same amount of power. If they have a faster CPU that beats an Intel chip at both cpu and electrical power, I am not aware of it.

    4. Re:Would it really help though? by Anonymous Coward · · Score: 0

      2) Are they more powerful with less power usage? Less power usage isn't the issue, there are plenty of lower power CPUs. The issue is can you actually do the same amount of computation, but do it using less energy, less silicon, with a non-x86 architecture? IBM and Motorola can't, maybe ARM can but not that I've seen so far.

      I think that GreenArrays has an interesting approach to this part, at least.

    5. Re:Would it really help though? by powerlord · · Score: 1
      --
      This space for rent. All reasonable inquiries will be entertained at proprietors discretion.
  22. Clock speed is a no-go by Anonymous Coward · · Score: 1, Informative

    With greater clock speed comes greater heat dissipation needs (most heat is created at clock switching); they have basically hit this wall already, hence the multi-core direction everyone is taking (can't go faster, so lets just go the same speed, but in parallel).

    1. Re:Clock speed is a no-go by QuantumLeaper · · Score: 1

      I thought it was crosstalk between the transistors that killed anything past 4GHz, silicon could do around 10GHz if we could get rid of crosstalk cheaply, or do you want to pay $10,000 for a CPU? Diamond or http://en.wikipedia.org/wiki/Graphene could be used as a silicon replacement, but it wouldn't be anytime in the next decade.

    2. Re:Clock speed is a no-go by Spatial · · Score: 2, Insightful

      (can't go faster, so lets just go the same speed, but in parallel).

      Actually they do go faster. Clock speed doesn't mean processing speed. Modern CPUs do much more per clock cycle than their predecessors because of their greater instruction-level parallelism, shorter instruction latencies, larger caches, etc. While their cores don't generally operate at a higher frequency, they perform many times faster.

      That's not even considering the additional cores and massively improved power efficiency. It's difficult to overstate just how fucking amazingly good CPUs are now.

  23. Re:This is what reversible computing is for, right by imgod2u · · Score: 2, Insightful

    People have been proposing circuits for regenerative switching (mainly for clocking) for a long long time. The problem always being that if you add an inductance to your circuit to store and feedback the energy, you will significantly decrease how fast you can switch.

    Also, you think transistors are difficult to build in small sizes? Try building tiny inductors.

  24. Obviously, one transistor per atom by Surt · · Score: 1

    That's how small they can go. Beyond that, increasing the functional density of our CPUs will get really challenging.

    --
    "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
  25. Sci Fi Story about that by ch-chuck · · Score: 1

    Sort of off topic but there was a science fiction story about this scientist who created a potion that could make him smaller, and he just kept shrinking and shrinking, and all the different worlds he went thru each time, atoms turned into solar systems, and he just kept going down, down, down into infinite smallness. The story is here.

    --
    try { do() || do_not(); } catch (JediException err) { yoda(err); }
  26. CPU caches also work like that by imgod2u · · Score: 2, Informative

    Actually, it's pretty common practice to put spare arrays and spare cells in the design that aren't connected in the metal layers. When a chip is found defective, the upper metal layers can be cut and fused to form new connections and use the spare cells/arrays instead of the ones that failed by use of a focused ion beam.

    But that still adds time and cost. Decreasing die area is pretty much always preferable. Also, larger dies means even more of the chip's metal interconnects have to be devoted to power distribution.

    1. Re:CPU caches also work like that by ultranova · · Score: 2, Insightful

      Actually, it's pretty common practice to put spare arrays and spare cells in the design that aren't connected in the metal layers. When a chip is found defective, the upper metal layers can be cut and fused to form new connections and use the spare cells/arrays instead of the ones that failed by use of a focused ion beam.

      Am I the only one who finds it pretty awesome that we're actually using focused ion beams in the manufacture of everyday items?

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    2. Re:CPU caches also work like that by Anonymous Coward · · Score: 1, Funny

      Yes.

    3. Re:CPU caches also work like that by Bitmanhome · · Score: 1

      No, not until we can use them to keep the Star Destroyers away.

      --
      Not that this wasn't entirely predictable.
    4. Re:CPU caches also work like that by ChrisMaple · · Score: 1

      It's my understanding that physical editing of a defective chip is very expensive (hours of labor) and is only done in the development process to avoid the hundreds of thousands of dollars required to make a new set of masks. It's not a normal production process.

      --
      Contribute to civilization: ari.aynrand.org/donate
  27. Better software by Andy_w715 · · Score: 5, Insightful

    How about writing better software. Stuff that doesn't require 24 cores and 64GB of RAM?

    1. Re:Better software by valnar · · Score: 1

      Oracle 11g, meet MSDOS.

    2. Re:Better software by Spatial · · Score: 1

      It's kinda difficult!

      Even more difficult is making non-shit programming tools that would allow us to do that in a reasonable amount of time. In fact it's so hard that nobody has ever done it. We're stuck with essentially the same old shit we were using 25 years ago.

      As you can imagine, "Pay me ten times more to get the same program done in quadruple the time" isn't very compelling in a corporate environment.

    3. Re:Better software by Anonymous Coward · · Score: 0

      because then we wouldn't be able to outsource programming jobs for $5/hr!

    4. Re:Better software by 4pins · · Score: 1

      Some would say that if your software can utilize 24 cores, it is good.

      --
      I will not mourn that which I never had to lose. - Unknown
    5. Re:Better software by evilviper · · Score: 3, Insightful

      How about writing better software. Stuff that doesn't require 24 cores and 64GB of RAM?

      They did. The are damn fast on modern processors, too. However, people simply look at me funny for using all GTK v1.2 applications... GIMP, aumix, emelfm, Ayttm, Sylpheed1, XFce3, etc.

      So, why AREN'T YOU using better software, which "doesn't require 24 cores and 64GB of RAM"?

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    6. Re:Better software by Anonymous Coward · · Score: 0

      yeah so far we are building software upon a cumulatively ancient stack of middleware without wondering whether we still need all that ''potential'' ''possible'' ''possibilities'' at each level or we simply could boil it down to something much tighter to what we actually use. I expect Chrome OS comes to revise at least part of this.

      Windows 98 flew with 1 CPU @ 350MHz and 64MB of RAM. Couldn't a modern stack of software allow us to do web, instant messaging and office with 350MHz and 64MB of RAM? Plus some hardware for decoding HD audio and video and we would be set.

      3 men went down from the orbit of the moon to the surface and returned with 1 CPU @ 2MHz, 72KB of ROM and 4KB of RAM. I understand drawing a 2 Megapixel GUI requires more than that but, why the F* are we needing 1,000 times that processing power and 100,000 times that memory?

    7. Re:Better software by Anonymous Coward · · Score: 0

      You sir are a liar and a heretic. Moore's Law is specifically available for the purposes of dumping all our lack of skill into processor/memory overhead and just hoping that we get around to releasing a revision with garbage collection sometime before our product is obsolete. I wish that was only joking...

    8. Re:Better software by vlueboy · · Score: 1

      "How about writing better software. Stuff that doesn't require 24 cores and 64GB of RAM?"

      I for one wish we would reach hard limits like the Planck barrier TODAY. Think of the benefits of other things lacking useful increase these days: like cheap modems stuck at 56K speeds, floppy drives for flashing those old corporate motherboards, ball mouse resolutions, sound card voice count, and CD/DVD recording units.

      Prices fall like bricks: $20 instead of a hundred per unit, which is elusive on the CPU market today. Advantages of technology limited by physics? People learn to cope or get other optimizations, or develop alternatives like DSL, USB sticks able to store more than 8GB DVD disks, high precision/dust-proof laser mice, and finally our multi-threaded programming and our multi-core environments [curiously already made at nearly fixed speeds of 3.0 GHZ since 2006, mind you.]

      CPU-wise, programmers can't handle parallel computing as a majority. Limits and company forces would stabilize them to a level playing field where "can't" makes you lose, and the best ideas are the ones that add value per each fixed clock cycle.

    9. Re:Better software by Cajun+Hell · · Score: 1

      Ok, write it. And I'll run it on a 24-core 64GB machine. It'll be awesome.

      --
      "Believe me!" -- Donald Trump
    10. Re:Better software by RyuuzakiTetsuya · · Score: 1

      Normally as an Apple fanboi, I applaud their achievements.

      However with Grand Central Dispatch you can multithread your incompetence and spread it among many cores! Not just one!

      --
      Non impediti ratione cogitationus.
    11. Re:Better software by ePhil_One · · Score: 1

      How about writing better software. Stuff that doesn't require 24 cores and 64GB of RAM?

      Or solving smaller problems? When I was a kid we were happy to control a dot on our TV

      --
      You are in a maze of twisted little posts, all alike.
    12. Re:Better software by hviniciusg · · Score: 1

      I could not agree more whit you, but i think if that happened Intel and AMD would be out of bossiness or can someone explain me why window 7 requires 2 GB of ram, core 2 duo and all that fancy new hardware to almost the same that windows 98 and windows 98 required only 256 Mb and a 350 MHz CPU?

    13. Re:Better software by Anonymous Coward · · Score: 0

      So you are pretty much asking: Why didn't they just optimize Crysis enough so it can run on a 386? What is wrong with those lazy programmers?

      There is a limit on how fast software can run. As you optimize code, you have diminishing returns as you reach an asymptote. There is software out there that could greatly benefit from some optimizations but not as much as you might think (at least I don't run any of it). You get to the point where you have to either drop features, accept approximate results, constrain inputs, or make some other trade off.

      Also all that time spent optimizing could be spent adding new features, increasing stability, or improving usability. Users care about more than just speed. I can make my code super fast if it doesn't have to always work.

      Well-optimized code is really a pain to change. Once you do extreme optimizations, you better not have customers ask you for any changes. The code won't be flexible because it was tuned for performance. Even seemingly simple changes will require the code to be completely re-written and it won't have the same performance characteristics.

    14. Re:Better software by Anonymous Coward · · Score: 0

      because i'm a certified ACCESS programmer. btw you should use Word's spell check.. what do all these typo's in your post even mean? GTK v1.2 , GIMP, aumix, emelfm, Ayttm,

      rotfl !!!

    15. Re:Better software by Anonymous Coward · · Score: 0

      Come on man, putting GIMP and aumix on the same line? And not even a GTK application at all...

      Hopefully you meant some other software, not sure how you could write a sound card interface that requires 24 cores and 64GB of RAM...

    16. Re:Better software by evilviper · · Score: 1

      And not even a GTK application at all...

      Everything listed are DEFINITELY GTK applications.

      not sure how you could write a sound card interface that requires 24 cores and 64GB of RAM...

      I'm not sure how you could write ANYTHING that requires 24 course and 64GB of RAM...

      However, I'm extremely annoyed by all the trivial software that takes 5+ seconds before it pops up on-screen, while older versions launched in a fraction of a second...

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    17. Re:Better software by Tuan121 · · Score: 1

      Because it isn't always worth the time.

    18. Re:Better software by Anonymous Coward · · Score: 0

      Useability. There I fucking said it.

  28. Who cares about lithography? by david_thornley · · Score: 1

    The diameter of a silicon atom is roughly. 0.25 nm. That means that 32nm is about 120 atoms across. A 16nm line is about 60 atoms across.

    For reliable use, there is going to be an approximate minimum to number of atoms in a line. Electron interactions among individual atoms are quantum events, so for any sort of predictability you're going to need enough atoms for the probabilities to average out enough. I don't know how many that is, but it pretty much has to be more than one.

    I have a great deal of faith in the ingenuity of the companies involved, but there is a lower limit that's independent of fabrication, and we've got to be getting fairly close to it.

    --
    "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    1. Re:Who cares about lithography? by pz · · Score: 1

      The diameter of a silicon atom is roughly. 0.25 nm. That means that 32nm is about 120 atoms across. A 16nm line is about 60 atoms across.

      For reliable use, there is going to be an approximate minimum to number of atoms in a line. Electron interactions among individual atoms are quantum events, so for any sort of predictability you're going to need enough atoms for the probabilities to average out enough. I don't know how many that is, but it pretty much has to be more than one.

      I have a great deal of faith in the ingenuity of the companies involved, but there is a lower limit that's independent of fabrication, and we've got to be getting fairly close to it.

      A single transistor channel is more than a one atom wide chain of silicon atoms N nm long. Averaging comes from not just the length but the width, too.

      --

      Put my fist through my alarm clock with its ding-dong death inside my ear. - The Blackjacks.
    2. Re:Who cares about lithography? by ChrisMaple · · Score: 2, Interesting

      Another critical dimension is gate thickness. When you speak of a 16 nm process, you are (generally) talking about the minimum dimension in the XY plane, which is usually reserved for gate length. Gate thickness is a much smaller dimension, and if I recall correctly we're already down to about 4 molecules of thickness. Quantum tunneling is a problem.

      --
      Contribute to civilization: ari.aynrand.org/donate
  29. 3D Chips by Doc+Ruby · · Score: 1

    Why hasn't Intel rolled out 3D chips stacked in layers, with microfluidics cooling between layers? I used to see all kinds of engineering PR about it, but it's been years since I saw any progress, and it's taken way longer than I expected.

    3D would not only increase the amount of transistors (and other devices) fit into a "chip", but put the circuits closer together, requiring less voltage/power and shorter propagation times. What's holding it up?

    --

    --
    make install -not war

    1. Re:3D Chips by erice · · Score: 3, Informative

      Actually, 3D has picked up quite a bit in the last few years. However, the primary interest is connect different chips together in the same package with short, fast, interconnect. It's a lot better than conventional System In Package and much much better than circuit board connections. Unfortunately, the connections are a bit too coarse to spread a single design like an Intel processor across the layers.

      For that you need more sophisticated methods like growing a new wafer on top of one that has already been built up. These methods are not yet ready for production.

    2. Re:3D Chips by ChrisMaple · · Score: 1

      For many years (45?) it's been possible, and in some cases practical, to grind/polish away the substrate. It's possible to make a wafer no thicker than the metal + active elements. "All" that's needed is a practical way to make the actual connections between two or more chips from such wafers. It sounds expersive to me, and if the chips are large, yield will be a severe problem.

      --
      Contribute to civilization: ari.aynrand.org/donate
  30. diffraction by Khashishi · · Score: 1

    Perhaps the answer is to use something like electron beams or atomic beams instead of photons.

    1. Re:diffraction by Anonymous Coward · · Score: 0

      Perhaps the answer is to use something like electron beams or atomic beams instead of photons.

      Or redesign the transistor....

  31. Here comes the.. by WakaRiMaSu · · Score: 2, Informative

    graphene.

  32. Is mobile a good excuse? by jamesvandyke · · Score: 1

    I wonder if the mobile chips are a good excuse to introduce the public to a new architecture. You start selling a phone with the new architecture where it's low risk and the software isn't entrenched. Then, scale it up for different devices until at some point you introduce it to desktops? It looks like this is what Apple is starting to do with the Cortex chips.

  33. Start stacking'em up by BitZtream · · Score: 1

    Seriously, silicon CAN be stacked. Not in a single process but multiple dies in a single package is a good start. No, its not going to start out showing the same speed increases that we've got from shrinking the size of everything, but once you get so small you're done. Once you start getting every single drop of computational power out of a particular bit of matter, the only thing you can do is add matter.

    Its just another way to add cores essentially. Given some time, someone will start figuring out WAY better ways to interconnect the stacked dies, or eventually make one die with layers of silicon in a truely 3d chip.

    Its not going to advance until we start doing it and learning what works and what doesn't. Until we put some effort into 'work arounds' that almost achieve what we really want, we'll never likely jump directly to the end result.

    Car Analogy:

    Instead of trying to jump from cave man to Aston Martin, the wheel was invented first, and then various methods of attaching wheels to seats and animals, and finally to where we are today.

    We may even find out that our current thoughts about building chips in layers is just a bad idea anyway and we go an entirely different and far more useful direction, and then all the buggy whip makers will be freaking pissed but society will be better off for it.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    1. Re:Start stacking'em up by rienafairefr · · Score: 1

      nope, because we do computations with electronic currents, we can not add computational matter, like you'd like. not that simple. Look around child, people have stacked chips for decades, and it's not helped them a lot. silicon is expensive, basically. once you find a simple, cost effective way to stack stuff and have no problems of delays between stacks, no problem of loss of areal density, no problems of manufacturing, no problems of heat disspation, then go on, youll be rich. You can not solve an industry's problem in a comment, period

  34. Smaller is better? by DarthVain · · Score: 1

    making a smaller die size means you can fit more on a single chip, which in turn makes it go faster right? Well only if you keep to the same idea.

    Why do we need so many? Well the speed in which electricity travels, and from which something can switch from + to - is pretty much constant. Our current technological method is simply making them small and cramming more and more and more onto a chip, which can then of course do more, because it has more stuff. All that stuff is still all working at the same "speed", just more of it is working.

    While not very far along the development line, using "light" rather than current solves a lot of problems. A) it is a lot faster, and B) likely does not produce the amount of heat due to resistance along the material.

    More exotic is quantum chips, which I don't know all that much about, so they may, or may not exist... :)

    1. Re:Smaller is better? by DarthVain · · Score: 1

      Though I do remember hearing that rather than using Binary a whole new system would have to be used, or at least translated, as there was 0,1,2... On, Off, and Maybe or something along those lines...

    2. Re:Smaller is better? by Bitmanhome · · Score: 1

      More exotic is quantum chips ... they may, or may not exist... :)

      Yeah, that describes quantum chips quite well.

      --
      Not that this wasn't entirely predictable.
    3. Re:Smaller is better? by rienafairefr · · Score: 1

      not willing to be rude, but you have no idea what you're talking about. the speed of electricity has no sense at all. In chips, what's important is delays, due to capacitances and resistances, thus the delay of a line of copper might not be the same depending of its size and surroundings. the speed at which a transistor switches depends also of its surroundings, etc. Your idea of using light, pretty good, though been thought of since, like, before you were born. But it's still much more complex than using current, for now. smaller transistors switch faster. if you contain the delay of the lines, youll get a core working faster, but its much more complex thant "it has more stuff then but all that stuff at the same speed etc"

    4. Re:Smaller is better? by ChrisMaple · · Score: 1

      To some extent, "back of the envelope" calculations show that light cannot solve the problem. Light that can be made conveniently with semiconductors has a wavelength of about half a micron, which sets a minimum for feature sizes, and chips are already using devices with features an order of magnitude smaller than that. Secondly, light from semiconductors requires a minimum voltage to generate it, and that voltage is about 1 volt. We're already running close to that 1 volt limit, so improvements below 1 volt aren't feasible for light-based logic.

      Wavelength is inversely proportional to voltage.

      --
      Contribute to civilization: ari.aynrand.org/donate
    5. Re:Smaller is better? by DarthVain · · Score: 1

      Not to be rude, but you are arguing semantics.

      Are you trying to say that the speed in which electricity travels through a medium doesn't have anything to do with "capacitances and resistances"?

      Because I was talking about speed, and you the other. I also believe I mentioned those very words when talking about heat, which as most are aware is the actual limiting factor. As melting your chip in the attempt for more speed (by trying to overcome resistance) isn't too helpful.

      Or are you trying to say that that the "capacitances and resistances" will slow down light? Because that would be new to me that light shared those properties with electricity. I would think that interference and coherence would be more an issue with light but what the hell do I know.

      Also considering you don't know when I was born, I find it unlikely you can come to any conclusion as to when light started to be experimented on for computer chip development. I would also say your wrong there again.

      As for not going into great detail on microprocessor design and implantation I didn't feel it was all that necessary to the conversation when my point was that "small" isn't always "better", there are many more factors to consider, and that it also makes the big assumption that you are going to continue to do the exact same thing that you have been doing for decades, which I thought to be a foolish assumption.

      Also I'm not sure the problem is so much a delay as it is with certainty of change. The smaller you get, and less current you use, the harder it is to tell if a gate is open or closed. It becomes fuzzy. If it becomes too fuzzy, it cannot be detected, and then unusable. You have to be able to clearly define when a gate is totally open or totally closed, and if you can't do that, the chip will not operate, or will not operate as quickly.

      Architecture and memory, and type of memory, also play a role etc... but I was originally talking about the fundamentals (and how they might differ) of chip design without going into a great amount of detail.

  35. Don't forget to clean your room... by __aaasvk1266 · · Score: 1

    Hopefully, I'm not duplicating someone's post... Being able to cut a tighter line is one thing. Being able to do it on a "making license plates" scale is something else. As you move increase the density of what is being packed on the chip, you have to be able to increasingly control for smaller and smaller particles. Each jump in Clean Room Technology is neither easy, nor inexpensive. For details, and a whole lot more related material:

    http://www.lowtechmagazine.com/2009/06/embodied-energy-of-digital-technology.html

  36. less bloat ware...more efficient processors.... by Anonymous Coward · · Score: 0

    Faster processors are fine for servers and research...but as a consumer I'd prefer to have programs that don't require 100s of MB or RAM, Operating Systems that don't require GBs of space....so use this shrunken die to make my stuff smaller and cooler to the touch...and have it run longer....and write some freakin efficient software so I don't need more RAM every few yrs.

  37. Neutronic Degenerate Matter by jameskojiro · · Score: 1

    This would work better, of course mining Neutron stars for it would be very hard. But you could really shrink down those chips...

    --
    Tsukasa: All I really want, is to be left alone...
  38. It's hard writing software to keep up with the HW by garyebickford · · Score: 3, Funny

    Folks don't often realize how much work we software writers go through to write this big, complex, core-eating software. Back in the day with 8-bit 500 KHz CPUs we could write a simple 1000-iteration loop with a bit of code in it, and it might lag the CPU for a whole second. Now with these fast processors we have to go through all kinds of hoops to use up all those cycles! Building languages on top of languages, interpreted languages, all kinds of extra error checking (error checking can often take 80%-90% of the cycles and code), objects on top of arrays on top of pointers on top of objects ... you get the idea. SOMEBODY has to make the software to use up all those cycles.

    It's a dirty job, but somebody has to do it!!!

    WE CAN NOT LET THE HARDWARE PEOPLE WIN!!! For every added processor, every bump in Hz, we WILL come up with a way to burn it! Soon we will embark on the new 3D ray-traced desktop - THAT will keep the HW folks busy for a while!!! And (don't tell anybody) soon we will establish the need for full time up-to-date indexing of everything on the LAN. Of course, that could be done by one machine, but if we all do it independently on each machine, that will burn another whole 2GHz CPU's worth of cycles.

    Our goal and our motto: "A computer is nothing but a very complicated and expensive heater." :D

    --
    It's easier to be a result of the past, but more fun to be a cause of the future! http://www.spacefinancegroup.com/
  39. Re:It's hard writing software to keep up with the by arkenian · · Score: 1

    where are my mod points when I need them? Thanks, I LOLed this, and needed that. Not to mention its true in a sick way...

  40. Re:This is what reversible computing is for, right by ChrisMaple · · Score: 1

    I was curious about this, and looked into it (about ten years ago). The results I got implied that an inductor Q better than 2 wasn't possible for normal processing at the transition times of interest, and the cost was poorer layout due to the space the inductor would consume on a metal layer. Overall, there might be a benefit, but it would be small and difficult to design in.

    --
    Contribute to civilization: ari.aynrand.org/donate
  41. Just a thought by Anonymous Coward · · Score: 0

    But why arent we running our OS's on Video cards yet?
    GTX 470:
    Video Memory: 1280MB
    Memory Type: GDDR5
    Memory Interface: 320-bit
    Stream Processors: 448
    Core Clock: 625 MHz
    Memory Clock: 3402 MHz
    Shader Clock:1250 MHz

    I refuse to believe there isn't a group of linux nerds that cannot port the kernal into some Vector form to run on my Video card.
    Just saying...

  42. Power density by Anonymous Coward · · Score: 0

    Working with chips for 100GB long-haul optical transport, we're already at the stage where we can't actually fill the die with active gates because of power dissipation.

    The basic problem is that power efficiency (MIPS/mW) no longer scales with the square of gate length like it used to, because supply voltage no longer falls proportionally to gate length.

      -- 0.35um chips ran off 3V supplies
    -- 0.18um chips ran off 1.8V supplies, same power density
    -- 40nm chips run off 0.9V supplies, should be 0.4V for continued voltage scaling so power (CV^2) is already 5x higher than it "ought" to be

    We've already managed to design some high-speed circuits with 10W/mm2 peak power dissipation; if all circuits were like this a 300mm2 die would dissipate 3kW...

  43. Quantum computing is the key?!? by Anonymous Coward · · Score: 0

    http://www.newsdesk.umd.edu/bigissues/release.cfm?ArticleID=2190

  44. You don't need smaller. by Anonymous Coward · · Score: 0

    You need to go into 3 dimensions. You need to roll up the silicon into a scroll and circulate cooling fluid between the layers. As you roll the layers into the tube you soldier connections between the layers.

    Or you need to make a computing cube, which is a few mm squared made up of hundreds of layers of silicon and circuits.