Slashdot Mirror


Where's My 10 Ghz PC?

An anonymous reader writes "Based on decades of growth in CPU speeds, Santa was supposed to drop off my 10 Ghz PC a few weeks back, but all I got was this lousy 2 Ghz dual processor box -- like it's still 2001...oh please! Dr. Dobbs says the free ride is over, and we now have to come up with some concurrency, but all I have is dollars... What gives?"

36 of 868 comments (clear)

  1. Heat is the problem by CPNABEND · · Score: 4, Insightful

    Multi-processing is the way to go. We need to do that to help heat dissipation...

    --
    My wife doesn't listen to me either...
    1. Re:Heat is the problem by WaZiX · · Score: 5, Insightful

      The CPU spends as much as 75% of its time idle because its waiting patiently for the memory to give it something to do. With Systems only delivering information at a max of 1 Ghz and processors going up to almost 4 times as fast... Studies also show that they could in term be able to squeeze 20 Ghz out of wires as long as 20 inches (and only by 2010 will we be able to achieve that), but that would only be sufficient for the 32 nanometer generation of microships (and we're quite ahead of that)... So i think the future resides in optical connections within the motherboard, allowing processors to finally... well... process ;-)

    2. Re:Heat is the problem by dsginter · · Score: 4, Interesting

      Multi-processing is the way to go. We need to do that to help heat dissipation...

      So, you think that using multiple iterations of an inherently power-hungry technology will somehow solve the power problem? While, certainly, we could back off clock speeds with multi-processing and reduce heat considerably, but, people always want the cutting edge so the demand to "crank it up" would still be a profitable venture, thus pressuring the price of the lower-end stuff.

      Look at page 8. Processors are approaching the heat density of a nuclear reactor. Silicon is dead. We'll need something else if we want more clock cycles (or perhaps a new computing paradigm... something "non-Von Neumann).

      --
      More
  2. Don't complain. by inertia187 · · Score: 5, Funny

    People in Soviet Russia, however, appear to be afflicted with amusing juxtapositions of the aforementioned situation.

    --
    A programmer is a machine for converting coffee into code.
  3. Engineering within limits brings great results by skrysakj · · Score: 5, Insightful

    I remember the old days, when programmers nudged every
    single bit of speed and capability out of the machines they had.
    When computer engineers, faced with limits, still made magic
    happen.

    I hope this ushers that habit back into the profession. We have a lot of great technology, right now, let's find a better way to use it and make it more ubiquitous.

    1. Re:Engineering within limits brings great results by arkanes · · Score: 5, Insightful

      Er... yes? Do you actually REMEMBER how you used a computer back then? On my Windows 95 machine with 8 megs of ram swapping was slow enough that effective multitasking was out. On my modern spiffy computer I keep use multiple instances of enormous memory hogs of applications (that do stuff that nobody would have even considered adding to an application in 1995, like real-time analysis of a 50 meg C++ code tree), dozens of browser windows, all without flinching. At the article says, it's capability increase rather than absolute performance increase - there is no need whatsoever for a word processor that's faster than you can type. Speaking of that, in 1990 it was really easy to type faster than the Macs in our computer lab could keep up. So yes, MY applications certainly feel faster than they did 5 or 10 years ago. If yours don't then you either a) don't actually do anything that exploits the new power of your computer and your processor, and therefore don't need it or b) are looking at the past through rose colored glasses and don't remember when it took a weekend to run a compile, rather than it happening incrementally in the background without you even noticing.

    2. Re:Engineering within limits brings great results by gardyloo · · Score: 5, Informative

      Ah, yes.
      It seems that we need to review
      The Story of Mel.

      I'll post it here from several places,
      So that the good people of /.
      (and the other people of /.)
      Don't wipe out a single server (yeah, right!)

      http://www.cs.utah.edu/~elb/folklore/mel.html
      http://www.wizzy.com/andyr/Mel.html
      http://www.science.uva.nl/~mes/jargon/t/thestoryof mel.html
      http://www.outpost9.com/reference/jargon/jargon_49 .html

      and, of course, many other places.

    3. Re:Engineering within limits brings great results by grumbel · · Score: 4, Interesting

      ### The limits are high enough now to not care.

      The throuble is that this is assumption is wrong. The computers would in theory be fast enough to not care about optimization all over the place, the throuble is that a lot of bad programming doesn't result in just linear decrease of speed. If I use linear lookup instead of a hash-table, speed will go down, quite a bit more down then the amount of speed of the CPU increases over time.

      Simple example, Gedit, an extremly basic text-editor takes 4-5 seconds to load on a 1Ghz Athlon, MSDOS edit on the other side on 386er started in a fraction of a second. From a feature point of view both do basically the same. Gedit for sure has some more advanced rendering and GUI and isn't a text-mode application like MSDOS edit, however shouldn't it be possible with todays CPUs which are quite a bit faster then back then to have an application that has better rendering then text-mode, but still be at least as fast or faster then back then?

  4. Least of your worries by dunsurfin · · Score: 5, Funny

    According to most predictions we were meant to be enjoying lives of leisure by this point - working a 5-hour week in the paperless office, and driving to work in our hovercars.

  5. Re:Asymptotic by BrianHursey · · Score: 4, Insightful

    True we have found limits to materials hence we need to think out of the box and find new materials.

    --
    Linux is like a teepee. It has no windows, no gates, and there's an Apache inside.
  6. A Good Thing? by rdc_uk · · Score: 5, Insightful

    To my mind it _might_ be a good thing if the rampant speed-advance slowed (a lot).

    Consider:

    We might get some return to efficient coding being the norm, instead of writing systems anyhow and throwing more/faster hardware at it until it runs acceptably (Microsoft; its you I'm looking at!)

    Your (and your business') desktop machine might _not_ become obsolete in no more than 2 years, and mmight continue in useful service as something more sensible than a whole PC doing the job of a router...

    Processor designers might spend more time (i know they already spend some) on innovating new ideas, rather than solving the problems with just ramping up clock speeds.

    Cooling/Quietening technology might have a snowball's chance in hell of catching up with heat output?

    (and the wild dreaming one)
    Games writers might remember about gameplay, rather than better coloured lighting...

    1. Re:A Good Thing? by nine-times · · Score: 4, Insightful
      Processor designers might spend more time (i know they already spend some) on innovating new ideas, rather than solving the problems with just ramping up clock speeds....Games writers might remember about gameplay, rather than better coloured lighting...

      These both relate to a trend in the market that I believe we're seeing. Consumers are finding that their "old" computers from 2 years ago are still doing their jobs. When I have a 2Ghz Dell that I use for web surfing, word-processing, and e-mail, there's no benefit to upgrading to the newest 3.4 Ghz Dell. Though there's a hefty speed bump in there, most users will never know the difference.

      Therefore, developers/manufacturers are being forced to focus on things like usability and features. They're making their products smaller and more efficient, easier to use, and making them fit transparently into the user's life better. They're focusing on the whole "convergence" idea.

      Instead of people spending money on RAM upgrades, the money is going to smaller/lighter/better digital cameras, iPods, and home theater technology. In short, instead of seeing the same box being rolled out every year with better stats, we're seeing new boxes coming out every year with pretty much the same stats, but better designed boxes-- boxes that are actually more useful than last year's model, and not just faster.

      I, for one, hope the trend continues.

  7. I've always wondered by harks · · Score: 4, Interesting

    Why the size restraints on processors? Could a processor be made twice as fast if it could be made twice the size? When we hit the limit on how small transistors can be made, could processors continue to increase in speed by making them larger? I see no need why computers need to keep a processor size to two inches square.

    1. Re:I've always wondered by mikeee · · Score: 4, Informative

      No, making it bigger will make it slower. Current digital systems are mostly "clocked" (they don't have to be, but that gets much more complicated), which means that signals have to be able to get from one side of the system to the other within one clock cycle.

      This is why your CPU runs at a faster speed than your L2 cache (which is bigger), which runs at a faster speed than your main memory (which is bigger), which runs at a faster speed than memory in the adjacent NUMA-node (which is bigger), which runs faster than the network (which is bigger),...

      Note that I'm talking about latency/clock-rate here; you can get arbitrarily high bandwidth in a big system, but there are times when you have to have low latency and there's no substitute for smallness then; light just isn't that fast!

    2. Re:I've always wondered by ZorbaTHut · · Score: 4, Informative

      The problem with that is light speed. Transmitting a lightspeed signal across one centimeter takes about 3.3*10^-11 seconds - which sounds like a lot, until you realize that a single CPU cycle now takes about 3.3*10^-10 seconds. And I don't even know if electricity travels at true lightspeed or at something below that.

      Another problem, of course, is heat - if your 1cm^2 CPU outputs 100w of heat, a 10cm^2 CPU is going to dump 1000w of heat. That's a hell of a lot of heat.

      A third problem is reliability. Yields are bad enough with the current core sizes, tripling the core sizes will drop yield even further.

      And a fourth problem is what exactly to *do* with the extra space. :) Yes, you could just fill it with cache, but that still won't give you a computer twice as fast for every twice as much cache - MHz has nothing to do with how many transistors you can pile on a chip. (Of course, you could just put a second CPU on the same chip . . .)

      --
      Breaking Into the Industry - A development log about starting a game studio.
    3. Re:I've always wondered by Tacky+the+Penguin · · Score: 4, Informative

      The problem with that is light speed.

      Light speed is a big issue, but so is stray capacitence and inductance. A capacitor tends to short out a high frequency signal, and it takes very little capacitence to look like a dead short to a 10 GHz signal. Similarly, the stray inductance of a straight piece of wire has a high reactance at 10 GHz. That's why they run the processor at high speed internally, but have to slow down the signal before sending it out to the real world. If they sent it out over an optical fiber, things would work much better.

      And I don't even know if electricity travels at true lightspeed or at something below that.

      Under ideal conditions, electric signals can travel at light speed. In real circuits, it is more like .5c to .7c due to capacitive effects -- very much (exactly, actually) the same way a dielectric (like glass or water) slows down light.

      --Tacky the BSEE

  8. Re:Well Moore's Law is not a law... by stupidfoo · · Score: 4, Informative

    Moore's "law" has nothing to do with Hz.

    From webopedia
    (môrz lâ) (n.) The observation made in 1965 by Gordon Moore, co-founder of Intel, that the number of transistors per square inch on integrated circuits had doubled every year since the integrated circuit was invented. Moore predicted that this trend would continue for the foreseeable future.

  9. Leave Moore's law out of this, please by Raul654 · · Score: 5, Informative

    Moore's law has nothing to do with processor frequency. It says that semi-conductor capacity doubles every 18 monthsm, not frequency. (With the corollary that there is no appreciable change in price). As we all know, semi-conductor capacity is roughly proportional to speed, so saying processor speeds double every 18 months is not quite wrong, just a little inaccurate. On the other hand, saying that we're not seeing 10 ghz processors, so Moore's law is broken is wrong.

    --


    To make laws that man cannot, and will not obey, serves to bring all law into contempt.
    --E.C. Stanton
  10. Two birds, one stone by Tackhead · · Score: 5, Funny
    > According to most predictions we were meant to be enjoying lives of leisure by this point - working a 5-hour week in the paperless office, and driving to work in our hovercars.

    Judging from these pictures of the Intel retail boxed heatsink for the Pentium 4 560J (3.6 GHz), by the time we get 10 GHz PCs, the hovercar problem will take care of itself.

  11. Re:Asymptotic by abigor · · Score: 4, Funny

    Well, not unless he's able to leverage it, because it's impacting the story we have to tell.

  12. Re:We need a faster bus by mirko · · Score: 5, Funny

    Maybe the guy who promised him a 10GHz PC was counting in binary ?

    --
    Trolling using another account since 2005.
  13. Re:Well Moore's Law is not a law... by jj_johny · · Score: 4, Insightful
    No, Moore's law was about price performance not about absolute performance. If you look at the cost of a PC it has consistently gotten better performance while decreasing in price. Nearer to the beginning of the PC revolution it was all performance inprovement and very little price drop. Then in the early 90s it was kind of balanced. Then the 2000 to 2004 was all about the machines getting cheaper with performance nudging along.

    But now even you cheapest PC covers most users needs. So the CPU designers will continue to inovate but they will find that people will be able to keep their PCs and other electronics longer. Fundementally, the CPU business will start loosing steam and slow down. When people don't need to get new machines, they won't. The precieved premium for the high end products is getting less and less.

  14. Re:Asymptotic by CmdrGravy · · Score: 5, Funny

    I think it's going to take a lot of imagineering to fully appreciate the tectonics of a potential paridigm shift.

  15. GaAs and Relational Calculus by Baldrson · · Score: 4, Interesting
    First of all, when DARPA decided to directly back specific technologies such as Danny Hillis' "Connection Machine" while supercomputer sales were flagging, they corrupted the market-driven support for supercomputing innovation. As a result just when Seymour Cray had a viable production line for GaAs cpus there was virtually zero market demand for the technology. The lower capacitance as well as higher mobility of the electrons of his version of GaAs technology weren't the sole benefits -- it was also about a factor of 10 cheaper to capitalize the fabrication facilities.

    Whenever the government "picks winners" rather than letting nature pick winners, the technologists and therefore technology loses.

    (Now that Cray is dead, according to the supercomputing FAQ, "The CCC intellectual property was purchased for a mere $250 thousand by Dasu, LLC - a corporation set up and (AFAIK) wholly owned by Mr. Hub Finkelstein, a Texas oilman. He's owned this stuff for five years and hasn't done anything with it.")

    Secondly, as I've discussed before both operating system and database programming are awaiting the development of relations, most likely via the predicate calculus, as a foundation for software. Both are essentially parallel processing foundations for software.

    This feeds into quantum computing quite nicely as well, as relations are not just inherently parallel, but are parallel in such a way that they precisely model quantum software.

  16. Re:Asymptotic by Wordsmith · · Score: 4, Funny

    Mods don't find marketspeak funny, apparently.

  17. Re:Asymptotic by lucifuge31337 · · Score: 5, Insightful

    Without a major breakthrough, which isn't something I'd bet on, I'll agree that we are very close to the limits of silicon based CPUs.

    Remember when 9600 baud was close to the limit of copper? Then 33.6. Then they changed how the pair was used, and made 128K ISDN. Then they changed it again and we're getting 7-10 MB DSL....sometimes even faster depending.

    I find it hard to say the we're close to the limits of any technology in the computer/telecom field. Someone always seems to find a new way around it.

    --
    Do not fold, spindle or mutilate.
  18. Concurrent Applications are not The Answer by smug_lisp_weenie · · Score: 5, Interesting

    There is one law in computer programming that is even more certain than Moore's Law: Over time, the user is going to do less work for the computer and the computer is going to do more work for the user.

    Remember back when users had to wait in line in front of a terminal to run their punchcards through the mainframe? Back then, human time was cheap and computer time expensive. Nowadays the user's time is paramount.

    Multithreaded programming breaks this law: It is hard to do multithreaded programming- Humans just don't think that way very well. To do it in a way that an arbitrary program (i.e. not a ray tracer) can see consistent performance gains in a multi-CPU environment is almost PhD-level hard. Making single-threaded software is already a major undertaking and anyone thinking that, in general, they should start designing all their programs as fundamentally concurrent programs is going to fall behind their competition due to other factors (security, features, etc.).

    Instead, the only way concurrent programming is going to play a major role for the majority of software, I believe, is at the compiler and OS levels: The OS and compiler designers are going to have to do their utmost to transform single-threaded software to perform optimally in a multi-CPU environment- These folks are going to have to take up the slack that the slow CPUs clockspeeds are causing in terms of limiting the speed of Software- Concurrent programming at the application-level is only going to play a minor role in this, in my opinion.

  19. Re:Asymptotic by rizzo · · Score: 4, Funny

    Thankfully we've got some proactive synergies and tremendous upside.

    --

    "More organs means more human." - Zim

  20. GaAs??? GaAs is material of the future... by PaulBu · · Score: 4, Interesting

    ... and will always be! ;-) I think I first read this qoute sometimes in late 80s/early 90s, and it is still true. You know why? Ever looked at power dissipation specks of even the simplest GaAs chips? You would not want to build a processor out of those, Cray tried with Cray 4 and failed... ;-(

    superconductors is the way to go for highest speeds/most concentrated processing power, due to extremely small power dissipation and extremely high clock frequencies (60 GHz for logic is relatively easy right now), but the problem is that after someone invests $3B in a modern semiconductor fab they do NOT want to build a $30M top-of the line superconductor fab to compete with it. IBM would be a good candidate for this, but they got burned on superconductor computer project back in 80s and would not touch it with 10 foot pole now, though both logic and fab has changed dramatically since then.

    Disclosure: on my day job I do design III-V chips, and I used to design superconductor chips up until recently, now trying to push that technology forward is more of a night job for me... ;-)

    Paul B.

  21. Intel is to blame for this absurdity by bigtrouble77 · · Score: 5, Interesting

    This was spewed from Intel in 2002:

    "First, by switching to the Pentium 4 architecture, Intel can drastically boost the clock speed. The old server Xeon topped out at 1.4GHz. The new one debuts at 1.8GHz, 2GHz and 2.2GHz, and will eventually pass 10GHz, she said."
    http://news.com.com/2100-1001-843879.html

    I can't find the exact quote and article, but another Intel exec/rep stated that this goal would be achieved by 2006.

    Well, it's 2005, the P4 has topped out at 3.6ghz and has been discontinued because Intel has determined that the P4 arcitecture is streached to the limit.

    Bottom line is that we should be expecting a 10ghz processor soon because Intel brazenly stated that they would produce one. Whenever they do make these statements the AP drools over the story, stock prices jump and I'm sure investors get excited.

    Instead, their next gen processor is a 2ghz Pentuim M dothan. Intel should be ashamed of themselves for lying to the public and should be investigated for inflating their stock value though fictional claims about their processor technology.

  22. Re:Asymptotic by Waffle+Iron · · Score: 5, Informative
    Remember when 9600 baud was close to the limit of copper?

    That was never the limit of copper. It was the limit of voiceband phone lines, which have artificially constrained bandwidth. Since voiceband is now transmitted digitally at 64Kbs, that's the hard theoretical limit, and 56K analog modems are already asymptotically close to that.

    If you hook different equipment to the phone wires without the self-imposed bandwidth filters, then it's easy to get higher bandwidth. Ethernet and its predecessors has been pushing megabits or more over twisted pair for decades.

  23. Re:Asymptotic by arivanov · · Score: 5, Insightful

    No,

    The lack of breakthrough will be due to something entirely different.

    So far we have been exploiting the fruits of fundamental material science, physics and chemistry research done in the 60-es (if not earlier), 70-es and to a small extent in the 80-es. There has been nothing fundamentally new done in the 90-es. A lot of nice engineering - yes. A lot of clever manufacturing techniques silicon of insulator being a prime example - yes. But nothing as far as the underlying science is concerned.

    This is not just the semiconductor industry. The situation is the same across the board. The charitable foundations and the state which used to be the prime source of fundamental research funding now require a project plan and a date when the supposed product will deliver a result (thinly disguised words for profit). They also do not invest into projects longer then 3 years.

    As a result noone looks at things that may bring a breakthrough and there shall be no breakthroughs until this situation changes

    --
    Baker's Law: Misery no longer loves company. Nowadays it insists on it
    http://www.sigsegv.cx/
  24. Embedded Systems by crimethinker · · Score: 4, Interesting
    We're already back to the "old days" in the embedded systems field, if we ever left. When you have to squeeze every bit of life out of a battery, you make sure your code doesn't piss away processor cycles. If the system calls for an 8-bit processor and a certain network daemon, you make the daemon run on the 8-bit processor, even if it was originally written for a 32-bitter. (then you whack the salesweasel upside the head for promising the moon to the customer)

    If you crave the challenge of making tight, efficient code, sometimes with very little under you but the bare chip itself, then embedded systems might be the place for you.

    cue the grumpy old man voice: "Why back in my day, we didn't have 64-bit multi-core chips with gigabytes of memory to waste, no sir, we had to write in assembly code for 8-bit processors, and WE LOVED IT!"

    -paul

    --
    Pistol caliber is like religion: everyone has their favourite, and theirs is the only right choice.
  25. Re:Asymptotic by halivar · · Score: 4, Funny

    If we put our brains together synergistically, and I'm sure we can reach a solution.

  26. Re:Asymptotic by scovetta · · Score: 4, Funny

    For God's sake, please stop the business-speak!

    --
    Wer mit Ungeheuern kämpft, mag zusehn, dass er nicht dabei zum Ungeheuer wird. --Nietzsche
  27. Actually, 56k is the hard limit by Sycraft-fu · · Score: 4, Informative

    Analogue lines aren't like DS-0 lines, which have a seperate control channel, the control is "bit robbed" from the signal. They take out 8kbps for signaling, giving 56k effective for encoding. That's why with ISDN there is talk of B and D channels. For BRI ISDN you get 2 64k (DS-0) B (bearer) channels that actually carry the signal. There is then a 16k D (data) channel that carries the information on how to route the B channels.

    That's also why IDSL is 144k. The total bandwidth of an ISDN line is 144k, but 16k is used for circut switching data. DSL is point-to-point, so that's unnecessary and the D channel's bandwidth can be used for signal.

    So 56k is as good as it will ever get for single analogue modems. I suppose, in theory, this could be changed in the future, I suppose, but I find that rather unlikely given that any new technology is likely to be digital end to end.