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?"

868 comments

  1. Asymptotic by dsginter · · Score: 3, Interesting

    We've found the limits of silicon and hard drives and they are being approached asyptotically. Relax...

    --
    More
    1. 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.
    2. Re:Asymptotic by justforaday · · Score: 3, Funny

      Are you referring to some sort of paradigm shift or something?

      --
      I'll turn into a supernova and burn up everything. Well I'll turn into a black little hole and you'll turn into string.
    3. Re:Asymptotic by Anonymous Coward · · Score: 0

      Who is this "we" you are talking about? Are you working in semiconductor business?

    4. 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.

    5. Re:Asymptotic by Zocalo · · Score: 3, Informative
      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. Strained Silion and Silicon on Insulator are effective stop gaps, but multi-core and possibly switching to something like Gallium Arsenide are the most likely ways forward for greater processing power at the moment.

      Hard drives however? Some of the areal densities that are working in R&D labs are significantly denser than what we have now and will allow for plenty of capacity growth if they can be mass produced cheaply enough. Sure, we're approaching a point where it's not going to be viable to go any further, but we're not going to arrive there for a while yet. There is also the option of making the platters sit closer together so you can fit more of them into a drive of course. If you really want or need >1TB on a single spindle then I think you'll need to wait just a few more years.

      --
      UNIX? They're not even circumcised! Savages!
    6. Re:Asymptotic by Anonymous Coward · · Score: 0

      Yeah, he needs to get pro-active about developing new synnergy!

    7. 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.

    8. Re:Asymptotic by codeguy007 · · Score: 1

      Umm they haven't yet found the limits to Hard Drives. Hard Drives are the new chips. They are advancing and capacity and miniturization at an impressive rate.

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

      Mods don't find marketspeak funny, apparently.

    10. Re:Asymptotic by Anonymous Coward · · Score: 0

      I see all the mods are from the marketing department today. Either that or on crack... again.

      Com'n on mods, this is FUNNY!

    11. 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.
    12. Re:Asymptotic by ConceptJunkie · · Score: 3, Funny

      Worse, they think it's insightful.

      --
      You are in a maze of twisty little passages, all alike.
    13. Re:Asymptotic by enigmals1 · · Score: 1

      Like lasers on CPU's? :D

    14. Re:Asymptotic by Anonymous Coward · · Score: 0

      exactly.
      Now! who wants some tofruity!?

    15. Re:Asymptotic by Strange+Ranger · · Score: 2, Funny

      Like sands through the hourglass so go the chips on our dies. Thus, in order to birth a silcon sea change we need to get down to the granular level with the design schema.

      --

      Operator, give me the number for 911!
    16. Re:Asymptotic by Thud457 · · Score: 2, Insightful
      " I see all the mods are from the marketing department today. Either that or on crack... again."

      Those two conditions are not mutally exclusive. Actually, they appear to be strongly correlated.

      --

      the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

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

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

      --

      "More organs means more human." - Zim

    18. Re:Asymptotic by fshalor · · Score: 1

      And some of it's on the /. front page right now... Speaking of "image"ineering....

      Laser on die will rule the world. Until we come up with DNA computers that work.

      Then again, laser tech is probably the missing piece to being able to make the dna matrices

      --
      -=fshalor ::this post not spellchecked. move along::
    19. Re:Asymptotic by TheGavster · · Score: 1

      What I want to see is a 5-1/4 inch, full-height drive with modern areal density. Should hit the multi-terabyte range easy. Sure, you'd need the chain down the 15K rpm SCSI version, but I think its worth it.

      --
      "Because Science" is one step from "Because old book". Try "Because of my experiment testing my falsifiable assertion".
    20. Re:Asymptotic by Anonymous Coward · · Score: 0

      stop, stop, please, for the love of dog, stop!

    21. Re:Asymptotic by netwiz · · Score: 2, Informative

      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.

      perhaps not, but things are getting really dicey WRT silicon processes. The lates process shrink to 90nm really hurt, and required bunches of tricks to make it work. Specifically, thermal dissipation is a big problem, as when you shrink chips, they get hotter, and require more idle power to make them work. This increases the total thermal power you've got to dissipate, and you've reduced the surface area with which to do so.

      Leakage power is another problem. Sure, that 3.6GHz Prescott you've got there has a max dissipation of 110watt at full tilt, but it still consumes something like 53w doing nothing! That's pretty bad, and there's absolutely no fix for that. Physics and chemistry say so, and it only gets worse the smaller the transistors become. So 65nm will be a real bitch...

    22. Re:Asymptotic by Zocalo · · Score: 2, Insightful
      Yes, there's certainly a possibility that there may be a breakthrough, I just don't see it happening for several reasons. First and foremost we have the laws of physics; you just can't make the traces on the silicon substrate much thinner and still know for sure what's going on. This is something that strained silicon has alleviated a little, but without further size reductions then more GHz equates to more heat.

      My other reasons are a little more subjective, but are largely to do with the fact that both AMD and Intel are investing heavily in developing multi-core CPUs. In Intel's case this has involved the very public scrapping of a promised CPU and a drastic revamp of its roadmap. While breakthroughs in CPU design have come from academia and other companies, the vast majority have come from Intel and IBM. However, neither are investing the R&D in ramping clock speeds ever higher and are focussing on multi-core designs instead.

      Hence my original statement: based on what we current know about silicon based CPU design, we are at (or very close to) the limits of what is possible. Further R&D or a breakthrough might push that a little or even a significant amount higher, but without the massive R&D efforts of IBM and Intel, the chances of this happening are slim. Also, if the market does start to shift toward multi-core designs which seems very likely, then the inclination of people to look into better wats of doing things in the old way is likely to be reduced further.

      --
      UNIX? They're not even circumcised! Savages!
    23. Re:Asymptotic by Anonymous Coward · · Score: 0

      I have read about some R&D where we will utilize light to transfer data. There is a company right now that has developed a material to build boards and circuitry that can carry data via light through a system. That is probably the next route we will see in system development.

      At this point I highly doubt we will ever see biometric computer systems, As they require DNA matricies. we all know to well how so many people are up in arms about stem cell research just imagine using DNA to build a cpu core or a motherboard.

    24. 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.

    25. Re:Asymptotic by sremick · · Score: 1

      Yes, silly atoms... they are so Big-Bang-era-ish. Heh. C'mon... this is 2005!

      If we could just build chips and traces out of something smaller, we'd be set. ;)

    26. 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/
    27. Re:Asymptotic by Casca · · Score: 3, Funny

      Don't forget the symbiosis present with VARs and results oriented customers.

      --
      Casca
    28. Re:Asymptotic by KDan · · Score: 1

      We, us... we're all together in this synergistic orgy of proactive brainstorming.

      Daniel

      --
      Carpe Diem
    29. Re:Asymptotic by Anonymous Coward · · Score: 0

      What if I stood in a box while I thought out of the box? Would I have an out of box experience?

    30. Re:Asymptotic by Anonymous Coward · · Score: 0

      Until we come up with DNA computers that work."

      DNA computers will give a whole new meaning to "My computer has a virus".

      I really don't want to catch AIDS from my motherboard (future FOX News report?).

    31. Re:Asymptotic by macrom · · Score: 1

      What ever happened to the idea that man-made diamonds could be the future of computing? I know there was a Wired article a while back regarding this (yeah, I know that Wired can be the tabloid of the tech industry) saying that cheaply made diamonds could push processor speeds way faster due to better heat dissipation. Is this idea still way off or is it more the pipe dream of a huxter wishing to get rich?

    32. Re:Asymptotic by AJWM · · Score: 3, Insightful

      Mod that +1 insightful.

      I might also throw in the possibility that, since the end of the Cold War, there has been very little incentive for governments, etc, to back fundamental research that might (a decade later) lead to radically new technologies. Governments like the status quo, they like the future to be predictable. Fundamental research (except perhaps in really esoteric areas like cosmology or areas with practical benefits for them like medicine) scares the willies out of the people in power -- it might upset their apple cart.

      --
      -- Alastair
    33. Re:Asymptotic by cakefool · · Score: 1

      Have you priced up small atoms lately?!

    34. Re:Asymptotic by dschoettlin · · Score: 1, Funny
      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.

      We haven't been able to develop new "underlying science" because the aliens haven't returned. Duh.

    35. Re:Asymptotic by halivar · · Score: 4, Funny

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

    36. Re:Asymptotic by GigsVT · · Score: 1

      Well, there's always the potential to move to BJT technology and away from FET. FETs in saturation mostly just use power when you change state (i.e. clock dependant), but BJTs will use a relatively constant amount of power at any frequency.

      It's just the normal ecosystem of things, when one method starts to require so many hacks that it's no longer practical, it spurs us to look at alternate methods we may have discarded in the past for whatever reasons.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    37. Re:Asymptotic by null_session · · Score: 0

      Remember when 9600 baud was close to the limit of copper? Then 33.6.

      9600 baud is the limit of copper, and we haven't crossed it. The 33.6 is BPS or bits per second. Every speed increase over 9600 was obtained by compression (this is why you don't hear of a 33.6k baud modem).

    38. Re:Asymptotic by bdcrazy · · Score: 2, Funny

      Results oriented customers.... vs what? the customers that don't really care and will buy anything? oh, i get it. n/m me.

      --
      Tonights forecast: Dark. Continued dark throughout most of the evening, with some widely-scattered light towards morning
    39. 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
    40. Re:Asymptotic by AJWM · · Score: 2, Funny

      Sure, you'd need the chain down the 15K rpm SCSI version,

      Heh, reminds me of those reports of possible antigravity effects with spinning superconductor magnets. Do you suppose if you manage to write the right bit pattern to every sector on the drive you could get it to lift off?

      --
      -- Alastair
    41. Re:Asymptotic by Tanktalus · · Score: 1

      I'm not saying you're wrong - while I'm sure things are always much more complex than a couple lines can say, you've probably boiled down a significant portion of it. I'm just going to say it's unfortunate. What they're not realising is that just because they aren't pursuing fundamental research doesn't mean someone else isn't. And that will unbalance the status quo - and not in their own favour, usually.

    42. Re:Asymptotic by Anonymous Coward · · Score: 0
      We've found the limits of silicon

      Pamela Anderson ?

    43. Re:Asymptotic by null_session · · Score: 1

      Sorry, shouldn't have said "copper" 9600 baud is the limit of the PSTN

    44. Re:Asymptotic by boaworm · · Score: 0, Redundant

      No no.. the lazers will be attached to their friggin headz ! :)

      --
      Probable impossibilities are to be preferred to improbable possibilities.
      Aristotele
    45. Re:Asymptotic by Junior+J.+Junior+III · · Score: 1

      Why? Silicon is cheap, and any replacement material is bound to be more expensive. Most users' needs are far exceeded by 2+GHz processors. There's some people who could use faster procs, but they're pretty rare, and many of them are happy enough with SMP and clustering.

      --
      You see? You see? Your stupid minds! Stupid! Stupid!
    46. Re:Asymptotic by CODiNE · · Score: 1

      I think this can be achieved through the actualization of flux-capacitors running at a sustained 1.21 Jigawatts.

      --
      Cwm, fjord-bank glyphs vext quiz
    47. Re:Asymptotic by Tanktalus · · Score: 2, Informative

      Just to expand a bit on this. Not much - I'm going to grossly oversimplify this. Each "baud" is merely a change in signal. However, it is an analog change, not a digital change. These signals do not need to be either "0" or "1". They can be "2", "3", "4", etc. (there is a limit here, too, I'm sure). 33.6k is merely 3.5 times 9.6k, so we have amplitudes of 0 through 3 (4 discrete values, one of every two signals has an extra parity bit). Using 6 amplitudes (0-5), we get 57.6k, or, minus the parity, 56k. But we're still transmitting at 9600 baud.

      Of course, that only matters to geeks. To the rest of the world, baud is irrelevant. It's how fast the pr0n downloads that counts.

    48. Re:Asymptotic by stienman · · Score: 1
      The real problem is the submitter doesn't know how to predict a trend.

      Based on decades of growth in CPU speeds, Santa was supposed to drop off my 10 Ghz PC a few weeks back

      Using the highest available clock speed at each of Intel's (and if faster, AMDs) launches, we should be reaching 4GHz now, not 10GHz.

      Year Processor Speed MHz
      1978 8086 8
      1982 80286 12.5
      1985 80386 20
      1989 80486 25
      1993 Pentium 66
      1994 Pentium 100
      1995 Ppro 200
      1997 PII 300
      1998 PII 333
      1999 Athlon 750
      2000 PIII, Athlon 1000


      So we are at close to where we should be. Just because you didn't get the fastest this year, doesn't mean that it's not available.

      Secondly, Intel was the one to create the MHz monster and myth. Now they are dealing with the problems. The true problem is that people need to have a single metric that tells them the performance of a given object, whether it's HP, BTU, Square feet in a home, and clock speed in a computer.

      Now they are going to have to go back to the drawing board and come up with a new metric. MIPS is not adequate, even SPECInt isn't good enough.

      Dual core and other processing tricks are going to be needed.

      The 80186 flopped partially because it was not fully backwards compatible. Intel learned that lesson long ago, and was about to break through with the IA64, but came too late to the table with the goods. For now we still have to emulate this old CISC architecture and there are only so many ways to improve the performance before hitting yet another barrier, such as heat, cost, etc.

      Dual core chips is the next iteration. However, we aren't really going to see any huge performance improvements again until we ditch x86 architecture.

      Remember, the only reason Intel and others have kept pace with "Moore's Law" applied to MHz is that they've set that as a goal each iteration. If a given performance enhancement didn't fit within the time/performance ratio of Moore, it was not pursued. This means that a 5% improvement in performance must be fully implemented in 3 months. At the complexity of current processors, this is getting significantly harder to do.

      -Adam
    49. Re:Asymptotic by tacocat · · Score: 1

      Yeah, well every great breakthrough in human history has pivoted upon the Materials that he was able to manipulate: Bronze, Iron, Steel, Silicon... Theoretically you can go some pretty awesome stuff with Optical BiRefringence, but the technology to build the physical devices has been wanting for over 20 years. You can build big ones, about the size of the original transistors, but nothing to put them into a IC construction.

      One of the biggest limitations to more advanced material construction of electronics/optics is that

      1. AlGaAs / GaAs structures, while uber cool require a very painstaking Molecular Beam Epitaxy to create
      2. All of the electronics technology is built on in a 2 dimensional world
      By two dimentions I mean that silicone transistors work along the Z-axis only and move electrons around on X and Y axis from transistor to transistor. But for Optical devices to work, they need to build these finely tuned structures along the X-Z or Y-Z axis which is hard to do with any technology. Nano technology is the precursor to being to do this.
    50. Re:Asymptotic by HiThere · · Score: 1

      The following rant is my personal opinion. I appologize for sounding more certain than the facts really warrant:

      I'm not at all sure that it's lack of research. I think that with current technology it's a hard problem (like room temperature superconductors).

      OTOH, we have experimental proof that small computational elements ganged together appropriately can solve any problem, though not as efficiently. Quantuum computing is probably of limited use in comparison.

      Still, in today's news Intel has built a laser on a chip. I don't know how big it is, or how much power it eats, but that will allow the theoretical maximal speed of information transfer between separate components. Lots of engineering to be done yet, but ... predictable???

      The rate of change in a multitude of fields has NOT been slowing, but rather increasing. That we can still imagine and desire things that haven't been accomplished is called foresight, and allows us to chose (wisely?) between alternative potential futures.

      I understand the desire for an infinitely fast processor, but the only technique even on the horizon for doing this is quantuum computation, and nobody really knows just WHAT it is capable of delivering. If successful, this would move the bottleneck from the CPU to RAM, or possibly to external storage. (It's been there before.)

      Moore's law is still holding, and will continue to hold with parallel processors, far beyond the point where I thought it doomed to failure. And chips will get faster as they get smaller (which trend *IS* continuing). But it becomes harder to manage as we approach the limits of the current technology. The next identified step is a big one though ... nanotechnology. Rapid progress is being made in that direction, but the current indications are that it won't yield larger monolithic CPUs, but parallel one's organized in three dimensional patterns. (Expect heat removal and energy transmission to be as significant a problem as information transmission. And control to be the main problem.)

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    51. Re:Asymptotic by Dogtanian · · Score: 1

      Umm they haven't yet found the limits to Hard Drives. Hard Drives are the new chips.

      You're planning on upgrading that Pentium-4 with a 1TB hard drive?

      Or have you got some seriously fscked (*) up Turing machine thing in mind, with the hard drive replacing the tape?

      (*) BTW, I don't know why I'm typoing this; I'm a foe of Profanity Blacklist, so anyone who doesn't want to see swearing isn't going to read it anyway. Actually, "Profanity Blacklist" sounds like some cool motherfucker from a blaxploitation flick. :)

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    52. Re:Asymptotic by frankvl · · Score: 1

      This is what I consider one of the breakthroughs of the 90's. It is just not practical enough (or something) for the big guys, but it is an easy explanation for every physical phenomenon; very very interesting.

    53. Re:Asymptotic by Anonymous Coward · · Score: 0

      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.

      9600 was never "the speed of copper", otherwise the phone companies would have had a major problem with their trunk lines. 9600 was an upper limit to what you could modulate to audio on a single voice channel. Anything beyond that required more sophisticated signal compression, and simply didn't work with many lines.

      There's no effective limit in bandwidth. Once you saturate the bandwidth of a medium, you can always add more wires. With computation, there's always some segment of a problem that cannot be parallelized -- sometimes it's a significant chunk.

    54. Re:Asymptotic by quanticle · · Score: 0

      Most users' needs are far exceeded by 2+GHz processors.

      Just like "most users' needs are far exceeded by 640k of RAM"?

      --
      We all know what to do, but we don't know how to get re-elected once we have done it
    55. Re:Asymptotic by edxwelch · · Score: 1

      You can generate similar posts here:
      http://www.dack.com/web/bullshit.html

    56. Re:Asymptotic by Tassach · · Score: 2, Insightful
      I don't know if you could scale a 15K rpm drive to use bigger platters. You would have a lot more centripital force at the rim -- I'd be worried about the platters warping.

      Also, the linear speed might be too high to read without interleaving (which pretty much negates the advantage of the higher speed)

      Some quick calculations:
      Assuming that a 3.5" drive has 2.75" platters, which would have a circumferance of 8.64", would have a speed of 129,590 in/min at 15,000 RPM, which equals 122.7 MPH.

      If we assume the 5.25" drive has 4.5" platters, these would have a circumferance of 14.14", which translates to 212,057 in/min or 200.8 MPH.

      Also, the 5.25" platters are 268% larger (15.9 in^2 vs 5.9 in^2). Considering that the larger platters will also probably have to be thicker to prevent warping, an estimate of the platters having 3 times as much mass isn't unreasonable. This means much more powerful spindle motors, along with more heat, noise, and vibration.

      None of these are insurmountable problems, but I doubt you could solve them economically enough to bring the unit price down so that it's competitive with smaller drives. The platter circumferance in the 3.5" drive is 8.64", which at 15,000 RPM is 129590 in/min, which translates to 122.7 MPH.

      --
      Why is it that the proponents of "one nation under God" are so eager to get rid of "liberty and justice for all"?
    57. Re:Asymptotic by Anonymous Coward · · Score: 0

      If your theory is true then we should see the technology wagon of the cold war start up again as China becomes a big player.

    58. Re:Asymptotic by halivar · · Score: 3, Funny

      Mods don't find marketspeak funny, apparently.

      Probably because it has nothing to do with Communism, old people, Beowulf clusters or setting up bombs.

    59. Re:Asymptotic by Anonymous Coward · · Score: 0

      shut up, please. I hate having to browse through 20 posts like this one to come to the (interesting) and (informative) posts.

      Yes I am posting as a AC, so I can save mod points to annihlate idiots like yourselves

    60. Re:Asymptotic by Thuktun · · Score: 1

      9600 baud is the limit of copper, and we haven't crossed it. The 33.6 is BPS or bits per second. Every speed increase over 9600 was obtained by compression (this is why you don't hear of a 33.6k baud modem).

      Compression in the form of v.42bis or v.44 is not generally factored into the speed rating of the modem, since its effectiveness depends on the data being transmissted.

      See these tables for a better idea how these speed increases above the actual signalling rate (baud). There is a combination between faster signalling rates (note that none of these appear to have reached 9600 baud) and cramming more and more information into the signals using advanced modulation techniques.

      Compression is on TOP of this.

    61. Re:Asymptotic by ksheff · · Score: 1

      then run the 5 1/4 drive at 10K or lower to get the same in/min as the smaller drive. I have a tower with a few 5 1/4 drive bays. Either I waste a lot of space or spend a lot of money for a RAID enclosure that puts 3-4 3.5" drives in one 5 1/4 drive bay to make these bays useful. Would one big 5 1/4 drive have more heat, noise, and vibration as 4 of the smaller drives?

      --
      the good ground has been paved over by suicidal maniacs
    62. Re:Asymptotic by Junior+J.+Junior+III · · Score: 1

      Pretty much; for present day applications, 2GHz ought to be enough for almost anyone. There a few people who really need more than that, but they're not driving the market.

      --
      You see? You see? Your stupid minds! Stupid! Stupid!
    63. Re:Asymptotic by Saeger · · Score: 1
      Great Scott, man! You're suggesting that 3D nano-CPU-grids are right around the corner? Surely you must be joking.

      But of course you're right - moore's law hasn't slowed one bit. As one computing "paradigm" begins to lose steam (and people start crowing about the supposed end of moores law yet again), another method picks up the exponential pace where it left off, resulting in a pretty graph of overlappying tech. That graph doesn't apply just to CPU's either, but to almost every other advancing area you can think of as well.

      --
      Power to the Peaceful
    64. Re:Asymptotic by Don+Giovanni · · Score: 1

      Now I finally understand why
      if you download a really large text file
      that sometimes the speed can get to 10Kbps or
      even 13Kbps sometimes, because it compresses really well!

      --
      P2P Anonymous Distributed Web Search: http://www.yacy.net/
    65. Re:Asymptotic by Chandon+Seldon · · Score: 1

      Computers on the desks of normal people has only been a reality for fifteen or twenty years. In that time we've moved from "A Typewriter With Pre-Print Proofreading" to "A machine that can do realtime interactive full motion video".

      Now, I'll admit that there's a bunch of things we could be doing with current technology that we haven't figured out yet - but there's even more things we could be doing if desktop processors / busses / RAM were operating in THz.

      Just because you're not interesting enough to come up with uses for technology that hasn't been produced yet doesn't mean that advances wouldn't be useful - and that's just on the desktop. For those people who already know they want faster hardware, faster hardware is obviously useful, and those people are more common than you'd think.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    66. Re:Asymptotic by Marvelicious · · Score: 1

      ... tinfoil hats man, how can you forget!

      --
      Send whiskey and fresh horses!
    67. Re:Asymptotic by Junior+J.+Junior+III · · Score: 1

      That's my point -- most people aren't that interesting. There ARE some people who can benefit from faster processing. Most of them are happy to increase their computing power through parallelization rather than ramping up the processor speed. For problems that aren't able to benefit from parallelization, they're kindof stuck right now, but there's not very many people who have those problems.

      Could home users make use of terahertz processors? I'm sure they could. It might allow human-like AI and natural language interpretation and all kinds of stuff. Does anyone NEED it today? Arguably, yes. But is anything people presently use a computer for lacking for processor speed? Maybe. But does a 2GHz processor adequately run nearly any application you care to name? Pretty much.

      --
      You see? You see? Your stupid minds! Stupid! Stupid!
    68. Re:Asymptotic by Surt · · Score: 1

      Echelon alert! Echelon Alert! Deploying FBI!

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    69. Re:Asymptotic by JWhitlock · · Score: 3, Insightful
      I might also throw in the possibility that, since the end of the Cold War, there has been very little incentive for governments, etc, to back fundamental research that might (a decade later) lead to radically new technologies. Governments like the status quo, they like the future to be predictable. Fundamental research (except perhaps in really esoteric areas like cosmology or areas with practical benefits for them like medicine) scares the willies out of the people in power -- it might upset their apple cart.

      The government pumped over a half billion a year into the Human Genome project, and spent $1.6 billion on nanotechnology last year. The government is still willing to spend money on basic research, but I doubt they are willing to create a whole new agency, such as NASA. They would rather have private companies do the work (even if federally funded), then create a new class of federal employees.

      I also think you are assuming malice on the part of the government, when instead you should be assuming stupidity. And, since it is a democracy, you don't have to look far to find the root of that stupidity.

    70. Re:Asymptotic by drinkypoo · · Score: 1

      You don't hear of a 9600 baud modem either except when people are abusing terminology. The last modem speed given in baud was 300; because of the encoding involved it took 2 baud for 1 bit and you got 150cps. 1200+ speed modems report their speed in bps after encoding. Encoding, btw, != compression, though modems do both now. However, data can only be compressed so much which is why zipping a zipfile produces only limited savings; you are compressing the index information, not the file data. Try sending a tar file and a tar.gz file, both containing compressible data, via zmodem some time, it will be a real eye-opener. Even modems older than the 9600 bps units would do compression sometimes; I had a microcom 2400bps with MNP 1-5. 1-4 are error correction, and 5 is compression. Compressed files got a minuscule bump if any, and with text I would often get speeds as high as 9600 bps.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    71. Re:Asymptotic by Marvelicious · · Score: 1

      1 go into preferences then comments and put a few negative points to funny under reason modifiers and positive points to interesting and informative.

      2 Change threshold accordingly

      3 QUIT YOUR BITCHING!

      4 Profit? (Sorry couldn't resist)

      --
      Send whiskey and fresh horses!
    72. Re:Asymptotic by Fulcrum+of+Evil · · Score: 1

      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.

      Yeah. 33.6 is still the limit if you're using a voice line. 128K is 2 channels of a T1 (which has run on a copper pair for the last however long. 7-10M is only possible because we're running equipment at the CO to talk to your DSL bridge.

      The point is, almost none of that is a result of technology limitations. Rather, it's a matter of deploying the right equipment and getting the Telcos to actually play ball.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    73. Re:Asymptotic by Kurt+Gray · · Score: 2, Funny

      I'll add that to my list of action items that way we can pick the low hanging fruit by the time we close the books on Q4.

    74. Re:Asymptotic by pthisis · · Score: 2, Interesting
      Computers on the desks of normal people has only been a reality for fifteen or twenty years. In that time we've moved from "A Typewriter With Pre-Print Proofreading" to "A machine that can do realtime interactive full motion video".
      ...and then stopped. 5 years ago. If we buy the 20 years figure, the last 25% of the PC era has had no need for faster processer speeds.

      And until someone somes up with another must-have reason (a "killer app"), the demand for higher speeds simply isn't there. Somewhere around 200-500 Mhz, machines simply got "fast enough"--I remember the bad old days before then, when everyone I knew got a new machine every couple of years (or even every year). And it actually helped you with your everyday word processing, music listening, web surfing, spreadsheets, etc. But the last thing I needed a faster CPU for was DVD playback, and that hasn't been a problem for years.

      Seriously, I'm a full-time programmer who does real-time music visualization as a major hobby,I'm enough of a geek to have run Linux exclusively for (literally) over a decade now on my desktop, and even I don't see a reason to upgrade my machine's CPU. For the majority of the public, the ever-faster CPU craze has been replaced by other needs. Lower power consumption, wireless, better peripherals/displays, handheld/music devices, etc.

      I went from a 4 mhz 8088-> 20 mhz 386 -> 66 mhz 486 -> 200 mhz PPro. And you know what? I don't remember how fast the machines I've had since then are--my current one is a 1.3 or 1.4 ghz P4, I honestly don't know--because that's when I stopped caring. It just doesn't matter any more.

      I think 1997 was the last time I bought a machine where I gave much thought at all to CPU speed. I haven't bought a new desktop machine in 4 years, and I don't foresee getting one in the next couple--but I have gotten handhelds, mp3 devices, etc. Indeed, the only reason I bought the last one was that my old one was very noisy, so I built a silent PC.
      --
      rage, rage against the dying of the light
    75. Re:Asymptotic by infinite9 · · Score: 1

      Yeah, it's people that make the difference.

      --
      Disconnect your television. Do your own research. Draw your own conclusions. They're probably lying. Don't be a sheep.
    76. Re:Asymptotic by Anonymous Coward · · Score: 0

      What kind of cold war are you going to have when one country manufacters everything for your country.

    77. Re:Asymptotic by lucifuge31337 · · Score: 1

      As plenty of people on /. do, I also understand the technology. My point wasn't to be technically literal, it was to illustrate a point.

      As other responders have already mentioned (in a way that leads me to belive I wasn't clear enough to begin with), multi-core processors and the like are already in development. Which prove the point I was originally trying to make.

      --
      Do not fold, spindle or mutilate.
    78. Re:Asymptotic by tompaulco · · Score: 1

      >...we are very close to the limits of silicon based CPUs
      Crap. Now programmers will have to go back to programming efficiently instead of depending on increasing CPU and cheap memory and disk.
      Hey, it's not all bad. "Real" programmers will probably go back to being upper middle class instead of lower middle class.

      --
      If you are not allowed to question your government then the government has answered your question.
    79. Re:Asymptotic by Anonymous Coward · · Score: 0

      When I bought my 2400 baud modem, it was called a "2400 baud modem", not a "2400 bps modem".

    80. Re:Asymptotic by KlomDark · · Score: 1

      He said silicone... Hahahaha.

    81. Re:Asymptotic by Fulcrum+of+Evil · · Score: 1

      None of these are insurmountable problems, but I doubt you could solve them economically enough to bring the unit price down so that it's competitive with smaller drives. The platter circumferance in the 3.5" drive is 8.64", which at 15,000 RPM is 129590 in/min, which translates to 122.7 MPH.

      Sure I could. Just mount 2 3" drives in the 5.25" package and write some glue to RAID0 them. It's not exactly what you're talking about, but it's probably cheaper than the straightforward solution.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    82. Re:Asymptotic by Fulcrum+of+Evil · · Score: 1

      Was your point that people are trying alternative approaches to make systems faster? Because that point was made in the article.

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

      Actually, I was implying that people and animals were 3D nano-CPU-grids. That's the experimental proof I was referring to.

      OTOH...

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    84. Re:Asymptotic by ckaminski · · Score: 1

      /. has a profanity blacklist?

      Wow.

    85. Re:Asymptotic by Anonymous Coward · · Score: 0

      Governments sure didn't like the status quo after the end of the cold war. Without any external enemies, more and more people were coming to realise that we didn't have that much use for governments. But then come the war against terrah and terrism and now we have more governments than ever. That sure was a close call.

    86. Re:Asymptotic by danila · · Score: 1

      But think of the tremendous upside that can be realised by proactively implementing the potential synergies (based on this).

      --
      Future Wiki -- If you don't think about the future, you cannot have one.
    87. Re:Asymptotic by Goalie_Ca · · Score: 1

      Hehe... sounds like 1984! The 3 leading world parties basically froze time to stay in power indefinently.

      --

      ----
      Go canucks, habs, and sens!
    88. Re:Asymptotic by drinkypoo · · Score: 1

      yes, so was mine, but it was an abuse of the term baud, because it was really bps. Many people make this mistake, including the american hertiage dictionary which says it is equal to 1 bps, but that is not true at all, except maybe in the case of synchronous modems. Baud is basically the same as Hz , in that it denotes a transition. However, as just about anyone can tell you, you can't just store a bunch of data with no way to ensure sync/position. If you have 0110, there are only two transitions. Hard drives used to store their data with two bits used for every bit, so you could only store half as many bits as the drive area would support. I forget which was which (and it probably varies between manufacturers) but a 0 has no transition between bits in a couplet, while a 1 does... or, like I said, that could be backwards. Regardless there was always a transition between the second bit of one couplet, and the first bit of the next. Assuming I have it the right way around, 0101 is thus written as 00101101. Later, RLL encoding came along and let us encode 1 bit using 1.5 instead of 2 bits, which is why you could put a 20MB MFM disk on a RLL controller and get 30MB out of it (Both used an ST-506 interface, and the intelligence was in the controller and not the drives in those days.) I have no idea what kind of encoding is used on either hard drives or modems nowadays, though. Certainly it allows for more efficiency...

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    89. Re:Asymptotic by danila · · Score: 1

      Fortunately, you are wrong. The amount of research done was doubling every decade for more than a century and much more reliably than the number of transistors on silicon. There is a huge amount of fundamental science being done all over the world. Yes, I wholeheartedly agree that it would make perfect sense to increase funding for fundamental science 5 times starting from next year, but sadly this is not a real option. Still, science budgets do grow and short-term thinking doesn't really harm science as much as it helps society utilize the results more efficiently and improve networking between science and industry.

      There is some truth in what you are saying. United States was spending more generously on science during Cold War. Soviet Union was spending the unheard of 4 percents of GDP on science (more than USA, Japan or any other country). And it might have looked better because both the USSR and the USA were interested in explaining in no uncertain terms why it kicked major ass in science. Today science has to relay on sensationalist press-releases aimed at morons with ADD to attract at least some attention. But, fortunately, overall, science has managed to survive and flourish.

      --
      Future Wiki -- If you don't think about the future, you cannot have one.
    90. Re:Asymptotic by Anonymous Coward · · Score: 0
      Probably because it has nothing to do with Communism, old people, Beowulf clusters or setting up bombs.

      Or with marketspeak laughing at you, as in Soviet Russia.

    91. Re:Asymptotic by danila · · Score: 1

      Wired had an article on programmable matter some time ago. I don't know if the guy you link to is a quack or not, but it sounds similar in concept.

      --
      Future Wiki -- If you don't think about the future, you cannot have one.
    92. Re:Asymptotic by Chandon+Seldon · · Score: 1

      So you're *absolutely sure* that no killer app will show up as processors get faster? Theres nothing that's waiting on a faster processor? There aren't voice recognition / synthesis methods that become feasable? No-one will want to do voice chat in a 3d virtual environment(i.e. EverQuest)?

      Just because you haven't tried anything new with your PC in a while doesn't mean that stuff isn't out there.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    93. Re:Asymptotic by the+web · · Score: 1

      I attended a seminar on the future of Quantum computing. Fascinating. Using an electrons spin (clockwise or counterclockwise) as the gate signals. Most fascinating was the putforth theory of controlling subsequent electron orbitals at the same time. Sending multiple signals at once.

      --
      __
      Thou hast besquirted me, O leotarded one.
    94. Re:Asymptotic by lucifuge31337 · · Score: 1

      Was your point that people are trying alternative approaches to make systems faster? Because that point was made in the article.

      I read /. Not articles.

      --
      Do not fold, spindle or mutilate.
    95. Re:Asymptotic by Fulcrum+of+Evil · · Score: 1

      I read /. Not articles.

      Yes, of course. I forgot where I was.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    96. Re:Asymptotic by Anonymous Coward · · Score: 0

      I am posting as a AC, so I can save mod points to annihlate [sic] idiots like yourselves [sic]

      GP hasn't been modded, so I can only assume you're full of it and have no mod points. I'll bet you've *never* had mod points, virgin.

    97. Re:Asymptotic by rogabean · · Score: 1

      You forgot the the 10Ghz Overlords... you insensitive clod!

      --
      "why don't you just slip into something more comfortable...like a coma!"
    98. Re:Asymptotic by Junks+Jerzey · · Score: 1

      Dual core chips is the next iteration. However, we aren't really going to see any huge performance improvements again until we ditch x86 architecture.

      I used to think that, now I'm not so sure. The ultra-clean PowerPC camp is having exactly the same troubles as Intel. MIPS was similarly clean, and it has fallen by the wayside. Ditto for the SHx series. What's left in terms of high-end CPUs? UltraSPARC? AMD's 64-bit architecture?

      The x86 ISA is ugly and convoluted, but behind the scenes x86 CPUs are essentially RISC. So are you talking about some all new architecture that doesn't currently exist?

    99. Re:Asymptotic by luxdormiens · · Score: 1

      biological computing? would that work?

      --
      I harass my semi-colons.
    100. Re:Asymptotic by rrhal · · Score: 1
      I'm enough of a geek to have run Linux exclusively for (literally) over a decade now on my desktop

      See now there's your problem. If you had been running 2003 Server you'd be need'n a faster machine by now.

      --
      All generalizations are false, including this one. Mark Twain
    101. Re:Asymptotic by pthisis · · Score: 1

      So you're *absolutely sure* that no killer app will show up as processors get faster?

      Nope. But I am sure that until it does, consumers will put more emphasis on other features than on CPU speed--and that will cause people like Intel to focus more on things like low power CPUs, wireless chipsets, etc that have higher demand. Even Intel couldn't manufacture demand for MMX when no killer apps required it--demand existed only in those niches where it was really useful.

      I'm not saying CPU isn't a factor at all these days. But for a lot of people--I'd venture to say most--it's slipped well behind other features that they need in a new machine. That's largely because for a lot of people, machines are fast enough to do the things they want to do--and have been for years now. If/when that changes, CPU demand will spike again.

      --
      rage, rage against the dying of the light
    102. Re:Asymptotic by bill_mcgonigle · · Score: 1

      I do remember reading an article on 33.6 modems that talked about 'quantum tunneling' effects that made 33.6 as fast as you'd ever go on the wire.

      Not that it was right but it did get some play in the PC press.

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

      That may be an effect of gzip compression. Some webservers and Browsers automatically gunzip the data as it comes.

    104. Re:Asymptotic by bill_mcgonigle · · Score: 1

      Do you suppose if you manage to write the right bit pattern to every sector on the drive you could get it to lift off?

      Apparently I've figured out how to do it but have been applying the bit pattern to the wrong side of the platters - my drives never take off but they all crash.

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

      Right, and nobody's ever been wrong with a statement like THAT before.

      Just because you can't imagine it doesn't mean it isn't interesting.

      --
      Why yes, I AM a rocket scientist!
    106. Re:Asymptotic by ad0gg · · Score: 1
      Ethernet and its predecessors has been pushing megabits or more over twisted pair for decades.

      Ethernet is limited to 100 meters. DSL is a few miles. Dialup or ISDN can be farther.

      --

      Have you ever been to a turkish prison?

    107. Re:Asymptotic by dabigpaybackski · · Score: 1
      We've found the limits of silicon and hard drives and they are being approached asyptotically. Relax...

      I wish I could relax, except the word "asyptotic" isn't in my dictionary and it's FREAKING ME OUT, MAN!!!

      --
      "OH SHIT, THERE'S A HORSE IN THE HOSPITAL!"
    108. Re:Asymptotic by Mandrake.Eldorage · · Score: 1
      As a result noone looks at things that may bring a breakthrough and there shall be no breakthroughs until this situation changes
      You mean there will be no breakthrough until there is a breakthrough?
    109. Re:Asymptotic by Anonymous Coward · · Score: 1, Funny

      In soviet russia, laser makes YOU die.

    110. Re:Asymptotic by Anonymous Coward · · Score: 1, Funny

      Jigga what?
      Jigga please!

    111. Re:Asymptotic by stienman · · Score: 1

      So are you talking about some all new architecture that doesn't currently exist?

      Yes.

      What PowerPC, MIPS, etc don't have that the x86 has is a huge market. The only reason x86 is still alive is due to backwards compatability. I still run Novell Netware 3.11 with Dos 6.22 workstations on the latest PIV and Athlon systems.

      AMD64 is simply an extension of the x86, though each extension is becoming somewhat more risc like.

      A major problem with the x86 ISA and risc core is that millions of transisters are dedicated to converting x86 instructions into native risc instructions. Power and perfromance could be saved by dealing with the risc code directly. Let the compiler do the hard work once (as the IA64 was designed) and then the processor can run blindingly fast each time the program is run.

      The problem is that we've outpaced ourselves. In order to approach and then surpass the performance of other RISC machines we've built in so many tweaks and techniques that to go straight to a regular RISC ISA would actually decrease performance. However, if all the applicable tweaks and techniques were applied to a new RISC ISA, and it had the momentum of the x86 architecture, then we could easily surpass our current performance without all the heat generated.

      But no one wants to really get rid of x86. Mostly for IP reasons. AMD doesn't want to try and get around the bevy of patents intel has and will get when they release a newer chip. MS and others don't want intel to be a monopoly. etc, etc, etc.

      As an example, the reason AMD no longer makes chips that are pin compatible with Intel is that Intel patented the memory access patterns for critical word first memory accesses. Suddenly AMD had to make their own northbridge and southbridge. In the end I think that it was a good move to shove them out in the cold like that, now they are not only competing in terms of processor speed, but memory bandwidth/latency, FSB speeds, etc. It led eventually to AMD's Hyper Transport.

      There's more politics and marketting in this race than one might imagine.

      -Adam

    112. Re:Asymptotic by maotx · · Score: 1

      And until someone somes up with another must-have reason (a "killer app"), the demand for higher speeds simply isn't there.

      Heaven forbid the Doom 3 people get a hold of you.
      You would have no need for a faster PC to see hell.

      --
      I'm a virgo and on Slashdot. Coincidence? Yes.
    113. Re:Asymptotic by Jonboy+X · · Score: 1

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

      Intel's new materials consist mainly of chewing gum and duct tape to glue a bunch of P4's onto a single die.

      --

      "In a 32-bit world, you're a 2-bit user. You've got your own newsgroup, alt.total.loser." -Weird Al
    114. Re:Asymptotic by jsebrech · · Score: 1

      There's no effective limit in bandwidth. Once you saturate the bandwidth of a medium, you can always add more wires. With computation, there's always some segment of a problem that cannot be parallelized -- sometimes it's a significant chunk.

      Not to mention that in networks, concurrency doesn't matter because the signals have no cross-dependencies. In computing however, every thread of your multi-threaded application has a relationship to the other threads, and so you must be explicitly aware of the constraints imposed by that relationship, which has a nasty tendency to lead to more code (which slows down everything even more).

      There are three things I consider necessary for developers to paradigm-shift to writing multi-threaded apps by default:

      - Built-in transparent multithreading in the supporting libraries and components that come with your programming environment of choice.

      - Language features for easily supporting locking in a manner that doesn't require you to constantly be aware of everything that leads to thread-unsafe locking. I'm thinking of something like the synchronized keyword in java, only more evolved to be able to chart dependencies of a piece of code to all the objects that it needs and handle locking efficiently and automagically.

      - Debuggers that are thread-aware, and let you get an overview of the interactions of the different threads, by limiting breakpoints and code stepping to a single thread, or a set of threads, and by showing thread dependencies and lock status (likely intertwined with the aforementioned language features).

      None of these are anywhere close to where they should be, and some languages are completely dead in the water, like the favorite of the linux community, C. As a result, people only write multi-threaded apps when they absolutely have to. My one experience with writing a multi-threaded app was painful at the least. I don't want to revisit debugging concurrent threads with the current generation of developer tools. It sucks.

    115. Re:Asymptotic by bob+beta · · Score: 1

      I still run Novell Netware 3.11 with Dos 6.22 workstations on the latest PIV and Athlon systems.

      Good lord! Why?

      I have a bunch of Pentium I Dell Optiplexes out in the garage I should clue you into.

    116. Re:Asymptotic by SpecBear · · Score: 3, Funny

      Fine, we'll take this offline. Just make sure to touch base regarding the status of your action items by EOB. We can't afford to lose momentum.

    117. Re:Asymptotic by stienman · · Score: 1

      I still run Novell Netware 3.11 with Dos 6.22 workstations on the latest PIV and Athlon systems. Good lord! Why?

      I'd like to say it's because I can't use FreeBSD and Windows has too many security issues for a retail operation, but the bigger factor is the boss simply doesn't want the associated cost of upgrading the software and the additional TCO of administering Windows systems. I field 4-5 calls per week from 15 retail stores due to minor problems. Go to windows and I'll bet my call volume and the priority of the calls would go up significantly. It took me awhile to lock the PCs down in the main office, and train the users not to mess things up. It's a different story with clerks who aren't paid to think.

      I have a bunch of Pentium I Dell Optiplexes out in the garage I should clue you into.

      They would cost more to ship than to simply buy locally. Plus Dell's quality dropped significantly for their cheap machines. But if you want to crate them up and pay for shipping...

      -Adam

    118. Re:Asymptotic by warb · · Score: 1

      Like cable modems! :)

      # Download size (bits): 8192000
      # Download size (bytes): 1024000
      # Download size (kilobytes): 1000
      # Speed (bits/second): 3103030.3030303027
      # Speed (bytes/second): 387878.78787878784
      # Speed (kilobytes/second): 378.78787878787875

    119. Re:Asymptotic by Anonymous Coward · · Score: 0

      There really is fundamental science going on out there. Superconductors are getting warmer. The recent work in laser physics to 'slow' light is another fundamental advancement. I am sure there are many more.

    120. Re:Asymptotic by maken · · Score: 1

      apaches didnt use teepees

    121. Re:Asymptotic by corpsiclex · · Score: 1
      Hehe... sounds like 1984!

      uhh, you must be new here.
      --

      eBayDig 1s a typo saerch engien
    122. Re:Asymptotic by ATMAvatar · · Score: 1

      I'm confused... I'm still running with 640k. Aren't you?

      --
      "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety."
    123. Re:Asymptotic by Don+Giovanni · · Score: 1



      Trust me, it's not that.

      I really does happen.

      --
      P2P Anonymous Distributed Web Search: http://www.yacy.net/
    124. Re:Asymptotic by Anonymous Coward · · Score: 0

      Or use BeOS! They had that idea all along.

    125. Re:Asymptotic by darkwhite · · Score: 1

      The lates process shrink to 90nm really hurt, and required bunches of tricks to make it work.

      All process shrinks in the history of IC production have required some sorts of tricks. The next two stages - 65 and 45 nm - are already in advanced development. They're not far from the limit dictated by molecule size - once the feature size starts spanning fewer than, say, 10 molecules things start to become impossible - but that just means ICs will have to start putting on more layers and new dissipation mechanisms (not necessarily on a single chip - chips stacked vertically with extremely short interconnects and some sort of cooling between the layers doesn't sound implausible to me), and/or lots of redundancy and error correction to compensate for functional defects arising from ridiculously small feature size.

      when you shrink chips, they get hotter

      No they don't. The heat just gets more concentrated, which means it's harder to dissipate it properly and there's more danger of malfunction due to local overheating.

      it still consumes something like 53w doing nothing ... there's absolutely no fix for that

      Wrong. Throttle it and reduce the Vcc, and turn off idle units altogether. Leakage is a huge problem, but idle leakage is readily fixable.

      There are lots of engineering problems where seemingly insurmountable physical limits are overcome by cleverly end-running them. Despite the emphasis on parallelism, the demand for single-threaded performance won't go away, and I think technologies will be found to make it increase.

      --

      [an error occurred while processing this directive]
    126. Re:Asymptotic by phreakmonkey · · Score: 1

      Who's got the action item list? I need a chart of next-steps and an MS project timeline. Don't forget to matrix your resources and keep the indvidual contributers in the status loop.

    127. Re:Asymptotic by EvilJoker · · Score: 1

      Dial-up compression is very real, and is not limited to HTTP. It is, however, limited to data that compresses well (possibly GZip, I don't know). When I had dial-up, I could regularly get speeds of 15KB/s on a 33.6 via compression. This applied to all text data (e.g. usenet headers), but not binary data. This came free with my various ISPs, no question asked.

      Now, the various bargain-basement dial-up places charge an extra $5/month for it, with extra BS software required.

      Webservers and browsers don't play a part in any of it, all is handled by the computers directly attached to the phone line.

    128. Re:Asymptotic by Mindragon · · Score: 1

      Uhh...Aren't we forgetting Nanotechnology? When that comes around, we will have nothing *but* materials science.

      --
      Just add {In Space!} to anything.
    129. Re:Asymptotic by Chandon+Seldon · · Score: 1

      Your argument depends on shallowly hidden circular logic. Watch.

      In thinking of the applications computers are used for, only those applications that work smoothly with current computing power are "real applications" because other applications don't work yet. Therefore, we don't need faster computers because all "real applications" run fine on current computers.

      We won't really know what applications faster computers make possible until we have the faster computers.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    130. Re:Asymptotic by Junior+J.+Junior+III · · Score: 1

      Oh, I know that. But still, we've yet to see the really hard problems of computer science solved by faster hardware. Faster computing may make things possible, but it doesn't guarantee anything. Actual effort must be put in to these hard projects (such as AI) in order to see results. We've mostly stagnated for 20 years because for most of that time computer scientists have only had a dim understanding of the problem they're trying to solve.

      --
      You see? You see? Your stupid minds! Stupid! Stupid!
    131. Re:Asymptotic by MikeDX · · Score: 1

      or profits.... No wait.

    132. Re:Asymptotic by ksiddique · · Score: 1

      ... or Natalie Portman and hot grits. mmm

    133. Re:Asymptotic by alva_edison · · Score: 1

      The only problem with Gallium Arsenide is that it has been "the next big thing" in semiconductors for the last 40 years.

      --
      He effected a bored affect.
    134. Re:Asymptotic by Don+Giovanni · · Score: 1

      Actually aren't they merely further compressing
      what is already compressed throught the v.92 standard?

      I wish every website everywhere used gzip.

      --
      P2P Anonymous Distributed Web Search: http://www.yacy.net/
  2. 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 Ubergrendle · · Score: 1

      Do you mean multi-core CPUs, multi-cpu board architectures, or both?

      I've noticed that pretty much any RISC chip at this point is multi-core, or will be in the next year. I can only assume that the desktop PC will be headed in that direction as well in the next 18-24 months.

      --
      John Maynard Keynes: "When the facts change, I change my mind. What do you do?"
    3. Re:Heat is the problem by suso · · Score: 1

      CPU heat wouldn't be a problem if they would just invent steam power hard drives. ;-)

    4. 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
    5. Re:Heat is the problem by LWATCDR · · Score: 1

      The answer to the memory bandwidth could be to move the memory onto the cpu. That is sort fo what is happening already with cache. Optical? Optical is not that much faster than electical. They both run at close to c.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    6. Re:Heat is the problem by Blapto · · Score: 1

      And rather conveniently, this was /.ed earlier today :).

    7. Re:Heat is the problem by thepoch · · Score: 1

      Out of curiosity, does running two processors side by side really help with heat dissipation? Doesn't the heat increase simply because there are now two processors producing heat instead of one? Instead of one processor idling at around 40 degrees, you now have 2 idling at around 40 degrees. Plus the fact that most PCs aren't actually ventilated well with all the cables and additional cards inside.

      Of course I'm also assuming that people will run two processors at fast speeds (2.0ghz and up). I doubt anyone would be willing to lower heat by running a dual-processor machine at slower clockrates (ie how much cooler is a dual 1ghz machine compared to a dual 2ghz machine?). Everyone always wants the fastest.

    8. Re:Heat is the problem by Anonymous Coward · · Score: 0

      So, you think that using multiple iterations of an inherently power-hungry technology will somehow solve the power problem?

      No, (s)he said it would help solve the heat problem. Power was not mentioned.

    9. Re:Heat is the problem by JollyFinn · · Score: 1
      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.

      Yes an no. There are plenty of reasons why. Firstly the power comsumption is HIGHLY dependent on voltage, dynamic comsumption its V and for leakage I cannot remember. And somewhat on frequency, but maximum attainable frequency is function of voltage, and some design characteristics of transistors, that have been sacrificed for higher frequency traditionally. And besides that you use more transistors in complex large core than two simpler cores, that have higher peak performance combined than the single core. Also they could desing LOW power transistors, but those cannot get high frequencies. By now you probably know the point. ALL the things that processor designers could do for low power, could reduce powercomsumption FAR more than it would reduce performance. If their target would be for instance having half the powercomsumption of other core, they would probably get way over 2/3rds of performance. Now Dual core is about putting 2 cores that each are almost as fast as single core processor to a single die. The goal of maximizing single thread performance maybe over, simply because it costs too much in power comsumption to do so.

      --
      Emacs is good operating system, but it has one flaw: Its text editor could be better.
    10. Re:Heat is the problem by IWannaBeAnAC · · Score: 1

      Umm, exactly what do you think causes heat if it is not power dissipation in the silicon???

    11. Re:Heat is the problem by IWannaBeAnAC · · Score: 1
      Out of curiosity, does running two processors side by side really help with heat dissipation?

      Yes, a lot. I can't remember off the top of my head what the relationship is between clock speed and power disipation, but it is not linear. At least quadratic, probably worse. So a single core at 4GHz will consume much more power and generate much more heat than two 2GHz cores.

    12. Re:Heat is the problem by Ironsides · · Score: 2, Interesting

      It is not cheap to move memmory onto the CPU. Cache is VERY expensive. And they already did that by moving the cache onto the CPU (it used to be an external chip like RAM). Moving ram onto the cpu would be very expensive and would limit system ability to adapt. More likely would be to move the memmory controller onto the CPU so that the CPU bypasses the system bus altogether when accessing memmory.

      --
      Fly me to the moon Let me sing among those stars Let me see what spring is like On jupiter and mars
    13. Re:Heat is the problem by akuma(x86) · · Score: 2, Informative

      A few problems with your post.

      1) 75% idle time is nonsense. Where did you get that number? With SPECfp on an Athlon or P4 it's more like 20-30% idle. Just look at how spec scores scale with frequency to figure out the memory-idle time.

      2) Increasing switching speed with optical technology increases bandwidth but does nothing for latency since nothing travels faster than the speed of light and electrons flowing along a wire can acheive close to 80% of the speed of light already. To reduce latency, what we need are smarter architectures and programmers that can prefetch the data into lower latency caches ahead of time.

    14. Re:Heat is the problem by angel'o'sphere · · Score: 1, Insightful


      Optical? Optical is not that much faster than electical. They both run at close to c.

      Electrical chips run far below 1% of c.
      Optical would be far faster for several resons:
      o no interference between parallel lines
      o reduced waiting at gates for signals comming from the other side of the chip, so earlyer time ready to switch
      o generally faster travel time of the signal

      angel'o'sphere

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    15. Re:Heat is the problem by Anonymous Coward · · Score: 0

      Where are you pulling these BS figures from?

      75% of its time idle? Maybe while you're typing email, but definitely not when you're doing something intense.

      CPUs are NOT spending 75% of their time waiting for memory! Say it with me "megahertz: it's not a myth anymore!"

      CPUs are becoming insanely CORE-LIMITED! We have memory bandwidth to BURN! How can you prove this? Simple! Take an Opteron and compare performance with 1 channel and with 2 channels. You will come away surprised. The difference is seldom more than a few percent.

      Next, try underclocking the RAM. I'll save you some time and refer you to anandtech's last Opteron benchmarks on Linux. The difference between 333 MHz DDR and 400 MHz DDR was, in one test, at most a few percent, and in the other test, basically zero!

      What about L2 cache size? 512 KB versus 1 MB? Rarely does that matter, too. Again, typically a few percent at most if you dig back through past benchmarks.

      Now if you try an Opteron 148 and an Opteron 150 on an intense benchmark, you should find a surprising correlation with clock speed. Surprise! We just disproved the megahertz myth! At least for the K8, the fastest way to increase performance is to beef up the core. Add ALUs or increase clock speed.

    16. Re:Heat is the problem by Austerity+Empowers · · Score: 1

      Moving the memory onto the CPU has been done for almost 20 years. It's of course always a speed improvement, yet the size of applications, data etc. have also been increasing for 20 years. My 286 had a 20MB hard drive, some CPU caches are approaching that now. However, these days applications are also much bigger.

      In reality the bulk of memory is always going to be off chip. I agree with you optics is not the answer, since a single copper wire can transmit data fast enough to saturate a CPU. It's the memory devices themselves that are too slow.

      DRAM itself is slow, but it's the cheapest and fastest technology available. It'd be great if someone could invent a faster memory that could be made so cheaply. They'd get rich fast.

      Similarly Hard Drives are still a bunch of spinning platters with a mechanical arm flying around inside. To say it's slow is an understatement. Yet in terms of capacity...can't beat it.

      Anyone who solves these problems or provides an alternative will become insanely rich beyond his wildest dreams. Obviously it's easier said than done.

    17. Re:Heat is the problem by Wordsmith · · Score: 1

      It's not just waiting for the memory to give it something to do ... It's waiting for the user to. How much computing did the machine do while you read this paragraph of text?

    18. Re:Heat is the problem by Anonymous Coward · · Score: 0

      >The CPU spends as much as 75% of its time idle because its waiting patiently for the memory to give it something to do.

      This statement is almost laughable in it's ignorance. The memory is simply data storage. Running programs, processes, and user input give the cpu work.

      It is possible that the cpu waits for data to be returned from memory, but the cpu already has something to do when it accesses memory and waits. The memory (or any other storage device) doesn't give anything something to do. In fact it's quite the opposite. The CPU gives the memory subsystem work. Store this, get me that etc.

      I think you are referring to the wait times incurred by the cpu when it gives the memory controller work.

    19. Re:Heat is the problem by alexq · · Score: 1
      I think he made up the 75% number from the 1Ghz/4Ghz numbers.. It is bogus... (Because those numbers don't take into account the width of either the bus OR the processor/EXE units)...

      I was going to post something similar to your post, but I'll just instead agree with you here, and wonder why you aren't being modded up :)

    20. Re:Heat is the problem by WaZiX · · Score: 2, Informative

      1) 75% idle time is nonsense. Where did you get that number? With SPECfp on an Athlon or P4 it's more like 20-30% idle. Just look at how spec scores scale with frequency to figure out the memory-idle time.

      In an Article of November 2004s Issue of Scientific American about about optics-based computers.

      2) Increasing switching speed with optical technology increases bandwidth but does nothing for latency since nothing travels faster than the speed of light and electrons flowing along a wire can acheive close to 80% of the speed of light already. To reduce latency, what we need are smarter architectures and programmers that can prefetch the data into lower latency caches ahead of time.

      Huh, where did i even mention the speed of of electrons along wires? Im simply stating that wires will never be able to deliver enough data for the processor to be able to function at a correct regime.

    21. Re:Heat is the problem by NoData · · Score: 2, Interesting

      Electrical chips run far below 1% of c.

      Yeah, the flow of electrons in wire is extremely slow, but the work is really done by the electrical field generated, so that as one electron is pushed into the wire, it "pushes" the sea of electrons forward so that an electron at the other end of the wire is shifted forward. This "shift" occurs pretty close to c. I

    22. Re:Heat is the problem by akuma(x86) · · Score: 1

      >> Huh, where did i even mention the speed of of electrons along wires? Im simply stating that wires will never be able to deliver enough data for the processor to be able to function at a correct regime.

      I'm saying that there is not really a compelling need to go optical. Electrical does just fine with intelligent caching.

    23. Re:Heat is the problem by thoper · · Score: 1

      not really, look a the scale, its LOGARITMIC!, were not close to nuclear reactor heat density!

    24. Re:Heat is the problem by Botty · · Score: 0

      Well, IANAIE (Intel Engineer) but they dont replicate TWO WHOLE PROCSESSORS on one chip. Although there are two cores, they can share many other parts which means its hardly a 2x increase in heat. The processor is broken down into many subunits and the instruction decoding and processing units are just a few though they do the brunt of the "work".

    25. Re:Heat is the problem by Anonymous Coward · · Score: 0

      Propagation of signals in a wire is a function of voltage propagation, not current. c doesn't factor into it at all. The resistance and capacitance of the wire are what limit the speed through a wire.

    26. Re:Heat is the problem by MarkCollette · · Score: 1

      One reason why CPUs dissipate heat is because when a state change happens in a transistor, the stored energy is dumped, and is then converted to heat. If that energy could be moved elsewhere, temporarily, and then recycled, then heat would go way down, and clockspeed could go way up.

      Or I'm just pulling that out of my ass.

    27. Re:Heat is the problem by hasdikarlsam · · Score: 1

      They've already done that; the AMD64 chip has the memory controller on-die.

    28. Re:Heat is the problem by macemoneta · · Score: 1

      Actually, we're at the point where multi-processing would help people do the type of function that they want more CPU power for, like video transcoding and computer generated graphics. Using SMP configurations of low-power CPUs (like the XScale) would dramatically reduce power and heat, while improving throughput for these easily parallelized functions. A 16-way XScale configuration would dissipate only about 8 watts for the CPUs, yet provide the 10GHz effective processing.

      --

      Can You Say Linux? I Knew That You Could.

    29. Re:Heat is the problem by cyngus · · Score: 1

      Not, true, not true. A Power Mac G5 2.5Ghz has a 1.25Ghz bus speed. You argument also fails because of code locality where a lot of need info is in the processor cache and prefetch algorithms that deliver info to the cache before its need. The last time that CPU and bus speeds matched was in the 486 generation, I forget, early Pentium's may have had same speed buses.

    30. Re:Heat is the problem by hunterx11 · · Score: 1

      Meanwhile you could use something like simultaneous multithreading (like hyper-threading).

      --
      English is easier said than done.
    31. Re:Heat is the problem by Anonymous Coward · · Score: 0

      > (or perhaps a new computing paradigm... something "non-Von Neumann).

      Hello, Von Neumann. - Jerry

    32. Re:Heat is the problem by ChrisMaple · · Score: 1
      The resistance and capacitance of the wire are what limit the speed through a wire.

      Wrong. The propagation speed along a wire is c/sqrt(ue), where u is the relative permeability and e is the relative permittivity. In an IC's SiO2, this is about c/2. If conductor resistance slows this down further, the conductor was made too small or of the wrong material.

      --
      Contribute to civilization: ari.aynrand.org/donate
    33. Re:Heat is the problem by Anonymous Coward · · Score: 0

      Quite a bit, actually... its quietly folding proteins all day long.

      http://worldcommunitygrid.org/

    34. Re:Heat is the problem by Don+Giovanni · · Score: 1

      I believe the AmigaOS 4's ASMP is the future; assymmetric multiprocessing.
      You have three computers in your home?
      Cluster them together with Windows GEE Home Clustering Edition!

      --
      P2P Anonymous Distributed Web Search: http://www.yacy.net/
    35. Re:Heat is the problem by Val314 · · Score: 1

      >Processors are approaching the heat density of a nuclear reactor

      looking at those slides it looks like this should happened at 100nm. thank god prescott is at 90nm and surpassed this threat elegantly ;)

      hey... maybe this where the nuklear WMD everybody was searching for some time ago...

    36. Re:Heat is the problem by ArbitraryConstant · · Score: 1

      I've had the same thought as the person you responded to... it seems unlikely that clock speeds will increase a whole lot (maybe one or two doublings left), but I think it's safe to assume that we'll be seeing more and more cores on each die, and that increasing the number of memory buesses isn't practical (too many wires), so we'll be moving to higher bandwidth, higher latency memory busses that the CPUs cores will have to share.

      I was thinking that we could still have physical memory as we know it today, but it won't be directly usable by the processors. They'll treat it as swap space that's faster than a hard drive would be.

      The issue with this is overhead in handling page faults. Currently it's not even close to worth it. Significant optimizations and hardware support would be necessary.

      --
      I rarely criticize things I don't care about.
    37. Re:Heat is the problem by crgrace · · Score: 1

      To quantify this:

      Standard CMOS logic power dissipation varies as the square of the supply voltage, and is linearly dependent on switching frequency. It has nothing to do with Si, it has to do with the structure of standar CMOS logic. Current mode logic, like ECL in Bipolar tech or CML in CMOS, has a more constant power dissipation, regardless of speed.

      Lowering VDD (supply voltage) is the number one thing you can do to lower power diss, but there of course is a limit to that.

    38. Re:Heat is the problem by dajak · · Score: 1

      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.

      I would be perfectly happy with, let's say, ten passively cooled 1Gh pc's, each running one application + a small operating system, provided that I can use one set of peripherals and can cut and paste easily between applications through a global clipboard. The hardware is no problem: we need a new operating system.

      Another thing I have been waiting for for years is the integrated home pc/boiler/central heating system, powered by (watercooled) CPU's. I never understood why generating heat is a problem. The real problem is that we are wasting it by trying to force hot air out with fans through the same holes in the box that we use to let cool air in resulting in noise which is useless waste.

    39. Re:Heat is the problem by Fulcrum+of+Evil · · Score: 1

      Out of curiosity, does running two processors side by side really help with heat dissipation?

      Yeah - you can do stuff like turn one off when it isn't being used. this would require software support except for the dual-core case, but you could have a 4way box that drops 3 procs when idle.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    40. Re:Heat is the problem by LWATCDR · · Score: 1

      I do not see it limiting the systems ability to adapt. My idea is more along the lines if you need more ram add more CPUS yes it would be a massive NUMA system and you would have to write new software for it to be effective but then it is just an idea. I was thing each cpu having 256 megs of really fast ram and use the rest of the 64 bit address space to map to the other CPUs ram.
      Before I get flamed I know there are lots of much smarter people than I working on this. But then again this is slashdot so why not throw out a wild idea not and again.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    41. Re:Heat is the problem by NoWhereMan · · Score: 1
      I cannot speak about the fundamentals of heat issues, but I do remember something Grace Hopper said about working on the farm. She talked about the limits of using bigger and better horses to pull the plow. The obvious solution was to use a team of horses.

      She was a lady ahead of her times. Aside from her finding the first true computer bug (which was a Gypsy Moth according to my memory ;-) and handing out nanoseconds, she promoted multi-processing. Looks like we are just beginning to understand her wisdom.

    42. Re:Heat is the problem by Scott7477 · · Score: 1

      I have a P-4 and I run the Windows XP system monitor while I'm working (mostly text docs, spreadsheets, and web surfing) and the CPU usage graph generally stays somewhere south of 20% about 95% of the time. So your average user who isn't compiling/running simulations/calculating spreadsheets would probably see a similar graph.

      --
      "Lack of technical competence coupled with the arrogance of power, as usual, leads to no good end."
    43. Re:Heat is the problem by SQL+Error · · Score: 1

      So, you think that using multiple iterations of an inherently power-hungry technology will somehow solve the power problem?

      Yes, which is why Intel, AMD, IBM and everyone else are heading down that path as fast as possible.

      Here's a little hint: The 2GHz Pentium M Dothan uses about 21W. The 1.1GHz ultra-low-power version of that chip uses about 5W. Two 1.1GHz cores gives you more total througput at half the power.

      Another datapoint: The power figures for the forthcoming dual-core Opterons show the 2.4GHz version at 95W, the 2.2 GHz version at 55W, and the 1.6GHz version at 30W. So you can get six 1.6GHz cores for the same power consumption as two 2.4GHz cores. Twice the throughput, same power.

      And note that this is without even redesigning the cores; this is just running the same core at lower voltage and lower speed.

    44. Re:Heat is the problem by Anonymous Coward · · Score: 0

      In special cases it would be 'as fast as'. But probably not even then.

      For example lets say you want to play with a 2 GIG data set. Not all that large by todays standards. Lets say you have a bus that can transmit 1 MEG of data in 1 second (thats way low). But it will show off the problem nicely.

      So I have 16 cpus all sitting on 1 bus that can send 1 MEG of data. It would take 2000 seconds just to move the data into 1 cpu. Now with more than one cpu you are going to have to wait once and awhile for someone else. It is not as simple as saying 2000/16. There is a LARGE amount of over head. Also I didnt even have data going BACK to memory where I need it.

      Ah but you say 'I can use a switch topology' Ok There is STILL overhead. Lets say you have 4 banks it STILL is not 2000/16/4 There will be contention in the data bus.

      Ah I can have 2GIG of data and 1 bus per cpu. Ok an interesting idea but now you have to put your data on all the 'nodes' and get it all back from the 'nodes'. That takes time. It would probably be faster. But you would spend a lot of time chunking up the data.

      In special cases breaking up the data and sending it to multi cpu makes things smoke. But for MANY cases it does not do a whole lot. For example would a word processor really benifit from a 16 way machine? Probably a dual MAYBE a 3 way. The problem just does not 'break up' nicely.

      What it comes down to really is heat. They can not crank the mhz up because the things would melt. But they can put more and more on the cpu anyway. So it will either be more cpus or more memory. More memory is going to be the real bang. But it will only go so far...

    45. Re:Heat is the problem by NeMon'ess · · Score: 1

      So 2 channels + faster RAM + 1MB = ~10%

      That explains why AMD does it to get a 2.2GHz performing like it was a 2.5

    46. Re:Heat is the problem by fienna · · Score: 1

      Actually, i work for a microwave cable production company and we manufacture cables that have greater than 80% velocity. (86% and we're working on 90% with some funky stuff)

      By the way, i have a cable on my desk that goes to 70GHz without any trouble - we make them by the thousands.

      Introducing fiber optics to a computer motherboard only makes things bulky and slower. You first need to convert your electrical signal to light, then send it 10 inches, then convert it back to electric. (not to mention that you have thousands of traces on your mobo) Remember that the closer components are, the shorter the propigation delay, so if we're inserting all this extra hardware in the way, we'll find ourselves with huge globs of hardware. It certainly won't be faster as long as our cpu's work on the almighty electron.

      switch to photonic computing, however, and fiber becomes key...

      --
      /not so /obvious
    47. Re:Heat is the problem by xouumalperxe · · Score: 1

      this is an oversimplification of the problem. While it IS true that memory bandwidth is a limiting factor, you beg the inference that only 1 processor operation will be done on each piece of memory, so the processor will spend that much time idling. While I agree that assuming 1 operation per clock cycle is probably oversimplifying as well, I have to point out that often enough (most of the time, even), you will want to load a fair-sized block of data to the cpu's cache, and operate the crap out of it. Cache memory is usually accessed at the same frequency as the processor's. The presence of large amounts of cache on processors, together with the data requirements for real-life processing, greatly reduces the damage done by the limited bandwidth

  3. And that is why... by lukewarmfusion · · Score: 0, Offtopic

    ...you shouldn't do drugs.

    Since when did Slashdot start mimicking Hunter S. Thompson?

  4. 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.
  5. We need a faster bus by Anonymous Coward · · Score: 0

    system buss, hard drives, etc too slow anyway

    1. 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.
    2. Re:We need a faster bus by Anonymous Coward · · Score: 0

      This guy has hit it! He got a 4, but he should have a 5!

    3. Re:We need a faster bus by Anonymous Coward · · Score: 0

      01010010 01001111 01000110 01001100!!!

    4. Re:We need a faster bus by Grizzlysmit · · Score: 1

      Just a slight comment on the serious side, when were we promised this stuff and by whom, there where the odd predictions, but promises I must have missed those.

      --
      in my life God comes first.... but Linux is pretty high after that :-D
      Francis Smit
  6. Well Moore's Law is not a law... by zoobaby · · Score: 3, Informative

    It was just an observed trend. The trend is breaking, as far as retail availability, and thus we are not seeing our 10GHz rigs. (I believe that Moore's law is still trending fine in the labs.)

    1. 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.

    2. Re:Well Moore's Law is not a law... by frankthechicken · · Score: 1

      Indeed, Moore's law is more concerned with the amount of transistors to be found on integrated circuits rather than the marketing drive of Intel and their need for speed and increasing GHZ.

    3. Re:Well Moore's Law is not a law... by Viking+Coder · · Score: 1

      I thought it was 18 months?

      Is it that the frequency doubles every 18?

      --
      Education is the silver bullet.
    4. 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.

    5. Re:Well Moore's Law is not a law... by stupidfoo · · Score: 1

      No, the "law" was later adjusted to 18 months. Originally it was every 12 months.

    6. Re:Well Moore's Law is not a law... by AvitarX · · Score: 1

      But since the low end machines are junk that break down as quickly as replacement cycles of yesteryear. Compenter repairs cost as much as a new machine on sale ($200.00 for HD plus install)

      And until MS gets subscriptions they have a vested interest in peoples machines getting spy/add-ware and viruses to slow them down to sell more OS's on new machines (of course the purchase of anti sppyware and anti virus properties implaies a move to subscription based revenue without infuriating everybody that they need to subscribe to be secure from exploits).

      I think general computer idiocy along with first time purchasers will keep the market going as long as marketing can keep things as a new revolution.

      They don't even need to make the chips faster to get people to replace their computers. If someones 2 year old machine is slow due to spyware, they could buy a slower machine with a name like Ass Kick Proc 63 and talk about how much it sped things up for them.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    7. Re:Well Moore's Law is not a law... by MrWa · · Score: 1
      I love how misinterpreted and confused Moore's law can be, yet people still insist on referring to it whenever microprocessor technology is discussed.

      From four highly moderated posts we get:

      It was just an observed trend. The trend is breaking, as far as retail availability, and thus we are not seeing our 10GHz rigs. (I believe that Moore's law is still trending fine in the labs.)
      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.
      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.
      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.

      So, depending on where you start reading, one could believe that there are 10GHz rigs in the labs, transistor count == processor speed, Moore's Law is about price performance, or transistor density doubles every 18 months.

      Can we stop quoting Moore's Law like it is anything other than an observation from 40 years ago? Yes, Moore's Law is used as a driving and motivation force at microprocessor companies (e.g. Intel...) but that doesn't mean your processor will double in SPEED every 18 months, or come down in price, or anything concrete.

      For the record: I believe the original observation was regarding transistor count per area.

    8. Re:Well Moore's Law is not a law... by LordOfYourPants · · Score: 1

      Please note that when AMD released their GHz processor first that it was all about "the need for speed and increasing GHz." Now that they've fallen back all of a sudden it's not about the GHz anymore.

      LordOfYourPants' law: The importance of GHz measurements are proportional to the ratio of your company's highest GHz CPU offering relative to all other companies.

    9. Re:Well Moore's Law is not a law... by Mr.+Shiny+And+New · · Score: 1

      But AMD found that they could get better performance by increasing the ammount of useful work done per clock cycle, rather than increasing the number of clock cycles, so in a sense they "Fell behind" in the GHz game, but they kept up in the performance game. Of course, because the public has been brainwashed for so long, they don't understand the difference, so AMD needs to advertise differently since they are not the king of the GHz game.

    10. Re:Well Moore's Law is not a law... by kannibal_klown · · Score: 1

      A friend of my brother's really annoys me.

      He claims to be an expert on computers (and I'll admit he knows a little).

      But whenever someone mentions AMD, he laughs. "They're at what, 2 GHz now. Talk about ripping people off with those upped numbers."

      No matter how many times I explain what's going on, and that the performance is similar, he sitl laughs and starts going on about clock cycles.

      I don't know who I hate more. Those that know nothing, or those that know only a little.

    11. Re:Well Moore's Law is not a law... by Mr.+Shiny+And+New · · Score: 1

      Well, the other day I was in a computer shop and I asked the guy if they sold AMD processors, and he basically laughed at me and said you should only buy Intel. I tried to explain: AMD chips tend to be faster AND cheaper, why would anyone buy Intel? He didn't understand. I started to explain about the AMD speed rating numbers and I could tell that I lost him. It's such a simple concept: performance = number of instructions executed /cycle * cycles / second. Intel increases the second value while AMD increases the first. sigh.

    12. Re:Well Moore's Law is not a law... by Anonymous Coward · · Score: 0

      Since when did "trend" become a verb? No, really, give me a date. Damn this mutating English language and its quickly-changing semantics.

    13. Re:Well Moore's Law is not a law... by coopaq · · Score: 1
      No, Moore's law was about price performance not about absolute performance.

      No. Moore's law states that any processor that performs better than a duck and floats is made by witches!

    14. Re:Well Moore's Law is not a law... by timeOday · · Score: 1
      That's OK, except straight interpretation of Moore's law is completely uninteresting in the first place. The "law" wouldn't be famous in the first place if it didn't have implications for speed and cost.

      When people say "Moore's law is failing," what they mean is that the exponent on price drops and performance increases is shrinking, which is true, and which is a really big deal.

    15. Re:Well Moore's Law is not a law... by Fulcrum+of+Evil · · Score: 1

      So, depending on where you start reading, one could believe that there are 10GHz rigs in the labs, transistor count == processor speed, Moore's Law is about price performance, or transistor density doubles every 18 months.

      I know for a fact that there were 10Ghz chips in the lab as early as 1997. The problem was that these were technology prototypes, and so only had about 10k transistors and a huge heatsink.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    16. Re:Well Moore's Law is not a law... by Anonymous Coward · · Score: 1, Funny

      "that the number of transistors per square inch on integrated circuits"

      Make those integrated circuit higher. They will have the same base size but a bigger volume.

      It's a good Moore's law hack.

    17. Re:Well Moore's Law is not a law... by MrWa · · Score: 1

      I wouldn't dispute that - it is just funny that three different Moore's Law posts get +4 or +5 for being Informative or Insightful...

    18. Re:Well Moore's Law is not a law... by RedWizzard · · Score: 1
      that the number of transistors per square inch on integrated circuits had doubled every year since the integrated circuit was invented
      I don't think that's right. I think it was that total transistor counts would double each 18 months. Transister density has certainly not doubled every year, or even every 18 months. More like every 30 months.
    19. Re:Well Moore's Law is not a law... by King_TJ · · Score: 1

      Well, at least where I live, I'm starting to observe more of a trend of people paying out the money for good computer service and support. All of the cost-cutting and price wars to get PCs down to the "Complete system with flat panel monitor for under $500!" caused "customer service" to all but vaporize.

      Sure, some people *are* going out and buying new machines when spyware/viruses screw up their existing ones, but many of them are quickly messing up the replacement computers too. Usually, after they go through 2 machines like this, they decide maybe they should really just pay someone to fix the problem and show them how to avoid causing it again.

      The number of on-site/on-call computer support places in our local phone book easily doubled since last year. Some random calls to these places showed that on *average*, they're billing people at least $100/hour or so for their work, too.

      This makes me think the trend towards getting the cheapest PC possible might reverse itself. People are gonna say "Hey, I called around and it's gonna cost me hundreds just to fix this ONE problem my computer had. If it's like that, maybe I should just buy that higher-end system next time anyway? No point paying out close to the initial cost of my PC every time I need some help with it - and maybe I'll get more for my money if I spend a little more?"

    20. Re:Well Moore's Law is not a law... by Anonymous Coward · · Score: 0

      Originally it was every 12 months

      no, originally it was 24. it used to be said "every 2 years it doubles".

    21. Re:Well Moore's Law is not a law... by MindStalker · · Score: 1

      In side note in the article writer actually meantions that a dual-core chip could give you performance boost, simply because one core could be processing your spyware while the other core handling your applications. I think he is joking, but its kinda sad really.

  7. 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 bustersnyvel · · Score: 1
      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.
      Oh, how I long for those days!
    2. Re:Engineering within limits brings great results by AviLazar · · Score: 2, Funny

      So I can run four instances of CS and p0wn3d everyone in my single player, multi-character clan.
      Viva la VM-Ware

      --

      I mod down so you can mod up. Your welcome.
    3. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 2, Funny

      but without a higher number of mhz on my CPU how will my penis get larger?

    4. Re:Engineering within limits brings great results by the_rev_matt · · Score: 1

      I've been reading the stories on folklore.org, and it's truly amazing what they were doing with the very limited memory they had available to them. These days software shops assume the user has a 1.5Ghz machine and at least 512M of ram and a seperate GPU and video ram as well. Makes them value efficiency and graceful code far less, in my opinion.

      --
      this is getting old and so are you

      blog

    5. Re:Engineering within limits brings great results by nurb432 · · Score: 2, Interesting

      I doubt it will go back that way, we are to the point that they can be sloppy and get a way with it.

      The limits are high enough now to not care. Back in the old days the limits were low enough that it did make a difference...

      Not only that but the skills that used to exist in the older days are dissapearing.. "dont need to know that stuff'..

      --
      ---- Booth was a patriot ----
    6. Re:Engineering within limits brings great results by SpaceLifeForm · · Score: 1
      Those days are still with us. It just depends upon where you look.

      If you follow the MS philosophy, you keep piling on features (and other stuff), and you make the users have to upgrade the machine to faster processors, more ram, faster disk drives, etc.

      If you follow the Linux philosophy, you constantly strive to make the performance as best as possible, so that you *can* run it on older hardware.

      --
      You are being MICROattacked, from various angles, in a SOFT manner.
    7. Re:Engineering within limits brings great results by Lally+Singh · · Score: 1

      Right now we've got another problem: the demand for software vastly outstrips the supply. Developers don't have the time or economic incentive to spend more time on software that already meets requirements.

      --
      Care about electronic freedom? Consider donating to the EFF!
    8. Re:Engineering within limits brings great results by isecore · · Score: 1

      Amen to this.

      I miss those days when you had 25 Mhz, and some wacky demo-coders were doing crazy stuff with it!

      Future Crew, where have you gone?

      --
      I enjoy large posteriors and I cannot prevaricate.
    9. Re:Engineering within limits brings great results by menkhaura · · Score: 2, Insightful

      These days we have processors hundreds times faster than 5, 10 or 20 years ago, we have thousands times more memory than we had yore... But, do our apps feel faster?

      I tend to believe that they don't value efficiency and graceful code at all.

      --
      Stupidity is an equal opportunity striker.
      Fellow slashdotter Bill Dog
    10. Re:Engineering within limits brings great results by blargorama · · Score: 1

      Educational Sig: Referrer is spelled with two r's, not one. HTTP_REFERER has a typo. Ummm.... excuse me, but isn't referrer spelled with FOUR r's, not two?

    11. Re:Engineering within limits brings great results by punkass · · Score: 1

      What, you don't get spam?

      --
      "Nobody owns the fucking words man." - James Dean
    12. Re:Engineering within limits brings great results by dAzED1 · · Score: 1

      really? I used to have no problem creating a kernel smaller than 512k to boot from. Now I can't get the damn thing under a meg and have it support the same stuff it did before.

    13. Re:Engineering within limits brings great results by Trigun · · Score: 1

      There comes a time when you just have to let go of the past. The floppy drive has the distinct scent of almonds, it's time to cut the gangrenous mess off.

      The longer we use legacy hardware, the longer we are plagued with it. Get a CF reader, and boot from that. You're way better off. As an exercise in stress relief, smash the old floppy drive with a ball-peen hammer.

    14. 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.

    15. Re:Engineering within limits brings great results by lee7guy · · Score: 1

      A desktop box with Linux installed with the corresponding functionality of Windows (Gnome/KDE) is not much faster than Windows, in my experience. I have been running Redhat, Gentoo, Mandrake and SuSE, none of these were much faster than Windows on the same box, running either KDE or Gnome.

      Talking server performance specifically, your points would be more accurate. Windows is not a server OS, it's a desktop OS modified for running server tasks.

      Looking for an OS with best (desktop) performance possible, Amiga, BeOS, AtheOS (Syllable) is where I would start.

      --
      Ceterum censeo Microsoftem esse delendam
    16. Re:Engineering within limits brings great results by CreatureComfort · · Score: 1



      In those days spirits were brave, the stakes were high, men were real men, women were real women and small furry creatures from Alpha Centauri were real small furry creatures from Alpha Centauri.

      We miss you DNA

      --
      "Unheard of means only it's undreamed of yet,
      Impossible means not yet done." ~~ Julia Ecklar
    17. Re:Engineering within limits brings great results by dAzED1 · · Score: 1
      I was able to do this just a couple years ago. I haven't had a computer with a floppy drive in years.


      My point is people can whine about windows all they want and say Linux is staying efficient, but...its not. Its not as bad as windows has been in its best moments, but its definately taking on a lot of bloat regardless.

    18. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 0

      I remember the old days, when programmers nudged every single bit of speed and capability out of the machines they had.

      It still happens...on consoles. Look at the difference between a first generation game (GTA3) and a final generation game (GTA:SA). Both were said to push the limits of the PS2 at the time of release.

      At the same time, though, the PS2 is some old hardware.

    19. Re:Engineering within limits brings great results by tolan-b · · Score: 1

      The right to bear arms was meant to be about local militias, not redneck wankers shooting their neighbours.

      Sheesh, I'm from the UK and I know that...

    20. Re:Engineering within limits brings great results by ThosLives · · Score: 1
      If this were the case, wouldn't the price of software and the demand for programmers be higher? With all the talk about programming work going overseas, it seems there is definitely enough supply of developers.

      On the flip side, the fact that software companies can charge thousands of dollars for enterprise-level applications (I'm even thinking in the engineering arena, when a single license for a simulation package that implements college-level concepts costs $3000 for a year) does bear some credence to your observation. You would think, though, that software companies would remain profitable, keep US (high-paid) employeees, and not have to offshore.

      It sounds like, since the supply is so limited, that all the unemployed programmers in the US should be able to find all the jobs they want, because the customers would be happy to hire them (after all, you get hired because of customers, not because of a company that produces product Z). The fact that this doesn't work and the companies have the ability to [offshore] means that there is enough supply (not just local) and the demand and supply are in balance. Granted, this doesn't apply to all classes of software, so it's hard to quantify.

      Interesting train of thought on which you've sent me this afternoon, though...

      --
      "There are a dozen opinions on a matter until you know the truth. Then there is only one." - CS Lewis (paraprhase)
    21. Re:Engineering within limits brings great results by gorgonite · · Score: 1

      Get the hell out of *their* country.

      Referring to Iraq, for example.

    22. 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.

    23. Re:Engineering within limits brings great results by Threni · · Score: 1

      > I hope this ushers that habit back into the profession.

      Fuck that.

      Tell you what, I'll continue to write good code quickly which requires 2ghz and a big hard disk or whatever the platform I'm writing for with, then I get paid and go out and enjoy myself away from my PC while you fuck about with Vtune, WinIce or whatever the hell people with that sort of obsessional disorder use these days making it go faster and getting paid assembly-monkey wages. Deal? I'm through with assembly and low/medium level optimisation.

    24. 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?

    25. Re:Engineering within limits brings great results by wan-fu · · Score: 1

      While I think those times were great, I have to disagree with you. Think about a lot of the advances we have made in programming technology such as better garbage collection, multithreading, object oriented systems, etc. A lot of these new technologies are great to use, but to manage at the level you speak of to squeeze every bit of speed/memory is simply crazy. A big part of why our stuff is getting higher and higher level is because it provides better abstraction so that programmer's can do more interesting things and focus on the problem and not so much the tiny little things. Yes, using a bitboard will help you increase performance in a chess-playing program, but the implementor can save a whole lot of his own effort and be more productive to implement better features if he focused his time elsewhere. I'm not saying you're completely wrong, I still think it's important for every programmer to understand machine architectures, etc., but these days, they can be more productive focusing on things other than trying to pack eight bits into seven.

    26. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 1, Insightful

      I don't think sloppyness as much as history and economics: layers upon layers of crap that accrete over the years. All the programmers in the world keep churning out more and more code, and they, and vendor sales, management have to make a living. Therefore, the accounts of customers are continually churned, as we are pushed along by vendors, 'the gartner group', and the numerous trade rags, who all have the same agenda: that the customer continue to spend.

      New protocols, paradigms, middleware, and the buzzwords and evangelists to sell them are pushed out at a phenomenal rate. We are now going from 'ERP' and 'CRM' to 'web services' to 'service oriented architectures', etc... without the time to even understand what these really are (the vendors don't really want us to anyway), much less what benefit they actually provide.

      Once again, politics and money have determined events, and now we are living with the result: Bloated, buggy, incomprehensible, useless-feature-laden, eye candy.

    27. Re:Engineering within limits brings great results by Dun+Malg · · Score: 1
      The right to bear arms was meant to be about local militias, not redneck wankers shooting their neighbours.

      Straw man argument. False dichotomy. When you have a local militia made up of regular citizens, some of them are going to be redneck wankers and they are going to shoot their neighbors. You send those jackasses to the electric chair; you don't decide the militia shouldn't be armed.

      --
      If a job's not worth doing, it's not worth doing right.
    28. Re:Engineering within limits brings great results by PurpleAlien · · Score: 1

      I'll continue to write good code on a 2Ghz and big hard disk. Then I get paid and go out and enjoy myself away from the PC. But I'm glad I know assembler and can optimise C because that way I have more options getting paid well because I can program and optimise embedded systems which have for instance 20KB of RAM and 256KB of ROM, which is more than enough to even let it talk to the internet etc.
      Point is, these low level, optimising programming techniques are still needed in the industry today, and by having those skills, one can be more secure of a job.

      --
      My blog, if you're interested: http://www.purp
    29. Re:Engineering within limits brings great results by Just+Some+Guy · · Score: 1
      I wouldn't have said it quite like that, but yeah, I agree with you. Honestly, I just don't give a rat's butt about low-level optimization anymore.

      I work mostly in Python now. Rather than deciding on whether to use a shift instead of multiplying by a power of 2 (and weighing the odds of the multiplication factor changing to a non-power-of-2 a few months down the road and having to re-code that bit of the program), I can concentrate on making my programs algorithmically sound. I try to use idiomatic Python whenever possible so that I can let the interpreter do the hard work instead of my high-level code, but that's my main concession to optimization - other than compiling Python with -march=athlon-thunderbird in the first place.

      Know what? I wouldn't change it for the world. It's far cheaper for my boss to buy a faster CPU than to pay me to hand-tune my code, and we've reached a level of compiler development that I doubt I could do a better job anyway. I still value efficient code, but I'd rather get it by analyzing the problem at hand and designing a reasonable solution than by picking away at every last wasted cycle.

      --
      Dewey, what part of this looks like authorities should be involved?
    30. Re:Engineering within limits brings great results by Dun+Malg · · Score: 1
      Perhaps you don't understand that: We the people != You the individual

      Yes it does, just as it does in all the other amendments. Read the Federalist Papers next time before you presume to understand exactly what the words in the bill of rights were intended to mean.

      --
      If a job's not worth doing, it's not worth doing right.
    31. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 0

      There is lots of demand for software, just lots of people who want radically different pieces of software. If they all wanted the same app I think things would be different.

    32. Re:Engineering within limits brings great results by Mike+O'Hara · · Score: 1
      Couldn't agree more.

      There are many games out now that have a ridiculously high minimum spec, and the reward for achieveing this is hugely disappointing in comparison to what was being done years ago on much simpler machines.

      For example, the Sims2 plays incredibly badly on a XP2200, Geforce4Ti4600, 512MB ram. Not exactly a cutting edge machine, but come on! The Sims2 doesn't exactly present me with any cutting edge in the visuals department.

      The only thing to blame is sloppy coders. In my days as (and here I risk discrediting myself) an Amiga user, people were doing more impressive things on a 200MHz 603e with 128MB of ram than The Sims2 on a 1.8GHz processor and 512MB.

      --
      [FUCK BETA]
    33. Re:Engineering within limits brings great results by operagost · · Score: 1
      On my Windows 95 machine with 8 megs of ram swapping was slow enough that effective multitasking was out.
      My OS/2 box did quite well with that amount of RAM.
      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    34. Re:Engineering within limits brings great results by JesseL · · Score: 1

      Official opinion on what the Second Ammendment to the US Constitution means, from the Office of Legal Counsel for the Attorney General of the the United States.

      www.usdoj.gov/olc/secondamendment2.htm

      --
      "Prefiero morir de pie que vivir siempre arrodillado!"
    35. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 1, Interesting

      >Makes them value efficiency and graceful code far less, in my opinion.

      Actually most programmers value efficiency very highly (if they are actual programmers and not posers). So do the shops.

      The issue you are referring to manifests when the client makes unrealistic and unreasonable demands to have software released before it is ready, because an uninformed manager was forced into a poorly researched estimate. All because the RFP had to be out before the other guy's so the competition wouldn't get the job. Proper R&D for the estimate is rarely possible. That estimate is basically a contract.

      Economics makes them value efficiency and graceful code far less. The minute you get something to work, in the real world, is usually the final state of the code. In reality you should then start looking at ways to make it work as efficiently as possible and go through a peer review process. The response I always get when I suggest this is, "I have to get this into QA by tomorrow, we don't have time for this luxury". It's always do or die and 2 months behind schedule.

      They'd rather get the code out by an unrealistic deadline, half assed, then patch it into crap oblivion, than do it right the first time. I see it daily. Trust me it's the business people, not the programmers and engineers.

      Of course if we did things correctly it would take too long. It isn't poor programming, most code is simply in an alpha state because of time and money constraints. If it does the job as it needs to be done right now, this minute, it's good enough in the mind of the business man. Forget extendability and efficiency.

    36. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 0

      Yeah - I'd be happy to kick all the XML heavy bloatware out right now!

    37. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 0

      OMFG. Are you actually trying to start an OS/2 vs Win95 flamewar?

    38. Re:Engineering within limits brings great results by SmittyTheBold · · Score: 1

      I do find it entertaining that as soon as we started taking ever-increasing speed gains for granted, they stopped coming so fast...

      --
      ± 29 dB
    39. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 0

      Ahh... the days when programmers optimized. Would be cool if they did return.

    40. Re:Engineering within limits brings great results by letxa2000 · · Score: 1
      My experience was different. I finally moved from Windows to Linux on my laptop when I bought a new 1.5GHz laptop with XP and Word 2000 opened slower than it did under Win98 on a 550Mhz laptop.

      I subsequently installed Linux and bought Win4Lin for my legacy Windows apps. Under Win4Lin under Linux my Word 2000 open time was similar to what it was before and definitely faster than the same machine with XP.

      So I guess your mileage may vary. I got much better speed out of Linux than XP.

    41. Re:Engineering within limits brings great results by AmigaBen · · Score: 1

      Your problem is you were using a Windows 95 machine. :) I was happily multitasking graphical apps in 512k of RAM years before that on my Amiga. So maybe it's not that his glasses are rose colored, but rather that you've worn blinders for years.

      --
      +5 Insightful, really!
    42. Re:Engineering within limits brings great results by HiThere · · Score: 1

      You would do better to compare vim and MSDos edit. That way you could compare applications that were doing nearly the same thing (at least if you were running in single-user mode with X not loaded and all feasible processes killed.

      If you are running gedit in a Gnome or KDE desktop (or even blackbox), you have much overhead besides the editor.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    43. Re:Engineering within limits brings great results by EnderWiggnz · · Score: 1

      25 MHz ?!?!?

      try 64K of ram - c= style.

      and the demos STILL kick much ass.

      --
      ... hi bingo ...
    44. Re:Engineering within limits brings great results by arkanes · · Score: 1

      It was a specific data point, not the only machine I used ;) You weren't doing the sort of seamless multitasking I can do now in Photoshop, and you weren't working with images at the same sort of resolution, either. Capabilities have changed, is the point. Performance of an application beyond the perception of the user is pointless, so adding capabilities makes sense. If you don't USE those capabilities, then you may decide that software is bloated and slow even though it's subjectively not. Exactly how fast does a text editor need to be? How would you even measure it's performance?

    45. Re:Engineering within limits brings great results by Dogtanian · · Score: 1

      I doubt it will go back that way, we are to the point that they can be sloppy and get a way with it.

      In some cases, yeah.

      In other cases (not necessarily those that apply to real-life), if you choose a shitty algorithm, it will get bogged down *very* quickly.

      For example, if you have an algorithm whose time to run is proportional to "n!" (n factorial), where n is the number of items, then you are in the shit.

      In such a case, if you have, say, 30 items, the speed is proportional to 30*29*28...*2*1.

      If you add another item, the speed is 31*30*29*...*2*1.

      If you add *another* item, the speed is 32*31*30*...*2*1.

      So, going from 30 to 32 items has slowed the algorithm down by 31*32 = 992 times!

      Imagine adding another ten items. The important implication is this; if you bought a computer 31 times faster than your old one, it would let you run the same program with 31 items instead of 30 (in a fixed amount of time). That's all. Pathetic, isn't it? And this is far from the worst rate of growth.

      So; moral is, don't choose lousy algorithms. However, it can sometimes be proven that even the *best* algorithm for a given task is incredibly slow.

      Not only that but the skills that used to exist in the older days are dissapearing.. "dont need to know that stuff'..

      BTW, this is true Computer Science, as opposed to Software Engineering; which is why seemingly pointless mathematical stuff that "practical" courses don't cover *can* be important. I suspect that understanding stuff in this vein may help practically when it comes to getting the most from concurrency, although this isn't my personal strong point.

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    46. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 0

      You can talk to w3c about this one. The variable is spelled HTTP_REFERER. The name of this variable is spelled correctly. The word used by the variable in it's name is mispelled. I lost count of the number of bugs this caused me my first 6 months of HTTP programming LOL. I always put 4 r's in at first, especially at 4AM.

    47. Re:Engineering within limits brings great results by ThousandStars · · Score: 1

      As long as you're going to tell the story of Mel, we should also review what makes a Real Programmer, and why they don't use Pascal (which, it almost goes without saying, means they would really abhor Java).

    48. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 0

      I dunno. Try switching from email to email in Outlook 2003 sometime and see how fast it updates the screen.

    49. Re:Engineering within limits brings great results by roosterx · · Score: 1

      Actually, what I took from the parent post, was how they optimized software knowing that the hardware wasn't going to change. What I instantly pictured was my atari 2600, and how the longer it was on the market, the better the games got. The hardware didn't really change, but the software developers took what little they had and did great. Now, I don't think we're at that point yet where we can start doing that, but eventually, the layers upon layers of API's demanding better hardware so that it's easier for a developer to create a widget with only 2 lines of code....yeah maybe we have a little wiggle room there.

    50. Re:Engineering within limits brings great results by AnotherBlackHat · · Score: 1

      These days software shops assume the user has a 1.5Ghz machine and at least 512M of ram and a seperate GPU and video ram as well. Makes them value efficiency and graceful code far less, in my opinion.


      I used to think that it was the size and speed of modern processors that led to bloatware, but no more.

      Now I think it's because people believe in Moore's law.

      Why make a program 20% faster and 20% smaller, when in a year the machine will be 40% faster and have 40% more memory?
      It's not cost effective to optimize - much better to work on something else.

      You still see tight code in systems that can't grow - embedded controllers and such.

      I predict that when Moore's law stops (or at least, slows down enough) then bloatware will end.

      -- Should you believe authority without question?
    51. Re:Engineering within limits brings great results by grumbel · · Score: 1

      ### That way you could compare applications that were doing nearly the same thing.

      Gedit and MSDOS edit are doing basically the exact same thing, the presentation is different, but from the feature point of view they are almost exactly the same. The point is that while the CPUs have become faster, the applications themself actually have often gotten a whole lot slower, in this case actually slower the the amount of CPU speed increased, resulting in an overall slower 'computer'.

      There is nothing wrong with adding feature which make use of the additionally available CPU power, but today its far to often 95% pure bloat without actually adding any features, sometimes even reducing them. There is really absolutly NO excuse for having such a trivial app like Gedit take multiple seconds to load, writing fasts apps today is still quite possible, Blender or Rox for example start in an instant, basically no Gnome or KDE app comes even close.

    52. Re:Engineering within limits brings great results by gothfox · · Score: 1

      Gedit is based, for example, on the GTK toolkit. Did your "MSDOS edit" have anti-aliased fonts and RTL input?

      Do you really think that all this stuff you consider basic and don't even think about comes for free?

      Vim starts in a second and it shreds that "MSDOS edit" to pieces in terms of functionality. Think about it.

    53. Re:Engineering within limits brings great results by Garak · · Score: 1

      Win 95 is the worst example ever of efficent code. The thread is about code from 1985 and older not 1995.

      Windows 95 is a prime example of the mentality that creates crappy slow software.

      --
      God, root, what is the difference?
    54. Re:Engineering within limits brings great results by Surt · · Score: 1

      I'd be fascinated to hear in what cases the best algorithm can be proven to be slow.

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    55. Re:Engineering within limits brings great results by pthisis · · Score: 1

      These days we have processors hundreds times faster than 5, 10 or 20 years ago, we have thousands times more memory than we had yore... But, do our apps feel faster?
      Yes, dramatically.

      20 years ago I was waiting minutes for programs to load off of tape and routinely typing in programs that overflowed the machine's RAM despite being as minimalist as BASIC allowed. Just drawing the screen was visibly slow even at low resolutions.

      15 years ago I was waiting over a minute for my word processor to load off of disk before I could do anything, waiting a long time to save, and couldn't open more than one document at once (aside from maybe looking at a calendar in Sidekick if I was feeling adventerous). The games I played had major visible slowdowns even with low-res CGA sprites.

      10 years ago I was swapping like crazy if I opened two windows in netscape, and it was honestly faster for me to run my copy of netscape on my rooomate's computer (and vice-versa) so that the X server and Netscape were taking advantage of each other's CPU and RAM (despite the network latency of 10BaseT). Running Emacs and Netscape at the same time was a major problem, I'd have to wait for visible repaints if I flipped between virtual desktops running the two.

      When mp3 playing became prevalent (a little less than 10 years ago for me), it was a major adventure to find a setup that would allow me to listen while I worked with only a little skipping--I definitely picked certain editors and compiler options to help with that.

      Now I have 16 tabs open in my browser, a half dozen terminals, 4 graphical editor windows, a compile running, an instant messenger client, tons of little doohickeys in my control panel, an OpenOffice spreadsheet, and an mp3 player going. And yet it feels FAR faster than that machine I had just ten years ago--I can click buttons and see them respond immediately, flip around between virtual desktops as though they were virtual consoles, listen to music without problems, etc.

      --
      rage, rage against the dying of the light
    56. Re:Engineering within limits brings great results by isecore · · Score: 1

      My apologies, I never got into demos until I got my 386.

      Yes, I am a pagan, I know.

      --
      I enjoy large posteriors and I cannot prevaricate.
    57. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 0

      Have you tried FreeBSD? You will definitely see a
      performance increase, and it will feel more responsive, than
      anything else except BeOS and those homebrew OSii.

    58. Re:Engineering within limits brings great results by WWE-TicK · · Score: 1

      Depends on how you look at it.

      Windows 95 had to be more backwards compatible with MS-DOS than any other OS at the time and had to support an extremely large installed base of legacy software and hardware. Given these design contraints, it's amazing that Windows 95 ran at all.

    59. Re:Engineering within limits brings great results by pthisis · · Score: 1

      I do find it entertaining that as soon as we started taking ever-increasing speed gains for granted, they stopped coming so fast...

      We started taking them for granted when we ceased really caring about them--when the need for speed affected our daily work, we looking forward to the faster CPUs with great anticipation, bought machines more often to get more speed, and were willing to pay a premium for it. When CPUs got fast enough for us, we started taking speed increases for granted.

      Not coincidentally, when the demand for faster CPUs dropped, manufacturers switched to giving us things we wanted more.

      That said, the rate of CPU speed increases hasn't actually tailed off too much.

      --
      rage, rage against the dying of the light
    60. Re:Engineering within limits brings great results by WMD_88 · · Score: 1
      Speaking of that, in 1990 it was really easy to type faster than the Macs in our computer lab could keep up.

      Your lab had some crappy Macs! :)

    61. Re:Engineering within limits brings great results by grumbel · · Score: 1

      ### Do you really think that all this stuff you consider basic and don't even think about comes for free?

      It of course doesn't come for free, but its still rather cheap, its by no means an excuse for having almost 5 sec startup time. Just look at Blender, it can do 3d modeling, video-editing, edit images and even comes with a text-editor, anti-aliased fonts too, startup time however is instantanious, a fraction of a second. Beside from that, the 5secs startup time of Gedit are already with a fully running Gnome session, so all the UI-goodiness, fonts and stuff should already be loaded into memory, which makes the startup time look even worse then its already is. As said, there is just NO excuse for such a poor startup time, its just bad optimization, nothing else. If you don't care about startup time, you will get such horrible startup times simply because its way to easy to do stupid things that cause them.

      ### Vim starts in a second and it shreds that "MSDOS edit" to pieces in terms of functionality.

      So what? Of course you can write programms with more features then yesterdays apps without making them slower, thats the whole point, even my Emacs starts faster then Gedit.

    62. Re:Engineering within limits brings great results by arkanes · · Score: 1

      Well, yes. Schools didn't exactly get the newest and shiniest stuff ;) Most of the original machines were orignal Macintoshes. No "2", or "SE", just "Macintosh". There was one that everyone wanted to use cause it had 2 disk drives, meaning you didn't have to switch to play Dungeon of Doom. I think that was a Mac SE.

    63. Re:Engineering within limits brings great results by Lally+Singh · · Score: 1

      Desktop software's only cheap because it's mostly worthless. There's been no innovation for years, and the market has flooded with copycats. That's why prices are so low. They can't compete on features so they have to compete on value, which when features is constant, means price goes down.

      Enterprise and engineering apps (where there has been innovation) seem only to get more and more expensive, yet only increase in value. Look at how many people that software is replacing!!

      India's got problems meeting their demand of IT labor at this point. India's willing to invest in the IT industry (gasp! what a risk!) to see future rewards, and it's already paying off.

      Demand is just opportunity. Being able to take advantage of that demand is a different issue. Demand can't be met without investment in infrastructure to satisfy it, which we don't have in the US. There's no major investment going on for any industry (outside of defense and oil...), and as such these industries have to sit back and wait, or get creamed by other countries that are willing to invest (like India).

      --
      Care about electronic freedom? Consider donating to the EFF!
    64. Re:Engineering within limits brings great results by fupeg · · Score: 1

      Let's not forget the other aspects of those olden times. Baffling bugs. Indecipherable code that was impossible to maintain. The constant joy of re-inventing the wheel on every project.

      Maybe we can go back to other good ol' times. Like when it took great skill to tell time by observing the sun, instead of lazy buffoons using clocks. Hey next time I see somebody going to IKEA maybe I'll stop them and suggest they go chop down a tree and build themselves a table just to show off their "magic."

    65. Re:Engineering within limits brings great results by Hynee · · Score: 1

      Simple example, Gedit, an extremly basic text-editor takes 4-5 seconds to load on a 1Ghz Athlon

      Interesting that you picked on startup latency, this probably depends mostly on the system and compiler libraries that the App loads, and these probably contain a lot of stuff that the app doesn't need, plus layers of legacy--read already optimized in days of slower processors--functions that the app needs, like string inserts and find functions.

      Added to this Gedit is a GUI app on Linux, and GUI isn't mature yet there, so there's probably lots of debug code loaded when those libraries are implemented.

      Slightly straying, I can remember when you could watch the Mac OS go through all its window drawing and region invalidating routines, and you could click and type ahead, knowing what order the events would go through and what objects they would be sent to. That doesn't get honoured any more--when I really load up firefox, and press control-tab then click, then before the system can react, left-click, this is interpreted as a control click. Maybe this is optimized for fast computers, or maybe it's buggy code, I don't know.

      --
      Damn, I already moderated this topic. Now I'll have to log in with my sock puppet to comment.
    66. Re:Engineering within limits brings great results by Fulcrum+of+Evil · · Score: 1

      So that the good people of /. (and the other people of /.) Don't wipe out a single server (yeah, right!)

      Wow, a Slash-clusterfuck. I mean, a beowulf cluster of slashdots. Um, how about a MIRVed slashdot warhead. Yeah, that's the ticket.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    67. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 0
      Official opinion on what the Second Ammendment to the US Constitution means, from the Office of Legal Counsel for the Attorney General of the the United States.

      I believe the official opinion comes from the Supreme Court, not the AG.

    68. Re:Engineering within limits brings great results by gothfox · · Score: 1

      Now that I think about it you could have some local configuration problem.

      I just installed gedit - it launched in a second first time on my Debian box running FVWM.

      I don't use Gnome so probably I won't be of much help, but sometimes fontconfig (which GTK uses) slows program startup a lot if you have many fonts installed. You could investigate that. Or try running gedit under strace.

    69. Re:Engineering within limits brings great results by tolan-b · · Score: 1

      I was suggesting that the arms should be held by the nominated administrators of the militia, rather than in everyone's homes.

    70. Re:Engineering within limits brings great results by default+luser · · Score: 1

      This is a limitation of storage speed, not processing power.

      Your latest, greatest hard drive is only 10-20x faster in terms of sustained read bandwidth than a drive of a decade ago, and is only about 5x faster in terms of access time.

      Edit loads fast because it's a tiny program that uses low-level OS hooks to interact and render itself.

      GEdit loads slow because it's about 100 times larger than Edit, and the disk subsystem hasn't kept pace with the code bloat. Plus, the high-level library interfaces Gedit uses don't help it's loading times any.

      So yeah, we have mostly hit a wall in terms of loading times and what your processor can do to alleviate them. As memory gets larger and outpaces the growth of hard drive transfer speed, loading times are likely to get even larger.

      Of course, there are still justifications for having a powerful processor. Half-Life 2, with it's powerful physics engine, eats processors for breakfast. I've got a 2GHz Athlon64, and the framerate can still dip well under 60fps even with minimum video settings...it just eats that many processor cycles.

      And don't count out media performance. These days everyone does a little encoding / decoding here and there, and it's always nice to do it faster.

      --

      Man is the animal that laughs.
      And occasionally whores for Karma.

    71. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 0

      "slows program startup a lot if you have many fonts installed"

      Precisely...

    72. Re:Engineering within limits brings great results by Sri+Lumpa · · Score: 1


      If the given task is NP.

      --
      "The obvious mathematical breakthrough would be development of an easy way to factor large prime numbers." Bill Gates,
    73. Re:Engineering within limits brings great results by Pfhreakaz0id · · Score: 1

      I dunno. Try switching from email to email in Outlook 2003 sometime and see how fast it updates the screen.

      Ok, AC, I'll bite. I just did that. I have outlook 2003 up and running right now and 4 emails open. No real delay.

      This is my environment, thought: a 2.8ghz P4 with 1 gig ram.
      but I've got eclipse, two command prompts running large custom java programs, a browser with 8 tabs open, XMLSpy with a big XML file open (15 meg), Tomcat server, SQL Server database, excel word, ultraedit and ObjectDoc (a very graphically intensive start bar replacement). Oh, and Itunes sharing (and playing) music on the network.... I think I'm somehow making the original poster's point :)

    74. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 0

      You're sooo 1337.

    75. Re:Engineering within limits brings great results by Surt · · Score: 1

      Really, you have a proof of this?

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    76. Re:Engineering within limits brings great results by tolan-b · · Score: 1

      Which seems to imply that the intention was to have well organised armed militias.

      How many US gun owners are members of a well organised militia?

    77. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 0

      Gedit takes 0.9 second to load on my 1.6Ghz Duron... Not super fast, but nothing to complain about.

      (Using Fedora Core 3, gedit 2.8.1)

      How did you managed to slow it down to 4-5 seconds?

    78. Re:Engineering within limits brings great results by RedWizzard · · Score: 1
      You weren't doing the sort of seamless multitasking I can do now in Photoshop
      Care to elaborate on what you mean by that? The Amigas didn't have memory protection, but the multitasking was as real and seemless as OS X, Linux on XP.
    79. Re:Engineering within limits brings great results by kkith · · Score: 0

      gawd...blah blah blah...how cliche.

      You just HAD to be the first geek to talk about the "OLD" days...

      you know what tho...NOONE CARES!

    80. Re:Engineering within limits brings great results by Anonymous Coward · · Score: 0

      There's always two sides to this argument - and I agree with the Mel story - quite funny.

      I saw a whip with C++ write a program that took -5- minutes to read in a data file and display it on an 800x600 display as vectors with associated data in ASCII. I was asked to improve the reading performance when he moved to another project.

      I viewed his code - very elegant, polymorphism, multiple inheritance, template classes, strongly typed elements - wow! This was shmick code.

      It was then I noticed that he was
      - creating a 1 byte array, copying the first element into it
      - Creating a 2 byte array, copying the first array into the second array, then deleting the first array.
      - etc. etc. etc.

      So I calcualted the file size, pre-allocated the memory (with checks) and voilais! The reading time went from 5 minutes to 2 seconds [for a large file]

      Now that little story just goes to show you that there are instances where efficiency can be improved - and that was the WORST example of many, many examples i've seen over the years.

      Anyone heard of pass by reference?
      Your Friendly Neighbourhood

      AC

    81. Re:Engineering within limits brings great results by arkanes · · Score: 1

      You weren't doing it because the hardware wasn't there - anyone who claims to be able to simultaneously edit (and switch between, with no delay) 100 images on a 512k Amiga is deluded or lying. But I can do it no problem with a high end G5. Or an XP machine. Or with GIMP, etc, etc.

    82. Re:Engineering within limits brings great results by tomhudson · · Score: 1

      Bet your laptop is a centrino - most of them are slow as shit (like how the P4s are slower than the PIIIs for the same clock, and how Intel's original argument that they have more room to grow - to 10ghz - was shown to be wishful thinking).

    83. Re:Engineering within limits brings great results by JesseL · · Score: 1

      If you had actually read through the document to the conclusion you would see that the second amendment secures an individual right to keep and bear arms. The militia clause is explanatory but without function with regard to how the right is applied. You don't have to be a member of the press to enjoy the protections of the first amendment, do you? Also you may note that the unorganized militia is legally composed of all able bodied adults.

      --
      "Prefiero morir de pie que vivir siempre arrodillado!"
    84. Re:Engineering within limits brings great results by RedWizzard · · Score: 1

      Ok, I see. You meant multitasking as in a person doing more than one thing at a time, not multitasking in the technical sense of the capabilities of the OS.

    85. Re:Engineering within limits brings great results by tolan-b · · Score: 1

      I'm not saying it's not legally the case, I'm just talking about the intention.

      And isn't it 'well organised militia' not 'unorganised militia'?

    86. Re:Engineering within limits brings great results by JesseL · · Score: 1

      It's "well regulated militia", meaning "properly equipped and practiced" by the phraseology of the late 1700's, not "managed and organized".

      --
      "Prefiero morir de pie que vivir siempre arrodillado!"
    87. Re:Engineering within limits brings great results by ksiddique · · Score: 1

      I'm always amazed how, over time, console developers can make the most of the hardware. Compare Super Mario 1 and Super Mario 3 on NES.

    88. Re:Engineering within limits brings great results by Sri+Lumpa · · Score: 1


      Good point, it's not so much a proof as a theory otherwise I would be at least a million dollars richer from proving that NP != P.

      However if you really believe that there are no algorithms that are the best and can be proven to be slow then you are welcome to prove it by finding faster algorithms for any of the current best algorithms that are slow (like factorising large non-prime numbers).

      I guess the original poster should have been more careful and say the best *known* algorithm can sometimes be proved to be slow.

      --
      "The obvious mathematical breakthrough would be development of an easy way to factor large prime numbers." Bill Gates,
    89. Re:Engineering within limits brings great results by Surt · · Score: 1

      Yeah, that was my probably overly pedantic point, but it did sound to me like the grandparent was trying to claim that some problems were proven to require slow solutions.

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
  8. Please, captain... by salvorHardin · · Score: 3, Funny

    ...I cannae change the laws'a'physics!

    1. Re:Please, captain... by cnettel · · Score: 2, Funny

      Bah, just use a tachyon burst followed by a concentrated tetryon beam.

    2. Re:Please, captain... by 91degrees · · Score: 2, Funny

      Anyone ever felt that was a bit rich coming from a TV series where the whole premise was based on changing the laws of physics?

    3. Re:Please, captain... by cnettel · · Score: 1

      It's like (unhacked) DVD regions, you can only change them so many times, then you have to stick to what you've got.

  9. 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.

    1. Re:Least of your worries by DaHat · · Score: 1

      To quote Avery Brooks from the ~5 year old IBM commercial, "It is the year 2000 and I was promised flying cars, where are the flying cars? Where? Where? Where?"

    2. Re:Least of your worries by DataCannibal · · Score: 1

      Hover cars ????

      I expected a flying car, or a jet pack at the very least.

      And you forgot Professor Nuclear Power: "...and in the future electricity will be so cheap it won't even show up on your meter"

      There's something wrong with my fucking meter. as well

      --
      No but, yeah but, no but...
    3. Re:Least of your worries by Thud457 · · Score: 1
      "Too cheap to meter" turned out to have problems.

      If something's too cheap to meter, how do you charge them for it?

      --

      the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

    4. Re:Least of your worries by itsnotthenetwork · · Score: 1

      Yeah ! And Video phones. Where is my video phone.
      Although, I'm not sure I would want to see what some people are doing while I'm talking to them on the phone.
      And, it would really hurt to crash a flying car.
      All the drunk drivers would be drunk flyers.
      Maybe it is a good thing we don't have these.

    5. Re:Least of your worries by Anonymous Coward · · Score: 0

      The same way you charge for broadband?

      $50/month no limits (hahaha) access.

    6. Re:Least of your worries by sacherjj · · Score: 1

      When anything is too cheap to meter (or it cost to much to meter down to the single consumer) then a blanket cost is applied to all. This occurs in apartment complexes for water and sewer. They can't track usage by unit, so they throw a little onto the rent to cover it.

    7. Re:Least of your worries by Anonymous Coward · · Score: 0

      I can't beleive it! You are charged for that???
      I just can't beleive you have a f***ing meter!

    8. Re:Least of your worries by lbmouse · · Score: 1

      You've watched too many episodes of the Jetsons.

    9. Re:Least of your worries by dustinbarbour · · Score: 1

      I think it goes like this.. We were promised that all these inventions (computer, nuclear energy, etc) would make our current tasks much, much easier which they have. I'm sure I can accomplish the same bookkeeping work in an hour that would have taken 6 hours in 1950.

      The problem is that employers noticed this trend too, but they saw it differently. Instead of getting the same amount of work done in less time, they saw more work done in the same amount of time.

      But I guess that was inevitable. Most people get paid hourly and not by the amount of work they accomplish. So I guess we, the employess, are to blame!

    10. Re:Least of your worries by matt-fu · · Score: 1

      Most of the people I know only get five hours worth of useful work done per week anyway.

    11. Re:Least of your worries by pizza_milkshake · · Score: 1

      i loved that ad.

  10. Hardware resources and software design by SIGALRM · · Score: 2, Insightful
    Make a CPU ten times as fast, and software will usually find ten times as much to do (or, in some cases, will feel at liberty to do it ten times less efficiently)
    I find that software designers often do not take resource limits seriously. Programming is tedious, hard work. The algorithms chosen *are* important, and in some cases you shouldn't simply reach into the API toolbox and use the third-party solutions. There is no substitute for knowing how to write your own sort routines, specialized linked lists, and binary trees.
    --
    Sigs cause cancer.
    1. Re:Hardware resources and software design by Derkec · · Score: 2

      Right. But you also need to know when to write your own optimized software and when by using the API toolbox you won't cause much slowdown and will be able to deliver faster and cheaper.

      I would also observe that programmer can be a lot of fun.

    2. Re:Hardware resources and software design by cmburns69 · · Score: 1
      I find that software designers often do not take resource limits seriously. Programming is tedious, hard work. The algorithms chosen *are* important, and in some cases you shouldn't simply reach into the API toolbox and use the third-party solutions. There is no substitute for knowing how to write your own sort routines, specialized linked lists, and binary trees.


      When designing commercial software, there are basically 2 factors related to this: 1) Does the application really require bleeding-edge performance (extremely low resource usage) and 2) If we take the time to do it right and consequentially takes longer to bring to market, will a competitor gain an advantage?

      The choice is highly dependent on the type of project you are developing. Optimized games and server products gain a marketplace advantage over their lesser-optimized brethren. But in most consumer markets, software has become a commodity and high performance isn't really a selling point. Nobody really wants to pay extra for a word-processor that can spell check twice as fast.
      --
      Online Starcraft RPG? At
      Dietary fiber is like asynchronous IO-- Non-blocking!
    3. Re:Hardware resources and software design by Steve+Embalmer · · Score: 0

      The algorithms chosen *are* important, and in some cases you shouldn't simply reach into the API toolbox and use the third-party solutions

      Here, here! That's exactly the reason why a technical degree is a plus: you are going to get practice with these techniques and algorithms--if it's a good school.

    4. Re:Hardware resources and software design by hng_rval · · Score: 3, Insightful

      There is no substitute for knowing how to write your own sort routines, specialized linked lists, and binary trees.

      What about knowing how to use the libraries that have these functions built in, such as the stl? You might not be 100% as efficient with the libraries, but you can be sure that those libraries are tested and optimized, and if you write these functions yourself, they might be buggy and will most likely be slower than the what comes with the compiler.

      --
      Thank you Mario! But our princess is in another castle!
    5. Re:Hardware resources and software design by gUmbi · · Score: 3, Insightful

      There is no substitute for knowing how to write your own sort routines, specialized linked lists, and binary trees.

      Hogwash! Write first, optimize later...or in the real world: write first, optimize if the customer complains. Even then, what are the chances that I can write a better sorting algorithm than one included in a standard library that was written by some who studied sorting algorithms? Close to zero.

    6. Re:Hardware resources and software design by UpLateDrinkingCoffee · · Score: 1
      While I agree with the gist of your comment, I think all sorts of red flags need to go up if you are finding yourself re-implementing freely available API's, even if they aren't exactly the code you had hoped for. Of course there will be special situations that call for finely tuned custom algorithms, but these situations are few and far between for most of us.

      More projects fail because of a bloated code base and the cascading stream of problems that causes than poor performance. Unless the fundamental architecture is completely screwed, performance bottlenecks are usually pretty easy to find and fix if time is allotted to that exercise.

      Don't bloat the code!

    7. Re:Hardware resources and software design by SIGALRM · · Score: 1
      When designing commercial software, there are basically 2 factors related to this
      I agree with the two questions you pose, but there are many more to ask. Design and implementation techniques depend on project size, organization, build and configuration process, the special role of project tools, and testing strategies.

      At any rate, any non-trivial software project should have it's design assumptions mercilessly decomposed. As you said, it's highly dependent on the type of project, but the questions are still much the same.
      --
      Sigs cause cancer.
    8. Re:Hardware resources and software design by SIGALRM · · Score: 3, Insightful
      Hogwash! Write first, optimize later
      No, you cannot retrofit quality and performance into a software project.

      what are the chances that I can write a better sorting algorithm than one included in a standard library that was written by some who studied sorting algorithms? Close to zero
      Maybe so, but it can (and should) be done in specific cases. For example, I maintain a library of binary tree functions, and I do use them frequently. They are well tested and perform beautifully. However, a project I completed recently required a large amount of data to be traversed in a specific manner, so we designed and built our own BTA--specifically optimized for the task.

      As you know, poorly designed code will bubble up through the code and bite you in the end... and your project will suffer from it.
      --
      Sigs cause cancer.
    9. Re:Hardware resources and software design by TomorrowPlusX · · Score: 1

      While I agree 100% it is also smart to know when 3rd parties are smarter than you.

      I avoided the STL for a long time, assuming I could hack out simple, lightweight containers as I needed. Turned out I often a) Made dumb mistakes b) Wrote code that wasn't any faster than, say, std::whathaveyou, and c) Wasted time that could have been better spent on algorithms.

      Stuff like the STL, Boost, etc are written by SMART people who know what they're doing. Don't assume that because it's generic it's inefficient.

      That said, even if you're using 3rd party stuff, any programmer worth employing should know how to roll it himself, should the need arise.

      --

      lorem ipsum, dolor sit amet
    10. Re:Hardware resources and software design by __aagujc9792 · · Score: 1

      What nonsense. These structures are implemented in the C++ language spec. You might as well say you have to know how to wire a half-adder.

    11. Re:Hardware resources and software design by Anonymous Coward · · Score: 0

      This good school you speak of, it would have also shown you that the expression is 'hear, hear'.

    12. Re:Hardware resources and software design by NSash · · Score: 1

      You might as well say you have to know how to wire a half-adder.

      You should.

    13. Re:Hardware resources and software design by fitten · · Score: 1

      Hogwash! Write first, optimize later...or in the real world: write first, optimize if the customer complains.

      Unless your software performance issues are architecturally rooted, in which case you will write first, then rewrite later (much more expensive).

    14. Re:Hardware resources and software design by akuma(x86) · · Score: 1

      >> I find that software designers often do not take resource limits seriously. Programming is tedious, hard work.

      The reason they don't take resource limits seriously is because they're getting resources for damn near free. Hardware capability increases exponentially at the same cost point over time. Why waste your VALUABLE engineering time optimizing a problems that the hardware solves for you?

      This article is claiming that the gravy train of free resources is over and programmer will have to think again.

    15. Re:Hardware resources and software design by Bigby · · Score: 1

      I second that. You should know how, whether you know you will or not. If you know how the computer internals work, then you'll write better code.

    16. Re:Hardware resources and software design by l3v1 · · Score: 1

      And what would be wrong with that one ? :) There are many many of us who know both (be that algo or adders wiring). Thing is, you have to keep a clear head and recognize the situations where you are ok to use 1). your implementations 2). libraries like stl. On time pressure, libraries can save your a$$, that's for sure :) Otherwise, always consider all your options.

      I have a bit offtopic but still amusing (in a peculiar way :)) story regarding library use. It happened on an interview for a coder's job. I had to complete some test before anything else. I had a pretty good score, then in one of the verbal interviews a coder guy asked me what I knew about STL. Well, I told him all about STL, then I said I don't really use it (which was quite true). He looked a bit shocked to say the least :) when I explained I trust my code better :) when I have the time for it. Well, times have changed since then - not regarding my trust in my code :) - (btw, the job was offered, but I declined because of another) and I use everything that can save me time these days.

      I find it sad though that most greenhorn coders think the word "optimization" is just an archaism associated with commodores and z80's, with hacking and scene quarters.

      --
      I am putting myself to the fullest possible use, which is all I can think that any conscious entity can ever hope to do.
    17. Re:Hardware resources and software design by angel'o'sphere · · Score: 1

      Tzzz, how can that eb insightful?

      While I agree with your view that k. The algorithms chosen *are* important

      I find this really silly: There is no substitute for knowing how to write your own sort routines, specialized linked lists, and binary trees.

      So suppose I'm a complete dumb ass and you are a genius. How big might the diffrence between your linked list implementation and mine be? Factor 10? So your linked list is ten times faster than mine? And what do you gain from that?

      A programmer has to descide wether a linked list is the correct data structure. He has not necessaryly to be able to craft that datastructrue. Indeed I favour the programmer who uses the standard of the shelf API given for his language. E.G STL in C++ and java.util.X in Java.

      Why? Its very easy to replace the STL typedef for the whole program when a replacement implementation (yours probably) should be used but its completely impossible to replace "programmer invented" "super special" datastructures in a consistent way in an application written by a team or over a long time.

      While the algorithms are important, they likely are the latest to optimize. The first thing which is important is a clear interface to your "algorithms" and a clear datastructure (class/struct) for your data.

      With the interface you can optimize behind the interface (adapt your algorithms) and you can refactor in front of the interface (business logic). And thats where the money goes ore comes from, business. Not from "my superb selv invented", but "for thousend times reinvented" linked list derivation.

      angel'o'sphere

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    18. Re:Hardware resources and software design by arkanes · · Score: 1
      I understand where you're trying to go here, but you examples are outright wrong, especially the sort. Unless you're a Donald Knuth or something, it's very unlikely that any sort routine you hand-code is going to be better-implemented than ones you can find provided in standard libraries. Sort in particular is a case where there's very little benefit to be gained from tuning for implementation-specific data. Customized data structures are a different matter, because there's lots of space/performance tradeoffs you can make (like single vrs. double linked lists, just to pick the most obvious) so it's worth making your own sometimes. That's not much if a "specialized" link list, though, and rolling your own list has very little to do with your choice of algorithms and your implementation of same.

      I see a lot of programmers who like to strut about how much they care about performance and how they never use third party libraries, forgetting that these libraries are generally written by people much, much smarter than them who actually understand the tradeoffs and issues involved. The STL is a good example of this - there certainly are tradeoffs made, and they're well documented so you can make informed decisions and you can even make domain-specific optimizations without losing the benefit of the libraries algorithm implementations.

      That's not to say that there aren't poor third party implementations. But if you write your own quicksort or string copy or any of these sort of basic well known operations all the time, then you need to be smacked with a clue stick. You're a peacock who doesn't know what he's doing.

    19. Re:Hardware resources and software design by Anonymous Coward · · Score: 0

      Always write the first one to throw away; you're not going to keep it anyway. Paraphrased from Fred Brooks, I believe.

    20. Re:Hardware resources and software design by corngrower · · Score: 3, Informative
      Hogwash! Write first, optimize later...or in the real world: write first, optimize if the customer complains.
      Supposing that you need that first sale of your system to a customer, and when they demo your software, they see it's so slow that they dismiss it and buy the competitor's product. You don't have a second chance. This actually happened with a company I know of. The company pretty much went tits up because the architect neglected performance.

      Even then, what are the chances that I can write a better sorting algorithm than one included in a standard library that was written by some who studied sorting algorithms?
      I don't necessarily need to write the sort algorithm, but I need to be concerned with the effect of using the various algorthms on my system and select the corrrect one accordingly.
      Again, that company that failed went with using a standard library for some functionality in the product instead of rolling their own and this had disasterous results. After the customer complained about performance, they found that they'ld need to completely redesign a significant portion of the product to correct the problem. It wasn't a two or three day fix. The fix would have taken 1-2 months. Try eating that cost when you're a small company.

    21. Re:Hardware resources and software design by 91degrees · · Score: 1

      Most standard tools and libraries are realy quite efficient in a general case. In fact, my observations suggest that not using them will cause an indirect slow down. A lot of the software I use uses slow searches because they're good enough, and nobody can be bothered to implement a binary search for a marginal speed increase.

      If we used a library with the binary search capability in the first place, the performance would probably have been better, even after the overhead caused by the algorithm beingtoo generic.

    22. Re:Hardware resources and software design by Anonymous Coward · · Score: 0

      As someone who knows how to wire not only a half adder, but a propagate-generate adder, and a matrix multiplier and high radix divider, and has done timing analysis of analog circuits and digital critical paths, I would say your average programmer doesn't. The whole point of abstraction and the revolution that is digital logic is that you focus on what's important, which is what your doohickey does, not how it does it. You still need to know the limitations of the device if you want fast performance, but, as long as you conform to the spec, you should always at least get correct behavior.

      Programmers have no way to manipulate half adders anyway; if you could somehow eke out extra performance from the design by executing addition with certain operands rather than others, there's probably a bug in the processor itself, because that means some operands will take longer, and you won't be able to use synchronous digital logic to achieve those results. This, of course, ignores the whole point that programmers are rarely called upon to code hand assembly addition routines/instructions these days.

      Knowing everything is important in analog design, where a little tweak in one part of the system can have a cascading effect on everything else, but analog design is also insanely hard.

      I think this is really just /. kneejerk elitism; "I know how a half adder works, you hapless slob, so that makes me a superior programmer. Nyea nyea." In most cases, it probably doesn't.

      While the basic principles of a half adder should be easy enough for anyone familiar with Boolean logic to devise (something I think every programmer should actually know, but mostly because it's sorta critical to figuring out how to write any sort of logic), there's certainly almost no cause for your average programmer to care.

    23. Re:Hardware resources and software design by corngrower · · Score: 1
      I did one time work on a project where the STL classes caused a significant performance hit to the software for certain operations (on one partcular CPU architecture). In this particular spot in the source, the container and iterator code was hand written to avoid the performance hit.

      Don't assume that the STL code will be the most efficient ALL the time.

    24. Re:Hardware resources and software design by psetzer · · Score: 1

      Or, as others have said: "Premature Optimization is the root of all sorts of evils." You don't want to think of the number of problems that could have been averted if someone had thought to write out their algorithm simply and abstractly first. Then they could profile it, find where the bottlenecks are, and fix them. Most of the 'carefully hand optimized' code of yesteryear was shotgun optimization: Try speeding things up until the program actually runs fast. By the time they finally hit the actual problem or got the speed to a reasonable level, they'd already gone through most of the code. You think they'd have done that if they knew that it was screen updates taking up 95% of their processor time? I don't think so.

      --
      "Anyone who attempts to generate random numbers by deterministic means is living in a state of sin." -- John von Neumann
    25. Re:Hardware resources and software design by obender · · Score: 1
      Even then, what are the chances that I can write a better sorting algorithm than one included in a standard library that was written by some who studied sorting algorithms? Close to zero.

      Sounds like you fell asleep well before the third volume of taocp.

    26. Re:Hardware resources and software design by Anonymous Coward · · Score: 0
      what are the chances that I can write a better sorting algorithm than one included in a standard library that was written by some who studied sorting algorithms? Close to zero.

      Actually it's rather easy to outperform (say) qsort() in a typical application written in C on most platforms. If you know what you're doing and can't get at least a factor of 2 or 3 you're just not trying very hard. Library routines are often written for more generality (& less efficiency) than you need.

    27. Re:Hardware resources and software design by __int64 · · Score: 1

      Hogwash! Write first, optimize later...what are the chances that I can write a better sorting algorithm than one included in a standard library that was written by some who studied sorting algorithms? Close to zero.

      Now whose fault is that? hmmmm?
      Hopefully you just misread the grandparents post because it sounds like your proclaiming that through ignorance we can write more efficient code.

      "There is no substitute for knowing how to write your own sort routines, specialized linked lists, and binary trees"

      And he's right, there is no substitute to understanding how the things you use work -> it's how you know to use them effectively. Skilled programmers write faster programs than noobs because they understand how the hardware works; no exceptions.

      And this is the root of the problem; with all the excess CPU 'speed' lying around in the 90's programmers got lazy and the next generation were born even lazier. Why bother learning to write faster code when in 6 months it will be fast.
      Just as a test how many people in your code farm actually know O(n) and other simple methods of algorythmics?
      Furthermore the standardized general solutions found in API's and libraries are just that -> solutions for general problems. They're most certainly not optimized for unique cases inside your application; thus leaving huge benefits un-reaped.

      And this is why I'm not worried about outsourcing; there are millions of programmers out there but very few good ones. And good programmers are employed. And according to this article will be in higher demand than ever before.

    28. Re:Hardware resources and software design by TomorrowPlusX · · Score: 1

      I don't -- I sped up some of my code once by a factor of about 10 by going *from* std::vector to a vanilla new'd array.

      But most of the time STL is shockingly fast, and correct. Just make certain you use the right access/iteration semantics for the container type.

      --

      lorem ipsum, dolor sit amet
    29. Re:Hardware resources and software design by Chembryl · · Score: 1

      ... and how long would it have taken that same small company to design test and build that customized sorting algorithmn? Add that to the design of the application itself and I'll wager that the same small company did not have the time nor resources to even consider it.

      --
      - This and all my posts are public domain. I am a Physicist. I am not your Physicist. This is not Physically advice
    30. Re:Hardware resources and software design by Anonymous Coward · · Score: 0

      No, you cannot retrofit quality and performance into a software project.

      And so linux is intrinsically doomed to never be high performance?

    31. Re:Hardware resources and software design by Anonymous Coward · · Score: 0

      I understand where you're trying to go here, but you examples are outright wrong, especially the sort. Unless you're a Donald Knuth or something, it's very unlikely that any sort routine you hand-code is going to be better-implemented than ones you can find provided in standard libr

      Donald Knuth is great computer scientist not necessarily a great computer programmer . As such, I'm sure Carmack (of ID software fame) could out code Knuth any day.

    32. Re:Hardware resources and software design by Anonymous Coward · · Score: 0

      "Supposing that you need that first sale of your system to a customer, and when they demo your software, they see it's so slow that they dismiss it and buy the competitor's product. You don't have a second chance. This actually happened with a company I know of. The company pretty much went tits up because the architect neglected performance."

      While that's a valid point, most folks in the biz understand about "first mover advantage". It's far, far better to get something out there FIRST than it is to spend time in development trying to speed things up.

      If you lose the first mover advantage, you've lost a tremendous amount. One can always replace lost money. One can NEVER replace lost time.

    33. Re:Hardware resources and software design by ChrisPee · · Score: 1, Insightful
      No, you cannot retrofit quality and performance into a software project.
      Quality != performance != speed. A better quality metric for most modern software is clarity of design. With clearly and cleanly designed modules and interfaces, speed improvements CAN be retrofitted. Without this clarity, a secure, reliable and bug-free program cannot even be tested for, much less achieved.
    34. Re:Hardware resources and software design by ObsessiveMathsFreak · · Score: 2, Interesting

      No, you cannot retrofit quality and performance into a software project.

      Quality does not nessessarily mean optimised code. For many customers it is more important to get code that works, doesn't crash and gets there yesterday. And if it's slow they'll either wait for an update or their next 10GHz PC! :E

      Efficient code is a part of quality, but how important it is depends greatly on the customer. For video games and email servers, very important, for kernels... well we'd all rather a secure kernel that doesn't crash over an dodgy uber effient one. At least.... I would anyway.

      Like all things it depends on what you want and what the programmer can realistically deliver.

      --
      May the Maths Be with you!
    35. Re:Hardware resources and software design by swimmar132 · · Score: 1

      If performance is going to be an issue, then the design specs should indicate what performance is needed.

      Otherwise, you could spend 5 times as long making the code go 25% faster for no good reason at all.

    36. Re:Hardware resources and software design by corngrower · · Score: 1
      and how long would it have taken that same small company to design test and build that customized sorting algorithmn?

      In my estimation - the same amount of time, possibly a week less.

    37. Re:Hardware resources and software design by corngrower · · Score: 1

      Correct. I estimated that the program should have been at least 80% as fast as its competitors. It was only 20% as fast (5 times slower).

    38. Re:Hardware resources and software design by mikeg22 · · Score: 1
      No, you cannot retrofit quality and performance into a software project.
      Maybe not quality, but you can certainly retrofit performance into a software project. In fact, I would say its preferable that way. Worry about sound structure the first go-around, identify the performance bottlenecks, and then retrofit them with the overall structure/security/modularity always in mind. Otherwise you may end up spending many orders of magnitude of the amount of time optimizing chunks of code that don't have a real effect on the overall performance of the program, and you can end up with some very unmaintainable code in the process. I'd say with most projects I've worked on, maybe 5% of the code accounts for 95% of the resource use. You don't always know where that 5% is going to be until the project is relatively far along, as requirements and specs can constantly change.
    39. Re:Hardware resources and software design by Hognoxious · · Score: 1
      Hogwash! Write first, optimize later
      No, you cannot retrofit quality and performance into a software project.
      Quality is not the same thing as performance, and if you have the former (good decomposition, loose coupling) you've made it much easier to do the latter.
      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    40. Re:Hardware resources and software design by Hognoxious · · Score: 1
      Supposing that you need that first sale of your system to a customer, and when they demo your software, they see it's so slow that they dismiss it and buy the competitor's product.
      Then you should have used magic, i.e rigged the demo.
      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  11. It'll still crash by turtled · · Score: 0

    It'll still crash, just faster. how about having M$ catchup on the 2005 technology brfore jumping ahead?

    --
    "I cannot think of any need in childhood as strong as the need for a father's protection." -- Sigmund Freud
    1. Re:It'll still crash by Anonymous Coward · · Score: 0

      baaaaaaaaaah.... baaaaaaaaaaaaaaaaaaaaaaaaaaaaaa..

      is grass really that tasty

    2. Re:It'll still crash by nospmiS+remoH · · Score: 1

      I can see the future now:

      - 1.0 Tbps Cable Internet
      - 10 GHz processor

      New PC with Windows Longhorn installed is compromised before the usere lifts his or her finger off the power button.

      --
      !hoD
    3. Re:It'll still crash by canofbutter · · Score: 1

      I don't belive that Longhorn would boot fast enough for that even with a 10GHz processor

  12. And where is my Jetson's car! by Evil+W1zard · · Score: 2, Interesting

    There will always be points where technology slows down because it invariably will have to go through some total redevelopment instead of just building upon current products (like what they will be doing with the space program.)

    --
    News Reporters Make Tasty Polar Bear Treats!
    1. Re:And where is my Jetson's car! by Jeff+DeMaagd · · Score: 0, Offtopic

      I don't trust drivers on two dimensions. 40k people in America die in auto accidents per year already.

  13. Legal Tender by SomeoneGotMyNick · · Score: 1, Funny

    we now have to come up with some concurrency, but all I have is dollars... What gives

    CONcurrency is short for Confederate Currency. Your ancestors used the old notes to light cigars after the Civil War.

    Then again, you might need to use laundered money. That's also called concurrency.

    1. Re:Legal Tender by TheVampire · · Score: 1

      I thought concurrency was ciggarettes!

    2. Re:Legal Tender by Anonymous Coward · · Score: 0

      Mod him up! He said M$!!!

    3. Re:Legal Tender by derrith · · Score: 1

      But, can you have laundered confederate concurrency? What would that be?

      --
      why does the porridge bird lay his eggs in the air?
    4. Re:Legal Tender by SomeoneGotMyNick · · Score: 1

      I thought they used the Bend Over Barter System.

  14. Harbinger of doom! by Heftklammerdosierer! · · Score: 1

    If the main processor can no longer be relied on to become continually faster to support perpetual feature bloat and inefficiency, how long until someone offers a FBPU?

    1. Re:Harbinger of doom! by Anonymous Coward · · Score: 0

      I've had completely enough of this doom harbinging. Can't anyone harbinge any happiness or prosperity?

  15. Because we all know by Anonymous Coward · · Score: 0

    that clock speeds are the one true and accurate method of determining computing performance, so if the clock speed isn't faster, it must not be better.

    Gee, thanks Intel Marketing Department.

  16. Hooking a 10GHz CPU to a front side bus... by BrakesForElves · · Score: 1

    ...running nearly twenty times slower sounds a little like hooking a 1,200 horsepower supercharged nitromethane-burning Hemi to a set of bicycle tires. With either one, if you can't "hook it up", what's the point?

    --
    About the word "if": If bullfrogs had wings, they wouldn't bounce around on their little green butts.
    1. Re:Hooking a 10GHz CPU to a front side bus... by slart42 · · Score: 0

      I for one could imagine having a lot of fun with those 1200hp hemi-powered bicycle-tires :)

    2. Re:Hooking a 10GHz CPU to a front side bus... by Dano+Watt · · Score: 1

      I'd assume that if they could get the cpu to run at 10GHz, it wouldn't be that much harder to get the fsb to run at a decent speed.

    3. Re:Hooking a 10GHz CPU to a front side bus... by Anonymous Coward · · Score: 0

      and where exactly did you get your EE, genius?

  17. 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 t_allardyce · · Score: 0, Flamebait

      The Java industry would die within months and old C/C++ programmers and assembly hackers would be in total demand with many hours of work required.. Hey what are we waiting for!!

      --
      This comment does not represent the views or opinions of the user.
    2. Re:A Good Thing? by Anonymous Coward · · Score: 0

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

      A beautiful subliminally chosen thermodynamic metaphor.

    3. Re:A Good Thing? by Anonymous Coward · · Score: 0

      I built my current machine two years ago, and I am still using it as a primary machine (I have secondary, tertiary, servers, laptop, etc, as well!). It's got a 2GHz AMD processor (admittedly overclocked, but that was because AMD were downbinning 2GHz processors!). Right now, I could buy a 2.4GHz AMD processor at the top end. Yes, it is a better processor, and the bus is faster and more efficient, and it could do 64-bit if I wanted it to. There's no need to upgrade yet. It isn't like 5 years ago, where the 3 year old PC would be a P200 and the new machine a P800. I'm expecting that my current PC will last another year before it starts even looking weak in comparison to new machines (3GHz AMD processors), and possibly a year beyond that before upgrading becomes essential (dual-core 2.6GHz processors?) heh.

    4. Re:A Good Thing? by Anonymous Coward · · Score: 1, Funny

      Ahhh - your "back in my day" rants are so refreshing to read as I lounge on the piles of money I make writing java.

      Mods: since I flamed this post, it is flamebait, no?

    5. Re:A Good Thing? by Swamii · · Score: 1

      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!)

      Why are you looking at Microsoft when IE boots faster than FF and MS Office boots faster than OOo? Adobe Reader 6 takes eons to load (v. 7 does too if it doesn't auto-boot the quick loader), Solaris 10 uses up a behemoth 12 GB install, and so on. It seems to me that MS isn't the only one "throwing hardare" at the problem.

      --
      Tech, life, family, faith: Give me a visit
    6. 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. Re:A Good Thing? by Anonymous Coward · · Score: 0

      He's talking about windows, which takes a day and a half to boot on anything less than SOTA.

      Once Win32 is loaded, IE boots semi-quickly.

    8. Re:A Good Thing? by akuma(x86) · · Score: 2, Insightful

      Oh my...where to begin.

      >> 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!)

      Efficient coding is only useful if there is a return on your investment for efficiency. Exponentially increasing hardware capability over time at the same cost point makes this tradeoff obvious. The article is saying the hardware capability will still increase, but the programmer will have to learn to use concurrency to exploit it. This implies a fundamental shift in the single-thread world that we have lived in for a long time now.

      >> 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...

      The only reason a computer becomes obsolete is that something better comes along to replace it. Why else would someone spend money to replace something that's just as good. There must be value there. So, you're saying you want to stop or slow down progress??? Nobody is holding a gun to your head to upgrade. Keep your old computers and the rest of the world will move on and pay for increased value.

      >> 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.

      Processor designers spend ALL their time innovating on new ideas. How do you think each and every new chip comes out faster than the last one? If we don't make a better chip, investors won't give us money to build new ones. It's all we do all damn day - build a better mousetrap. Innovation is part of the job. And "just ramping up clock speed" is pretty damn difficult thank you very much.

    9. Re:A Good Thing? by blackmonday · · Score: 1

      Insightful? Well, no one's gonna disagree that efficient coding is better. Look at OS X Panther reviving 4 year old G3 macs. Today's PCs arent built to last 5 years. Power supplies go out, hard drives die.

      People who downplay CPU speeds obviously don't encode video, record multitrack 96k audio, etc. There's nothing good to come from the PC industry ramping down hardware advances. Apps won't be rewritten. People will lose their jobs. On the contrary, most of us here on Slashdot benefit every day by the computer industry advancing with more and more powerful systems.

      Oh, by the way, Windows XP runs just fine on a 1ghz CPU.

    10. Re:A Good Thing? by t_pet422 · · Score: 1

      (Microsoft; its you I'm looking at!)

      Programmers exploit increased CPU speed. This is NOT just a Microsoft problem. Look at recent releases of KDE and Gnome.

    11. Re:A Good Thing? by Anonymous Coward · · Score: 0

      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!)

      Microsoft doesn't have any percentage in this! At least, up to now. As long as the desktops kept getting faster every year, they could capitalize on the benefits of writing shoddy code and letting the speed/performance increases mask their inneficiency until other aspects (security, stability, etc.) of it began to eat them up. Unfortunately, they now have a decade of such coding to clean up. Do you really think it's going to get any better in the Windows world?

      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...

      You know, I keep seeing this on Slashdot. My personal experience is quite different. I ran several of the small routers on my network (SMC, D-Link and Linksys) and I finally got tired of their shoddy performance. My current router is an old Packard Bell 200M Pentium with 64M RAM running IPCop. The difference in performance was simply astounding! Just browsing the Web felt twice as fast. And stable! I had to reboot each of those little boxes once a day. I haven't touched the IPCop box in months. Until the smaller stuff gets better, I think an entire old computer (that I couldn't recover 1/10 of my initial cost for if I was to try and sell it used) running as a router is very sensible.

      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.

      Look at AMD; they are already sqeezing about 1.5X as much work out of every clock cycle as Intel is. While Intel is running up against the 4G barrier, AMD is running similar performance at ~2.5G. The trend you are looking for has already started.

      Now, as for the premise of this article, I saw this one coming about 2 years ago. When I needed more computing power, I looked into Linux clusters. Rather than building a $2k dual processor screamer, I built a $1.2K 8 station Linux cluster in my basement with simple, stupid X-terminals in a couple of places around the house. Most of the time, a couple of nodes on the cluster are all I need. However, when the occasion warrants, I can fire up the entire cluster and distribute tasks across the cluster. I already have the equivalent of a 10 Ghz processor for many of the time-consuming things I do, like large GCC compiles. Yada, yada, yada, I can already hear the bitching now about comm latency, but a large number of things respond pretty well to this!

      I also agree with the article. Software designers need to spend more time making sure that their software works with concurrency. Several of the largest compile tasks that I want to do (KDE, Mozilla, are you listening?) deliberately disable distributed compiling because of known problems that they haven't chased down and fixed yet.

    12. Re:A Good Thing? by Swamii · · Score: 1

      From login, I can see the desktop in about 3 seconds on my 2GHZ XP machine. The key is to have very few external programs starting up; too many have Office, P2P, BitTorrent, etc. all starting up upon boot, slowing things to a crawl. Again, not MS's fault so don't blame them.

      --
      Tech, life, family, faith: Give me a visit
    13. Re:A Good Thing? by taybin · · Score: 1

      Well, not worrying about inefficiency has helped us write larger and more powerful software. Remember, Python and OOP are "inefficient". I think that generally, we've used the increased power in a good way. I would hate to return to the days when people hardtuned everything. That software was unmaintainable.

    14. Re:A Good Thing? by Anonymous Coward · · Score: 0

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


      Unfortunately for your dream, that "better coloured lighting" is one of the few things which scale at an almost unlimited rate. Serial programs like you run on your Pentium 5,000 don't benefit from massively parallel pipelines, but graphic engines are already pushing up 16+ independent pipelines, and they can do it because each rendered pixel is more or less independent of other rendered pixels. I once read a paper somewhere predicting that this trend would only stop when you had a sufficiently fast processor for every pixel, and a number of pixels equal to the visual fidelity of the human optic system. Needless to say, we're still a long ways off from that.

      By the way, while there's a lot wrong with your post that other people have already addressed, just go back and, say, playing the original SimCity. Sure, great game play, even to this day. But you know what? It's been re-done, and with better graphics, interface, and yes, even gameplay. Some of the enjoyment that your average gamer (including myself) get from games is seeing programmers push the state of the art. It might not do much for gameplay (although you can debate this point), but achieving Pixar-like real time graphics is something I suspect most gamers look forward to.

    15. Re:A Good Thing? by Eric604 · · Score: 2, Interesting
      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!)

      Microsoft's problem is memory usage, every unnecessary byte is processed at least once and is wasted cpu time. Ofcourse, reducing memory usage with huffman crunching won't make anything faster but the relation is clear: inefficient memory usage is a result of codebloat, non-streamlined datastructures, too many protocols/technologies and so on.

    16. Re:A Good Thing? by Dogtanian · · Score: 1

      Why are you looking at Microsoft when IE boots faster than FF and MS Office boots faster than OOo?

      IE "boots" faster? Do you mean "loads"?

      My understanding is that MS Office loads some of its components when Windows starts up, so that it is already partly in memory. I think the same applies to IE (it's "part" of Windows, isn't it?)

      Not that I'm claiming that's a bad strategy, necessarily.

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    17. Re:A Good Thing? by gnuLNX · · Score: 1

      I personally agree with you whole heartedly. As soon as processor speed comes to a halt C++/C/assemble programmers will once again be in the lime light...unfortunately so will FORTRAN...ick.

      Java people get so defensive. They would of course still have their place...just not as big as it is now.

      --
      what?
    18. Re:A Good Thing? by Anonymous Coward · · Score: 0

      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.

      sorry but a PIII-500, 256meg of ram with win98 and office 97 can do all those things and pretty darn speedy for 90% of the people in this world.

      hell my old dual processor P-III 866 machine with U160 SCSI drives is faster responding than most of the new 2.8ghz dells at work.

      people rightly are not buying new machines, it's silly to spend money for features that are not needed.

    19. Re:A Good Thing? by Swamii · · Score: 1

      I have a machine here at work with both MS Office and OOo; while some machines configure office components to start up with the OS, I removed this (I like fast OS boots, don't mind slower app loads), yet MS Office consistently opens faster. Firefox is a touch slower than IE (understandable since the RENDERING ENGINE of IE is built into Windows).

      What I was pointing out in the previous post is that there's a LOT of software, including OSS, that is too reliant on ever-increasing hardware power, not just MS software, as the progenitor post implied.

      --
      Tech, life, family, faith: Give me a visit
    20. Re:A Good Thing? by danila · · Score: 1

      This is obviously false. If there was any tangible benefit in slower development of processors, the market would cause this slowdown. If MS could write better office suit by concentrating on optimising software instead of using more processing power, it would. If Crytek could write better games by optimising code instead of using faster CPU, they would. The fact that everyone seems happy with increasing CPU speeds suggests that this is a better way. We will save the optimisation for 2015. Or 2020. May be AI will do it for us.

      --
      Future Wiki -- If you don't think about the future, you cannot have one.
    21. Re:A Good Thing? by Eric604 · · Score: 1
      Oh, by the way, Windows XP runs just fine on a 1ghz CPU

      i fucking hope so !! And it should run fine as well on 200MHz. 200 MHz is a lot of power for just shuffeling windows, scheduling tasks, managing memory and running an TCP/IP stack.

    22. Re:A Good Thing? by Anonymous Coward · · Score: 0

      Oh, by the way, Windows XP runs just fine on a 1ghz CPU.

      Minimum requirements for Windows 2000 list 133 MHz Pentium. (that's the original Pentium)

      What's the big deal about running on a 1GHz machine?

  18. dual cpu systems by Lawrence_Bird · · Score: 3, Interesting

    since the mid 90s thats all I have built - they really do extend the time before you feel compelled to upgrade. Sure there are not that many apps that run threads on each CPU. But to me a large part of it is that I run many applications simultaneously. With 2 CPU's I rarely get any sluggish feel. And if one app is being especially hoggish I can set it to run on one cpu and flip another important app to the other cpu.

    This time around I also sprung for a hardware raid card and set up a 10 array. That has helped quite a bit with system responsiveness.

    I've also turned off as much eye candy as possible. After a couple days its really not missed and things are much snappier.

    yeah it would be great if I could run out and get some 10GHz chips to fry a few eggs on, but I think my dual MP2200's still have a bit of life in them.

    1. Re:dual cpu systems by t_allardyce · · Score: 2, Interesting

      With multi-cores and such soon all CPUs will be dual/quad CPUs. what would be even better is a hardware interface (like AGP is to graphics) for CPU's instead of this 'sticking it in a socket in the middle of the motherboard' approach, then you could just keep adding more and more CPUs and even keep the old ones (converter boards would let you plug in even older cpus). It would be pretty impressive getting it to work with different memory/cpu/bus speeds and having a fool-proof multi-cpu management system cheaply and in the basic PC specs but damn it would be cool.

      --
      This comment does not represent the views or opinions of the user.
    2. Re:dual cpu systems by Lawrence_Bird · · Score: 1

      the memory part of it is probably the biggest issue. Wasn't there some brooha over the dual core cpus and whether the memory was tied to a single cpu vs a single pool accessible by both?

      I also wonder, while your idea sounds great on face, there
      would probably be a limit for the average person based on
      power and heat constraints.

    3. Re:dual cpu systems by Anonymous Coward · · Score: 2, Funny

      Dude, with a system like that you should be able to move past the Courier typeface.

    4. Re:dual cpu systems by Anonymous Coward · · Score: 0

      what would be even better is a hardware interface (like AGP is to graphics) for CPU's instead of this 'sticking it in a socket in the middle of the motherboard' approach

      That's what I'd like to see. "CPU cubes" with built in memory, CPU, clock, a mini motherboard, but no PCI/USB/firewire/any of that other crap. Just a single high speed low latency interface which works for really short distances (on each side of the cube, of course). Plug 64 of them together into a 4*4*4 cube, and you've got a minature brain in your hands. Any devices could hook up to one of the CPUs on the face of the cube (converting to PCI/USB/firewire/whatever first).

      Of course, you'd have to completely rewrite an operating system to use one of these babies. And I guess you'd need to build in a whole cooling infrastructure.

    5. Re:dual cpu systems by anthony_dipierro · · Score: 1

      Of course, you'd have to completely rewrite an operating system to use one of these babies.

      http://www.beowulf.org/overview/index.html

    6. Re:dual cpu systems by adrew · · Score: 1

      I concur. I bought a dual-processor Mac about four years ago...the twin G4's really aren't that fast (450 MHz each)--but, working together, the machine is still plenty fast and responsive for everything I need to do. I've used a single-processor 933 MHz G4 and it felt sorta pokey in comparison.

    7. Re:dual cpu systems by jawtheshark · · Score: 1
      I think my dual MP2200's still have a bit of life in them.

      That's what I think about my MP2400 too... *BUT* it would be enough that some marketing guy decides that the next big thing will be 64bit (AMD *is* working in that direction) and sooner or later we won't have any software left to run on our SMP 32-bit machines.

      You know that it is enough that most people need to be convinced that they *need* a 64-bit computer to enable such a movement. Instead of "Oooh! It has the double of bits, it must be better". Luckily Intel is lagging behind on the 64-bit desktop market, but when they catch up, we stand there with obsolete machines.

      --
      Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
    8. Re:dual cpu systems by arodland · · Score: 1

      NUMA machines are sweet. And linux is already reasonably adept at running on them, since 2.6.

    9. Re:dual cpu systems by benow · · Score: 1

      I've run dual boards for the last 5 years, and I agree: flexible for upgrades and smoother processing. AMD seem to have caught on, perhaps. I run a dual MP2000+ (erm, or did until the POS AMD fan failed and blew one of them) and the big benefit I'd see moving to a newer ath64 based system is memory/bus speed. However, to have a dual ath64 system is (way) out of my price range. To start requires a dual opteron board (~$400) and a single opteron (~$800+). Having a homebrew dual opteron top-of-the-line box would easily come in at the $3k range after all. Factor in power consumption and it seems that SMP isn't such a great thing. Perhaps dual cores will solve this, or maybe stackable metrinet micro-atx. There is always the athlon xp to mp and wire multiplier hacks (cheap MP2800+s)... I'm going the single ath64 (3500+) route, myself, due to "Cool and Quiet", pci-e and higher bus speed.

  19. Wikipedia as a source by me+at+werk · · Score: 0, Troll

    Did anyone else notice they sourced their Figure 1 from Wikipedia? I know the trolls are already going to agree with the article just to get picked on, but then they'd have to agree with wikipedia, which they can't do because they already are picking on Wikipedia.

    It's a paradox of trolling. What will we do!

    --
    For context, click Parent.
  20. Statistical significance? by Anonymous Coward · · Score: 0

    I'm not sure that graph in the article has any real significance - Nearly all of the 'flattening out' of the curve is in the future, and the remaining part doesn't look *that* discouraging.

    Apart from that.. I'm not sure if it's a major shift - quite a good amount of apps already are multi-threaded. Not to mention the increasing complexity (and thus amount of work done) of operating systems and api layers, which are already running as seperate processes.

  21. OK this is a serious question by Saven+Marek · · Score: 1

    and I am not being negative and glib just passing off the need for faster, PC. When you have speed things will come up to use that horsepower!

    But now say we have 2.5gihz athlon's and G5's and 3.8gihz pentiums and other processors all at respectable speed. They are really very good for many things!!

    What do you all people see as uses for faster PC's if you could have 10gihz on a desktop machine or even laptop. Well video would be one thing that is good. What else would it help to have the speed for? Would it make a real advantage for you to step up for a 10gihz computer? Is it more, important, to have your 500gib and 1tib hard drive space and 8gib of ram with a big monitor??

    Mac Security News

    1. Re:OK this is a serious question by Anonymous Coward · · Score: 0

      I might actually get Macromedia Studio MX to NOT run like a total dog?

      (Doubt it: I have 4 PCs, with varying levels of performance, Studio MX seems to run as slowly on them all...)

    2. Re:OK this is a serious question by SpaceLifeForm · · Score: 1

      One application would be to donate one to SCO so they can find the infringing code sooner.

      --
      You are being MICROattacked, from various angles, in a SOFT manner.
    3. Re:OK this is a serious question by Overd0g · · Score: 0

      Games, you fool.

    4. Re:OK this is a serious question by russellh · · Score: 1

      fault tolerant, dynamic languages will run at acceptable speeds. Things like squeak smalltalk might be useable. Emulation of more recent but obsolete systems will work and be useful. Today's renderfarm will edge toward the desktop, for near-to-realtime 3D of the kind used in movies and print. Machinima movies will approach photorealism for rendering on-the-fly during playback. That will be the intersection of movies and video games, leading to open source movies (so to speak).

      --
      must... stay... awake...
    5. Re:OK this is a serious question by Anonymous Coward · · Score: 0

      Haven't you read cyberpunk? We're going to strap VR goggles to ourselves and wave our hands to fly around a 3-D version of cyberspace.

    6. Re:OK this is a serious question by FireFury03 · · Score: 1

      What do you all people see as uses for faster PC's if you could have 10gihz on a desktop machine or even laptop

      Photo stitching... My Athlon XP 2100+ can spend hours running Sift, Hugin and Enblend to stitch a large panorama together. Of course that also wants nice fast memory since there is lots of data involved.

    7. Re:OK this is a serious question by Anonymous Coward · · Score: 0

      Stop using Macromedia products, problem solved.

  22. just 2 ghz? by GothicX · · Score: 1

    How about a double intel xeon 3 ghz ? should be better.. hehe

    --
    Music is the sedative for mind...
    1. Re:just 2 ghz? by Anonymous Coward · · Score: 0

      Opterons are drastically cheaper, and faster.

    2. Re:just 2 ghz? by fitten · · Score: 1

      Well... not that I'm a Maclot or anything, but two flavors of machine that are 'newish' at 2GHz are the Opterons and the PowerMacs (2.0GHz G5s).

  23. In the backseat of my... by UncleRage · · Score: 3, Funny

    flying car.

    Where else would it be?

    --
    #SickNotWeak
    1. Re:In the backseat of my... by Have+Blue · · Score: 1

      In the wormhole created by my teleporter.

  24. dollars? by ack154 · · Score: 0, Offtopic

    but all I have is dollars...

    They're probably even Canadian dollars...

  25. 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 Tiroth · · Score: 1

      signal propagation time

      Look again, your processor is one heck of a lot smaller than 4 square inches! All that space is mostly fan out to the connectors plus a few resistors/capacitors.

    2. Re:I've always wondered by LiquidCoooled · · Score: 1

      Its the inverse.

      They make the transistors smaller so that it takes less power to switch, and because of the reduction, you also get a reduction in the time it takes.

      However, packing hundreds of thousands of tiny little transistors all switching wildly into a tightly packed arena causes problems.

      Maybe however, your onto something, make the die larger, and make the spacing between larger (but keep long straight pathways) so that the generated heat can be dissapated better?

      --
      liqbase :: faster than paper
    3. 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!

    4. Re:I've always wondered by Anonymous Coward · · Score: 0

      I believe that if you make the core larger, it may actually slow the proc down because they bits have to travel further. Also, when you increase the size linearly, the heat produced goes up exponentially.

      It's kind of like how ants are very strong because they're small. They could not be made larger and still support themselves. Or maybe I've just been drinking far too much.

      Surely someone will correct me if I'm wrong. (Don't call me Shirley!)

    5. Re:I've always wondered by Anonymous Coward · · Score: 0

      For higher frequency processors (GHz and up) the core size will start to matter for a single processor. Speed of light and all that.
      Unless you meant putting multiple processors on a single chip, that could work.

    6. 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.
    7. Re:I've always wondered by VagaStorm · · Score: 1

      How aboute making them taler, like a cpu stak :)

    8. Re:I've always wondered by Anonymous Coward · · Score: 0

      To tie in with an earlier article from today, once on-silicon lasers are used instead of electronic pulses for signals, we're dealing with light speed propagation time. This means your CPU could be spread out over larger areas with little to no performance hit.

      I'm not going to profess that I can understand why you'd want to spread your CPU out over a large area (other than for heat dissipation), but then again, the initial applications of new tech aren't always readily apparent.

    9. Re:I've always wondered by NardofDoom · · Score: 1
      We'd run into issues of getting the electrons across the face of the processor in the time it takes to complete a clock cycle.

      What we'd need then is time zones for the processor.

      --
      You have two hands and one brain, so always code twice as much as you think!
    10. Re:I've always wondered by painandgreed · · Score: 1

      Why the size restraints on processors?

      IIRC, it's because processors are getting so fast that distance is actually becoming important also. Longer path means the longer the signal takes to get down that path. Also, longer path means more heat because resistance is per length. You might make is somewhat easier to disapate heat by spreading out the chip, but you'll cripple it due to travel times and causing more heat by making paths longer. Making things smaller cuts the distance between the circuits and causes less heat due to less material being used. allowing for the increase in speeds. Now that things are so small that the physics of that scale are preventing us from going further, we need another solution. One is making the chips larger by putting more stuff on them so that work can be handled by specialized circuit sets rather than one generic set to handle everything.

      IANACE (I Am Not A Compter Engineer) and it's been ten years since my last electronics class, so feel free to correct me if I'm wrong.

    11. Re:I've always wondered by banausikos · · Score: 0

      But then time zones would give the electrons jet lag!

    12. Re:I've always wondered by coachvince · · Score: 0

      This actually (to my uneducated mind) seems brilliant. If distance is the limiting factor in size, go 3d! Even with a quadrupling of height, you could lose some "floorspace" by putting level to level connectors on 10% of the chip surface, and you'd be ahead of the game.

      --
    13. Re:I've always wondered by untaken_name · · Score: 1

      yeah...you know, that *could* work! In fact, if you had RTFA or if you kept up with tech news, you'd know that processors of this type are currently available. They're called 'multicore processors', and they aren't exactly new (although Intel and AMD won't have them for another year or two).

    14. Re:I've always wondered by Anonymous Coward · · Score: 0


      How aboute making them taler, like a cpu stak :)


      That sounds like a great idea ... until you realize you have just constructed a minature Borg ship.


      Restance is futile. The backspace key will be assimilated...

    15. Re:I've always wondered by Anonymous Coward · · Score: 0

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

      Or higher.

      Current does not flow at light speed. Very fast, but not that fast.

      Individiual electrons can move 'faster than light' though, through quantum tunnelling. Although you could make a good argument that that does not constitute 'travel'.
      (Since to go from one place to another, you have to be in one place, and electrons aren't. They're quantum particles, not classical)

    16. Re:I've always wondered by Anonymous Coward · · Score: 0

      I don't remember the rate at which an electronic signal travels, but the electrons themselves travel very slowly (relatively speaking). If electrons were traveling anything near the speed of light down the wires, they would tear the place up.

      If you have a pipe full of water and apply pressure at one end, water will come out of the other end long before the first bit of water you pushed into the one end of the pipe travels to the other end.

    17. Re:I've always wondered by Anonymous Coward · · Score: 0

      It is erroneous to judge the "size" of the core by the size of the chip package. Many CPU's only take up a fraction of the total space available with actual transistors.

      Don't believe me? Have somebody show you what an Athlon XP core looks like before the heat sink is plopped on top of it. You'll see this tiny square in the middle of a huge chip slab!

      By and large, the package size is a function of the number of pins needed. The physical limits on packing pins closer together are much less forgiving than for transistors. So yes, there's almost always plenty of "room" on a chip to put more stuff on there, but if you give in to this temptation, you will have heat dissipation issues.

    18. Re:I've always wondered by Tiroth · · Score: 1

      Signal propagation time is already 0.67c in most substrates. So light-speed is really only 50% faster.

    19. Re:I've always wondered by benw1979 · · Score: 1

      If they would just make the chips 3D instead of 2D, the size would decrease by a whole dimension! Mwahaha!

    20. Re:I've always wondered by k98sven · · Score: 1

      Rather offtopic, but.. That's a meaningless thing to talk about.

      The valence electrons (ones carrying current) in a metal are delocalized. What that means is that they don't really have any 'identity'. They don't belong to any particular atom, and you can't locate them all individually. You just have a 'fermi sea' as it's called, a kind of electron cloud.

      Now, the analogy to a water pipe isn't bad. But the key difference here is that with a water pipe, you can identify the water going in and coming out (say, add some colorant to the water going in and see when it comes out).

      However, there is no way to 'label' the electrons going in and coming out of a section of wire. Not because we don't know any, but because it's theoretically impossible. If it was possible even in theory to distinguish the particles, then the laws of physics wouldn't allow them to be delocalized - and then the current wouldn't flow.

    21. Re:I've always wondered by Anonymous Coward · · Score: 0

      ...Because then it couldn't be called a "micro" processor. It's purely an aesthetic issue. I heard ,though, at one point in the 80's the Russians had been credited with created the largest microprocessor in the world. They called it a macroprocessor but the name never really caught on ;-).

    22. Re:I've always wondered by Anonymous Coward · · Score: 0

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

      Electricity is light, so it travels at light speed in the medium it's travelling (which is not a vacuum).

    23. 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

    24. Re:I've always wondered by Anonymous Coward · · Score: 0

      Clock speed has *nothing* to do with the speed of light. In fact, it has nothing to do with electron flow either. The drift of electrons is not the speed of light.

      Clock speed is related to how fast a voltage level can propagate across the circuit. You can measure this in picoseconds per millimeter on a chip and picoseconds per inch on a board.

    25. Re:I've always wondered by Anonymous Coward · · Score: 0

      Fortunately, signals do not have to get across the entire chip in one cycle! That is simply not possible at high speed.

      But you will see a surprising trend. Higher speed designs, at the gate level, often *are* bigger than slower speed ones. Why? Because the tools pick alot more smaller gates to get speed and large slow gates when they doesn't have to.

    26. Re:I've always wondered by xRelisH · · Score: 1

      well OK, instead of making it bigger, what if we made it a sphere with the same radius as half the length of one side of a square-ish CPU?

      Wouldn't that reduce distances travelled? I'm sure someone has thought of this before, but has cancelled it out for some major problem that I'm not seeing here.

    27. Re:I've always wondered by anthony_dipierro · · Score: 1

      Current does not flow at light speed. Very fast, but not that fast.

      Of course it does. Electricity is electromagnetic radiation, i.e. light. It doesn't move at the speed of light in a vacuum, but that's because it doesn't travel through a vacuum!

      Individiual electrons can move 'faster than light' though, through quantum tunnelling.

      Quantum tunneling has nothing to do with electrons moving faster than the speed of light. And even if it did, current is not the transfer of electrons, it's the transfer of electric charge. The electrons themselves move very very slowly compared to the speed of light. Think of a flowing hose which is suddenly shut off. The pressure at the other end drops off much faster than it takes for a single drop of water to travel along the hose.

    28. Re:I've always wondered by ZorbaTHut · · Score: 1

      Thanks for a good answer to this on a subject I wasn't sure of - I'd mod you up if I could. :)

      I'd entirely forgotten about the capacitance issue.

      --
      Breaking Into the Industry - A development log about starting a game studio.
    29. Re:I've always wondered by Jon+Pryor · · Score: 1

      Could a processor be made twice as fast if it could be made twice the size?

      In contrast to all the other responses (discussing signal propogation time and other issues), here's a different observation:

      This has already happened (somewhat), and is continuing to happen.

      How so? Adding additional integer and floating point units increases the processor size and performance. As does better branch prediction code. As does Level 1 Cache.

      Then there are the modern marvels such as SMT (aka HyperThreading), or even putting multiple cores onto the same die (see IBM's POWER series, and AMD and Intel will be doing this too).

      The key point of Herb Sutters article is that CPUs will continue to advance (more CPU cores, better HyperThreading, more Cache), will continue to get bigger, but all these advances won't be increasing MHz. Consequently, none of these advances will help single-threaded code. Concurrency is the only way to increase performance now.

    30. Re:I've always wondered by jdgreen7 · · Score: 1
      Only on geek sites will you ever see this phrase:

      light just isn't that fast!

      299,792,458 meters per second never really seemed that fast to me, either. 670,616,629 miles per hour? Bah! My Mitsubishi Eclipse can hit 120!

    31. Re:I've always wondered by Anonymous Coward · · Score: 0

      "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."

      Can you explain how are those two phenomenons exactly alike? I don't see it.

      --BSEE dropout

    32. Re:I've always wondered by Koyaanisqatsi · · Score: 1

      The speed of light may give you an upper boundary, but the real impeding factor it that for a signal to transition from "low" to "high" (or vice versa) you have to deal with the capacitance of the signal paths, and that gives you an RC circuit that takes some measurable time to transit from one state to another (by means of charging/discharging the parasitic capacitances present).

      That's why there's all that fuss about optical signal paths in the silicon, those are not limited by this one factor.

    33. Re:I've always wondered by Anonymous Coward · · Score: 0

      Actually, the L2 cache runs slower because of capacitance; access times for large amounts of memory require charging up address lines. Clock skew has very little to do with it; in fact, modern L2 and even L3 caches run at the same clock rate as the core CPU, just like the L1 cache. Clock rates mainly dictate how fast you can get data out of the cache once you've accessed it, which also depends on how wide you make the data bus, so you've got two paths there.

      Incidentally, there's no reason why you can't propagate a clock signal across several clock cycles. In fact, the Pentium 4 has 2 pipeline stages devoted just to this. Imagine a string of pulses travelling in sequence along a wire... yes, that's pretty amazing, but when you get to the kind of speeds we're talking about, you can do it.

      While clock skew requires an incredible amount of design effort to get right, it's certainly by no means the limiting factor. The main reason why large dies are infeasible is mainly economic, followed by the fact that you need to fit all your logic into a pipeline stage, and longer pipelines have generally lower performance due to longer flush times in the event of stalls (which are fairly frequent).

      The technology Sun's developing in capacitive interconnects solves the economic problem neatly, and you could well imagine entire systems placed in a single package, simply by laying slabs of silicon next to each other.

    34. Re:I've always wondered by k98sven · · Score: 1

      Electricity is electromagnetic radiation, i.e. light.

      No, electricity is the transfer of electric charge, you wrote that yourself. Electrical potential (e.g. voltage) is mediated through photon exchange, and is light.

      But just because the potential is felt at the speed of light does not mean that the current does.
      (which strives to equalize this potential and reach thermodynamic equillibrium)

      Quantum tunneling has nothing to do with electrons moving faster than the speed of light.

      Really, why not? Are you saying that electrons do move faster than light, but not through tunnelling? Or what?

      The electrons themselves move very very slowly compared to the speed of light.

      Speaking of 'the electrons themselves' is meaningless, since in a conductor they are delocalized and have no individual identities. (which they don't really have otherwise either)

      Speaking of the speed of a current is meaningful, speaking of the speed of the electrons is not. You can measure the current speed and divide that by the charge transferred and arrive at a number for the 'speed of an electron', but it's not a very meaningful number.

    35. Re:I've always wondered by mc6809e · · Score: 1
      Of course it does. Electricity is electromagnetic radiation, i.e. light.

      Electromagnetic radiation consists of alternating electric and magnetic fields. That is not what "electricity" is. Electricity concerns itself with the behaviors of positive and negative charges.

      ... current is not the transfer of electrons, it's the transfer of electric charge.



      Current is a quantity of charge moving through an area per second, though I wouldn't call it a transfer of charge.

      Consider a circuit powered by a solar collector. A current flows through the circuit, but how is charge transfered? No. The charge carriers are given energy by the solar cell and this energy is used to perform work. Eventually these carriers find their way back to the cell and are given more energy.

    36. Re:I've always wondered by A.S.M. · · Score: 1

      Eventually (and probably sooner than you'd think) you run into the limits of how fast the signals can travel in the CPU.

    37. Re:I've always wondered by A.S.M. · · Score: 1

      ..And hey, I'm a moron for submitting that without including this link:

      http://www.physlink.com/Education/AskExperts/ae391 .cfm

    38. Re:I've always wondered by iabervon · · Score: 1

      There's also less room to increase transistor count in this direction. If, in ten years, they made processors 200 times bigger than they do today, they'd be bigger than laptops and pretty useless. Additionally, they would take 200 times as much power and produce 200 times as much heat if no other major change happened as well. It's basically just not worth bothering with size when there's not all that much to get out of it (Aside from the other issues with making a chip longer than 1/(6 GHz) on a side).

    39. Re:I've always wondered by rrowv · · Score: 2, Insightful

      > ...which means that signals have to be able > to get from one side of the system > to the other within one clock cycle. In a pipelined CPU (which accounts for nearly all in use today), it will take many many cycles for it to move from one end of the die to the other as the instruction executes. You're right, the bigger the die, the harder it is to have tight clocks if you spread everything out. But its just never done that way...

    40. Re:I've always wondered by funaho · · Score: 1

      > list just isn't that fast

      More to the point, electrons just aren't that fast. Using light would make quite a bit of difference, hence the work on optical computing. :)

    41. Re:I've always wondered by Anonymous Coward · · Score: 0

      Yeah yeah yeah I knew that. Fuck off.

    42. Re:I've always wondered by BigEarzAllMHz · · Score: 1

      Uh, the last time I checked my RF cabling, the electric current that was running through it was only purring along at .81 * the speed of light propagating through a vaccum. That's the "velocity factor" of the cable and any time you have current running through a medium you have some degredation of absolute velocity in relation to the speed of light.

      --
      All science is either physics or stamp collecting.
    43. Re:I've always wondered by anthony_dipierro · · Score: 1

      Electromagnetic radiation consists of alternating electric and magnetic fields.

      and electricity doesn't?

      That is not what "electricity" is.

      Rather than give a complete 45 minute lecture I pointed out the flaw in the parent post using simplified language.

      Current is a quantity of charge moving through an area per second, though I wouldn't call it a transfer of charge.

      You can give a scientific definition, but that isn't going to help someone who doesn't understand the basis of that definition. Again, I'm not presenting a lecture, just a quick explanation.

      Consider a circuit powered by a solar collector.

      That's not what we were talking about in the current discussion. Again, if you want to give out a long lecture on what electricity is, feel free. I just wanted to point out a fundamental flaw in the reasoning of the post to which I was replying.

    44. Re:I've always wondered by jafac · · Score: 1

      The REAL problem is Intel's dominance of the CPU market.

      AMD/Transmeta aside, the dominance of Windows on the desktop, and the x86 platform in general, has translated into a Monopolists' inability to innovate. They've dominated for so long, and have not had a real need to innovate for so long, that the technology has stagnated. This has somewhat affected other players, as they've been starved for demand, which flowed unnaturally uphill towards Intel.

      The other players, however, are starting to gain traction as Intel's failures are beginning to chip away at their image. Itanium, PIV, etc. IBM's jettison of their PC division tells me that Power may soon become a serious player on the desktop. Not just in the Eternal Niche Mac market either.

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
    45. Re:I've always wondered by anthony_dipierro · · Score: 1

      Are you saying that electrons do move faster than light, but not through tunnelling?

      I never said that electrons move faster than light. Are you saying that they do, and that this is due to quantum tunneling?

      Speaking of the speed of a current is meaningful, speaking of the speed of the electrons is not.

      Apparently not.

      You can measure the current speed and divide that by the charge transferred and arrive at a number for the 'speed of an electron', but it's not a very meaningful number.

      It really depends on your purpose. But you're right in this case it's probably best to not mention the speed of "the electrons themselves" in the first place.

    46. Re:I've always wondered by mc6809e · · Score: 1

      "Electromagnetic radiation consists of alternating electric and
      "magnetic fields.

      and electricity doesn't?

      No, it doesn't. You can produce electromagnetic radiation by accelerating a charge, but that's not the same thing.

      So, you can use electricity to produce electromagnetic radiation, but electricity isn't itself electromagnetic radiation.

    47. Re:I've always wondered by anthony_dipierro · · Score: 1

      Well sure, of course, if you want to look at it another way, light only travels in the vacuum in between atoms, and then only at "c", it just slowed down by the constant absorption and re-emission.

    48. Re:I've always wondered by anthony_dipierro · · Score: 1

      "Electromagnetic radiation consists of alternating electric and "magnetic fields.

      and electricity doesn't?

      No, it doesn't.

      So you can have electricity without alternating electromagnetic fields?

      So, you can use electricity to produce electromagnetic radiation,

      You can't have electricity without producing electromagnetic radiation.

      but electricity isn't itself electromagnetic radiation.

      Fine. "Electricity is a property of certain subatomic particles (e.g. electrons/ protons) which couples to electromagnetic fields and causes attractive and repulsive forces between them."

    49. Re:I've always wondered by anthony_dipierro · · Score: 1

      Speaking of the speed of a current is meaningful, speaking of the speed of the electrons is not. You can measure the current speed and divide that by the charge transferred and arrive at a number for the 'speed of an electron', but it's not a very meaningful number.

      Actually, what about conservation of momentum, conservation of energy, etc? It's just not physically possible for electrons to be sent at such tremendous speeds. The only plausible scientific explanation is that photons are what is carrying the electricity, not electrons.

    50. Re:I've always wondered by k98sven · · Score: 1

      Actually, what about conservation of momentum, conservation of energy, etc?

      What about it? It is all conserved. I didn't write anything which implies it isn't.

      It's just not physically possible for electrons to be sent at such tremendous speeds.

      In a conductor, the electrons are not 'moving' in any classical sense. It's an oversimplification. One way to look at it is that when one electron leaves the wire, another jumps over and takes its place, and another takes that ones' place and so on all the way to the other end.
      (But that's an oversimplification as well, since they are indistinguishable.)

      The only plausible scientific explanation is that photons are what is carrying the electricity, not electrons.

      Photons cannot carry an electrical current. They have no charge. They do, however, mediate the electromagnetic force, which is the force between charged particles (the electrical field).

      But they don't 'carry the electricity'. But you could say that they are what 'pushes' the electricity through the wire.

    51. Re:I've always wondered by ZorbaTHut · · Score: 1

      I don't buy it. Look at AMD, they've been pushing innovation better than Intel has lately.

      The *real* problem is humanity's love of backwards compatibility. And that one you're not going to get rid of, ever.

      --
      Breaking Into the Industry - A development log about starting a game studio.
    52. Re:I've always wondered by jsebrech · · Score: 2, Insightful

      In a pipelined CPU (which accounts for nearly all in use today), it will take many many cycles for it to move from one end of the die to the other as the instruction executes. You're right, the bigger the die, the harder it is to have tight clocks if you spread everything out. But its just never done that way...

      Very true.

      Still, the signal needs to be able to cross the distance of the stage in your pipeline during the clock cycle. Smaller stages still mean you can have faster clock rates, as the intel chips demonstrate. All the clock rate benefits have come by making stages smaller (whether by reducing their functionality, optimizing their design, or shrinking the process). It seems we've reached the limit of how small they can be made, with intel seeing not just diminishing but vanishing returns of reducing the stage size to be able to bump up the clockrate.

    53. Re:I've always wondered by FarHat · · Score: 1

      So you can have electricity without alternating electromagnetic fields?

      Of course, and we do all the time, from cells and batteries.

      You can't have electricity without producing electromagnetic radiation.

      Yes, you can, and we do all the time.

      -F

      --
      At the intersection of computation and biology.
    54. Re:I've always wondered by Anonymous Coward · · Score: 0
      "640 KB OK... .. RESISTANCE IS FUTILE. Press F1 to continue"

      "Aw, dammit. Power it down, Steve."

    55. Re:I've always wondered by Tacky+the+Penguin · · Score: 1

      Now's where I get to make a fool of myself -- especially since my old electromagnetic theory book is stashed away somewhere.

      The two values of interest are dielectric constant and permeability.

      The permeability of free space, by definition, is 1.0. Increasing that (as in using an iron core) increases the magnetic field. Actually, the ration of the B field to the H field (and I forgot the exact definition of those two quantities).

      Since only a couple substances (iron, for instance) have a permeability of much more than 1.0, permeability is generally ignored.

      The dielectric constant increases the amount of energy stored in an electric (E) field (measured in volts per meter). If you slip some glass or barium titanate or something like that between the two plates of a capacitor, it will increase the capacitance, and therefore the amount of energy stored for a given voltage.

      The index of refraction is related to those two constants (no, I don't remember the formula). Generally, we take permeability to be 1.0, and let that part of the equation drop out.

      Therefore, if you know the dielectric constant of glass, you know the index of refraction of glass.

      (By the way, the index of refraction is the speed of light in free space divided by the speed of light in that medium. If something has an index of refraction of 2.0, light travels in that medium at 0.5c.)

      Similarly, the velocity factor (velocity of the signal divided by the speed of light) of a transmission line is calculated based on the capacitance and inductance of the transmission line. The capacitance and inductance are determined by the dielectric constant and permeability of the surrounding medium.

      So, it all comes down to permeability and dielectric constant.

    56. Re:I've always wondered by evilviper · · Score: 1
      When we hit the limit on how small transistors can be made, could processors continue to increase in speed by making them larger?

      Yes, but then they need much more power, and cost much more, and nobody likes that... CPUs could be cheaper and run much faster today, if cooling them wasn't so much of an issue.

      I am, of course, ignoring other significant problems with increasing die sizes. And, putting two cores on one chip, is essentially doing the same thing you are suggesting, though with several advantages.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    57. Re:I've always wondered by anthony_dipierro · · Score: 1

      Of course, and we do all the time, from cells and batteries.

      Cells and batteries utilize electromagnetic fields. In fact, pretty much everything we observe on earth (except gravity) uses electromagnetic forces. Which force would you suggest is predominant in a battery? Weak nuclear?

      Yes, you can, and we do all the time.

      Intelligent discussion, unfortunately you are wrong.

    58. Re:I've always wondered by untaken_name · · Score: 1

      Yeah yeah yeah I knew that.

      Of course you did!

      Fuck off.

      Have a nice day!

    59. Re:I've always wondered by Gob+Gob · · Score: 1

      "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."

      Why waste the energy? Would it not be possible to use a cooling system that recycled then energy to produce some electricity?

      I am sure that having a "power plant" inside a PC would be very costly but so is building the 1st car - its just when they are a commodity item the unit cost is significantly less. Since power will become expensive this sort of research may be a great benifit in the long term. If its is too expenisve for a single PC / Server perhaps a seperate device in a server farm which would draw the heat energy from a group of processors and feed it back. Then perhaps a large design of processor will be a *good* idea (from this limited perspective anyway).

  26. Who needs 10GHz by TychoCelchuuu · · Score: 1

    There are so many areas in which we can improve technology; it's not time to get fixated on GIGARHURTZ when we're coming up against a wall.

    --
    Against stupidity the Gods themselves contend in vain.
  27. 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
    1. Re:Leave Moore's law out of this, please by peragrin · · Score: 1

      >>On the other hand, saying that we're not seeing 10 ghz processors, so Moore's law is broken is wrong.

      Um it's Moore's Theory? Theory's haven't been proven but are just observed & hypothetical states.

      So Moore's theory is finally being broken down 3 decades later.

      --
      i thought once I was found, but it was only a dream.
    2. Re:Leave Moore's law out of this, please by Anonymous Coward · · Score: 0

      It's still just an observation not a law. It's also a poorly supported one.

    3. Re:Leave Moore's law out of this, please by vykor · · Score: 2, Informative

      Theories are explanations about phenomena, supported by evidence and observations. Laws are merely descriptions of phenomena. It's not as if you can eventually promote theories to law. They are two different types of things.
      Moore's Law is a description of semiconductor packing and describes the phenomena of it doubling in a given time period. A Moore's Theory would be if it attempted to explain WHY this occurs.

    4. Re:Leave Moore's law out of this, please by nospmiS+remoH · · Score: 2, Funny
      On the other hand, saying that we're not seeing 10 ghz processors, so Moore's law is broken is wrong.

      Er, huh?

      ** Preemptive response to my post follows **
      Re:Leave Moore's law out of this, please (Score:3, Funny)
      by Future_Child_Poster (723) on Friday January 07, @11:15AM)
      You're new here aren't you?
      --
      !hoD
    5. Re:Leave Moore's law out of this, please by Anonymous Coward · · Score: 0

      Since Moore and his successors have enormous influence over Semiconductor R&D, Moore's "Law" is less of an academic description and more of a self-fullfilling prophecy, or (gasp) business plan. See the article in the arstechnica archives.

    6. Re:Leave Moore's law out of this, please by Anonymous Coward · · Score: 0

      >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.

      Not so. The clock speed is only one part of the equation. You also have bus speeds, data path widths, and architectural advances to consider.

      My Athlon 64 rig at 2.0 Ghz is a great deal faster than a pentium 4 3.2 Ghz for memory intensive audio operations because of the 64 bit memory manager (handled at hardware level), double wide data path, on-chip northbridge, and some other factors.

      In layman speak, I can do around 60 audio streams on a PIV 3.2 Ghz. On my athlon 64 2.0 Ghz I have projects with 135. 24 bit, 48k.

      Sometimes one architecture can have a lower clock rate and be faster, especially if it can do double the work (or in my case, move double the data) per tick.

      Speed evaluation depends on taking the job you are doing, the clock rate, system bandwidth, actual work being done etc into consideration. Clock speed, while important, is only one of many factors.

    7. Re:Leave Moore's law out of this, please by Raul654 · · Score: 1

      Right, but did you actually read my comment? I said "semi-conductor capacity", not frequency. Off the top of my head, the number of transistors on your processor is a function of: the bus widths, the ISA, the branch prediction, the pipeline length, the amount of cache, the number of cores/ALUs/FPUs/thread units. Hell, in the future, even the voltage level will play a role (future processors will be razorized and run at a lower power level). All of the factors you named play into the capacity. So what I said is true - semi-condutor capacity is roughly proportional to speed.

      --


      To make laws that man cannot, and will not obey, serves to bring all law into contempt.
      --E.C. Stanton
    8. Re:Leave Moore's law out of this, please by gstoddart · · Score: 1
      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.


      Moore's law has little to do with anything. It's just an observation, with a bunch of corrolories which have upheld remarkably well.

      Really all it means is that roughly every 18 months the capacity roughly doubles which is roughly related to speed which meant that the speed seemed to roughly increase on some trend since the capacity went up in the first place.

      It's not like we've violated some universal constant or anything. A thirty-year old observation is suddenly not behaving linearly. Film at 11.

      --
      Lost at C:>. Found at C.
  28. Adding Ghz is probably not the best solution by 99BottlesOfBeerInMyF · · Score: 3, Interesting

    Ramping up clock speeds is hitting some serious limitations as far as increasing the work done by a machine is concerned. There are lots of ways to get work done faster. They are just harder to market without some good, popular, and independent benchmarking standards. At some point engine manufacturers realized that increasing the cubic centimeters of displacement in an engine was not the best way to make it faster or more powerful. Now most car reviews include horsepower. Clock speed is analogous to CCs.

    1. Re:Adding Ghz is probably not the best solution by rk87 · · Score: 1

      We need a new platform, period. And I don't mean AMD64 and all those 64 bit platforms that are all popular right now. 64 bit processing power is simply not needed and slows things down, as the article mentions, due to memory stuffs. 32 bit integers and pointers are perfectly alright. Current Intel processors are as bloated as Windows Longhorn 2 + SP 3 is gonna be. I, and others, have been saying to just calm down, strip the CPU, and come out with much smaller dies. RISC is a great technology, but few RISC vendors are doing it right.


      I quote http://www-106.ibm.com/developerworks/library/pa-m icrohist.html?ca=dgr-lnxw01MicroHistory:


      In 1992, DEC introduced the Alpha 21064 at a speed of 200MHz. The superscalar, superpipelined 64-bit processor design was pure RISC, but it outperformed the other chips and was referred to by DEC as the world's fastest processor. (When the Pentium was launched the next spring, it only ran at 66MHz.) The Alpha too was intended to be used in both UNIX server/workstations as well as desktop variants.

      The primary contribution of the Alpha design to microprocessor history was not in its architecture -- that was pure RISC. The Alpha's performance was due to excellent implementation. The microchip design process is dominated by automated logic synthesis flows. To deal with the extremely complex VAX architecture, Digital designers applied human, individually crafted attention to circuit design. When this was applied to a simple, clean architecture like the RISC-based Alpha, the combination gleaned the highest possible performance. Sadly, the very thing that led Alpha down the primrose path -- hand-tuned circuits -- would prove to be its undoing. As DEC was going out of business, , its chip division, Digital Semiconductor, was sold to Intel as part of a legal settlement. Intel used the StrongARM (a joint project of DEC and ARM) to replace its i860 and i960 line of RISC processors.

      Why not do that again? Intel and AMD have plenty of money to afford this effort. With a very good, simplistic design, plenty of registers, lots of cache, small die size, this would become a beautiful and fast chip. It might even drive the chip speeds up with the hand-tuning to Intel's dreaded 4Ghz. (Note: AlienWare has been selling 4Ghz AMD computers for a while now).

      --
      I'M NOT ANGRY!
    2. Re:Adding Ghz is probably not the best solution by deacon · · Score: 1
      At some point engine manufacturers realized that increasing the cubic centimeters of displacement in an engine was not the best way to make it faster or more powerful. Now most car reviews include horsepower. Clock speed is analogous to CCs.

      If by "at some point" you mean after about (waves hands) 1935, you are incorrect.

      The big development was the discovery that overlapping the camshaft lift duration for the intake and exhaust valves would improve power dramatically. After that, there was no substitute for cubic inches, unless you were willing to increase the engine RPM. (Horsepower=Torque * RPM)

      Since the internal stresses in the engine rise as the square of the RPM, that created problems with engine lifespans.

      Horsepower was a big selling feature in the 50s and 60s and early 70s, and it was heavily advertised.

      From my 1975 Motor databook, in 1970 Chevrolet made a 454 cubic inch (7.44 litre) V8 advertised at 460 HP (343KW) @5600 RPM. 11.25:1 compression ratio, bore of 4.251 inch, stroke 4 inch.

      The push to smaller engine displacements was only due to Federal mileage standards, and the concern with gas prices and fuel economy around 1975.

      Then we were screwed with the horrible,horrible cars in the 1980s, performance was out, plush velour interiours were in, and the speedometers used to have the "55" in big orange digits to remind you that your life was over and fun was forbidden....

      Sorry, I just had a flashback there and kind of freaked out. 8^(

      Anyway, in a feeble attempt to keep on topic, engine displacement is not a good analogy for chip clock frequency.

    3. Re:Adding Ghz is probably not the best solution by 99BottlesOfBeerInMyF · · Score: 1

      If by "at some point" you mean after about (waves hands) 1935, you are incorrect...Anyway, in a feeble attempt to keep on topic, engine displacement is not a good analogy for chip clock frequency.

      You are obviously not a motorcycle or snowmobile enthusiast. Think mid 90s. Think advertised still in some places. Many smaller, sport and recreation vehicles recently or still reference CCs, and use it as a selling point, just like clock speed. In most cases horsepower, acceleration, and top speed are really what consumers are interested in, but most consumers want one simple number for their simple minds. See any analogies with the computer industry yet? You can have machines with a large displacement that top out at lower speeds, and accelerate more slowly than machines with lesser displacement. This is very analogous to how some chips can perform more work, in less time while running at a lower clock speed. I think it a very apt analogy.

      P.S. nice flashback, plush velour, crappy horsepower, orange 55, that was my brother's Oldsmobile all right.

  29. Software by BrianHursey · · Score: 1

    Normal user software will get no improvement of cpu speed like this.. They day to day computer user would seek not benefit of something this fast.

    --
    Linux is like a teepee. It has no windows, no gates, and there's an Apache inside.
  30. Get over it by Mirk · · Score: 2, Insightful

    If, as the Dr. Dobbs article says, "the free lunch is over", then the only sensible thing to do is make do with what we have now. For goshssakes, people, the computers we have now are already insanely over-powered. How many more gigahertz do we need my life already?

    --

    --
    What short sigs we have -
    One hundred and twenty chars!
    Too short for haiku.
    1. Re:Get over it by fishbowl · · Score: 1

      "the computers we have now are already insanely over-powered."

      That depends on your application. Are you doing word processing or low latency general purpose signal processing?

      --
      -fb Everything not expressly forbidden is now mandatory.
    2. Re:Get over it by Anonymous Coward · · Score: 0

      "Nobody will ever need more than 640K"

      - Bill Gates

    3. Re:Get over it by IncarnadineConor · · Score: 1

      Good christ man, some of us are trying to solve chess.

    4. Re:Get over it by julesh · · Score: 1

      Good christ man, some of us are trying to solve chess.

      According to my calculations on this subject (which are admittedly a few years out of date) you're going to run out of memory quite quickly. I wouldn't worry about your CPU speed too much.

    5. Re:Get over it by Wordsmith · · Score: 3, Insightful

      Computers won't be fast enough until they can do anything we'd want of them near instantly. If I have to wait for feedback, it's not fast enough.

      My Athlon64 3200, which isn't top-of-the-line but it's pretty close, still takes quite a bit of time to convert a DVD to divx. It takes a few minutes (because IO needs to get faster) to copy large volumes of files. Photoshop filters on huge, detailed files can take a few minutes to run. Machines only slightly slower choke on playback of HDTV. I can't imagine how long it takes to encode.

      When I can do all those things instantly, do accurate global weather predictions in realtime and have my true-to-life recreation of the voyager doctor realize his sentience, THEN computers will be fast enough. Until the next killer app comes, of course.

    6. Re:Get over it by phasm42 · · Score: 1
      --
      "No one likes working in a hamster wheel, and your shop smells of cedar shavings from here." - TaleSpinner
    7. Re:Get over it by Billly+Gates · · Score: 1

      "How many more gigahertz do we need my life already?"

      Run 3d studioMAX and Gentoo?

      Nothing is powerfull enough and everything is way too slow.

    8. Re:Get over it by IncarnadineConor · · Score: 1

      Out of curiosity, have you ever seen a good analysis of how many legal positions there are in chess? I don't trust my grasp of combinatorics well enough to fell like I can come up with a good upwards bound, and I would be interested in knowing just how many legal positions there are.

    9. Re:Get over it by tuffy · · Score: 1
      How many more gigahertz do we need my life already?

      After seeing my 2Ghz Athlon64 take 15 hours to convert my FLAC collection to mp3 for portable use, I think we need more Ghz, more parallelism or both. Having too much CPU speed is never a big deal, but not having enough can be a real pain sometimes.

      --

      Ita erat quando hic adveni.

    10. Re:Get over it by k4_pacific · · Score: 1

      " Computers won't be fast enough until they can do anything we'd want of them near instantly"

      I fired up my old 386 with Windows for Workgroups the other day, and it's responsiveness was near instantaneous. My current work PC, a 1.8 Ghz P4 running W2K has noticable latency. The problem is not inadequate hardware, it is software bloat oupacing hardware improvements.

      --
      Unknown host pong.
    11. Re:Get over it by Anonymous Coward · · Score: 0

      "Nobody will ever need more than 640K" - Bill Gates

      Apocryphal and almost certainly false; the 640K limit wasn't MS's choice. If you wish to disagree, please cite the original source of the quote.

    12. Re:Get over it by Dogtanian · · Score: 1

      For goshssakes, people, the computers we have now are already insanely over-powered. How many more gigahertz do we need my life already?

      Amen; I've been thinking for a few years now that it might be interesting, and *possibly* beneficial, to stop all processor development, and see how much more speed we could get out of our x MHz CPUs. I suspect that if CPU development stopped tommorow, optimisation would improve vastly, and promote many interesting new developments in computer science.

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    13. Re:Get over it by julesh · · Score: 1

      This is all from memory. I spent quite a while researching this all about ten years ago in order to solve an argument about whether a solution to chess was possible or not.

      The number is extremely high (I've lost my references to how high, but it was rather ridiculous) if you include the 'position repeated 3 times causes a draw' move, which means that positions where all the pieces are in the same place on the board can actually be one of many different positions, depending on how it was reached.

      If you play without this rule, the history you need to keep is very limited (basically, whether each side has moved king or either rook, and which player is next to play), so the number of positions is substantially reduced.

      As a good first estimate, there are about 65!/33! ways of placing the pieces on the board (including the option of not placing them on the board; the actual answer is slightly more complex than this, but this is close enough for a first estimate). Multiply by two to consider whose turn it is. This is about 10^67. The actual number of possible positions will be less than this.

      I believe the number of positions of major pieces alone (discarding the pawn positions, which are harder to calculate the legality of) is in the order of 10^25. Some of these will be legal in one player's turn, but not the other, so including the turn in the information stored doesn't quite double the figure. There number of legal pawn positions is probably a few orders of magnitude smaller, but some of the piece positions are obviously not legal with some of the pawn positions, so we can't just multiply these figures together.

      Given these restrictions, a top-of-the-head guess is about 10^40 different legal positions.

      Having just googled for other sources, it seems I'm pretty close. Mathematical papers on the subject have given various values between 10^40 (Beeler et al) and 10^43 (Shannon), but with a few venturing as high as 10^120 (which probably includes relevant game history, not just position on board, by the sounds of it).

      Here's a reference.

    14. Re:Get over it by Wordsmith · · Score: 1

      And just try to do some serious multimedia work or real hefty multitasking on the old 386, with windows for workgroups. Have all the fonts in your 16 million color display antialiased, and play 3d games at a decent speed.

      I'm not saying bloat and cruft aren't serious issues, but we ask our computers to do much more now than we did when the 386 was still the bees knees. There are reasons why a modern *nix gui, OS X and Windows XP run more slowly than WFWG -- they do a hell of a lot more.

    15. Re:Get over it by evilviper · · Score: 1
      still takes quite a bit of time to convert a DVD to divx.

      Although you were quite vague, I'll still say what I've said before... If you were using an encoder based on libavcodec, encoding would be FAR faster. My 1.66Ghz can now do about realtime encoding (thanks primarily to mencoder's "turbo" option for two-pass encoding). The point merely being SOFTWARE is really what's holding you back, not usually hardware.

      Machines only slightly slower choke on playback of HDTV. I can't imagine how long it takes to encode.
      It's actually the displaying of the decompressed video on the screen that takes up most of the CPU time. So, encoding doesn't take as long as you would think.

      To be specific, I can encode 1440x1080 material at just about 1/2 the speed of 720x480 material. And my own system can't playback 1080 videos (smoothly) on the CPU...

      Incidentally, even dirt-cheap videocards can do MPEG-1/2 playback at HDTV resolutions on extremely low-end computers, so powerful systems aren't needed for HDTV playback.

      do accurate global weather predictions in realtime and have my true-to-life recreation of the voyager doctor realize his sentience, THEN computers will be fast enough.

      You are assuming those things are possible in the first place, at any speed. Perhaps they are not.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  31. Clock speed isn't everything. by bchernicoff · · Score: 2, Insightful

    The difference between Intel and AMD's cpu architecture yields similar performance but at very different clock speeds(AMD's 3200+ runs at 2.2GHz). Other aspects of PC performance continue to improve, so as long as the trend is towards greater overall system performance, clock speed matters less. And greater parallelism is a good way to achieve this.

  32. free ride may not be over by willCode4Beer.com · · Score: 1

    After reading the previous article about the laser on a chip. I think that we will continue to see sped increases.
    Everytime we come upon the "maximum" capabilities, some smart guys and gals figure out a way to get beyond it.
    I've been hearing for 10 years that computers can't possibly get much faster. Memory can't possibly get any smaller.

    I say "bah!" to the nay sayers. People will always find a way. A guaranteed way to be labeled an idiot in history is to claim something is impossible.
    Wasn't there some british lord in the 30's who publically claimed that it was impossible to fly?
    Wasn't the maximum possible speed to travel 100mph?
    then the speed of sound was impossible to overcome.
    then, you can only get to space with billions and billions of dollars.
    or, a computer to do "that" would be the size on the empire state building and require all the power of niagra falls just to keep it cool.

    The impossible is for weenies.

    --
    ----- If communism is a system where the government owns business, what do you call a system where business owns govern
    1. Re:free ride may not be over by Anonymous Coward · · Score: 0

      A guaranteed way to be labeled an idiot in history is to claim something is impossible.

      Wasn't there some british lord in the 30's who publically claimed that it was impossible to fly?


      An even better way to be called an idiot is to claim that something that is ubiquitous is impossible. Myself, I think typing is impossible.

  33. As stated in TFA by youngerpants · · Score: 1

    Moores Law is an exponential law; it just cant go on doubling exponentially, there has to be a ceiling at which the technology being used reaches its peak.

    Think of it like accelerating your car. 2mph, 4mph, 8mph, 16mph, 32mph... you are increasing your speed exponentially, but even that 5.7 V10 is going to max out at some point. IANAM, but I'm sure there is a name for this.

    Also from TFA, this hasn't happened yet, chip designers are just being more intelligent about how they boost speed (not just cycles, but cache, multi-threading etc).

    However, I'm sure that within the next few years silicon will have given us all it can... long live grid computing

  34. It's at the store right now by sprior · · Score: 0

    Go pick it up in your flying car.

  35. Abstract it away... by Lodragandraoidh · · Score: 2, Interesting
    What gives?


    You, sir, are an idiot. :p

    Seriously though, the article recommends building applications concurrently. Short-term this may be the case on a small scale (and really already is the case).

    The fundamental paradigm shift that will occur will be when we build our operating systems to handle concurrency for us; the advent of 4GLs will help move this forward.

    In this model, you would program normally, not worrying about concurrency at all. The OS would do all the dirty work of breaking up your application into pieces that can run concurrently for you. Are we there yet? No. Will we be there? Yes - particularly if you want to keep productivity at high levels. You will have to abstract concurrency from the day to day programmer for this to happen.
    --

    Lodragan Draoidh
    The more you explain it, the more I don't understand it. - Mark Twain
    1. Re:Abstract it away... by arkanes · · Score: 2, Interesting
      The OS would do all the dirty work of breaking up your application into pieces that can run concurrently for you.

      In a word, no. At least not with current languages. There's a reason we don't do this already, after all. Provably correct concurrency is very hard to generate, and almost impossible with pure machine code - you either end up with deadlocks and race conditions or very poor performance because you serialize too much stuff. Or incorrect results because data is transparently copied instead of shared. Etc. There do exist languages designed to accomodate and encourage both implicit and explicit concurrency, like Erlang, and I think we'll see more of them in the future, but it's not going to happen by simply ignoring it.

    2. Re:Abstract it away... by Lodragandraoidh · · Score: 1

      Grid computing (or a Beowulf cluster; I had to throw that in) also offers some options for leveraging concurrency, and much of the work done to make these systems work could be leveraged within the operating system to do similar things on multi-cpu machines.

      I agree - its not there now. I am not so sure an example of the solution won't be here in short order - considering the brick wall that many companies (particularly computer game companies, who are always pushing the edge of the envelope) will be hitting.

      Saying it won't happen, is as bad, or worse than saying it will happen on January 7th at 2200 GMT...

      --

      Lodragan Draoidh
      The more you explain it, the more I don't understand it. - Mark Twain
  36. Dual prossesors... by sirgallihad · · Score: 1

    It's really interesting that dual prossesors haven't caught on in mainstream computing. This isn't to say that there are mobos out there that are avalable to the public that support two or more prossesors, but it's really a niche market, people who generally understand computers looking for a super-fast new computer at a certain point have to start looking at dual prossesor solutions. Not to mention that those consumers(let's call them geeks), when they have their dual prossesor system, there are very fiew apps that actually take advantage of the dual prossesor capabilities(photoshop, final cut, etc). The rest of them just end up being run on seperate prossesors, which is still faster, if ALL apps where made for both single and dual prossesors, then Joe Gamer and the Geek and eventually Fred Email will want a dual prossesor computer, because the two prossesors can act as one(as I said, if the apps are coded right), therefore making faster systems.

    1. Re:Dual prossesors... by Dano+Watt · · Score: 1

      You realize that most people are on a budget, right?

    2. Re:Dual prossesors... by drspliff · · Score: 1

      Thats probably because Uncle Bob or Aunty Mary will go for the cheapest on the market.. It's not as if they need dual CPU machines to do performance hungry spreadsheet authoring or whatever the latest sales motives are

      Mind you, knowing that Microsoft® are known to drive a lot of the hardware upgrade with newer versions of Windows®, when we see Longhorn® coming out it'll probably need a multiprocessor machine - One for Windows and one for your programs!

    3. Re:Dual prossesors... by Damhna · · Score: 1

      "This isn't to say that there are mobos out there that are avalable to the public"

      There may be MB support available but the fact is that multiproc computing is still far from being able to accomplish true multitasking with the current architectures. I believe that once we can have proper multitasking architechtures multi proc'd systems will really come into their own at the user level.

      Have a look at Intel's =http://or1cedar.intel.com/media/training/intro_ht _dt_v1/tutorial/index.htmHyperthreading[/URL] ] for example . Pay attention to the section on Dual Proc'd Workstations. This is not multitasking , it's simply advanced thread scheduling.

  37. need for speed? by ekeup1 · · Score: 2, Interesting

    For >95% of users, I see no need to have computers faster than 2Ghz. Maybe I'm getting old... oh, and music these kids listen to....

    1. Re:need for speed? by bairy · · Score: 1

      And those who are power hungry will rig up their PCs so they can overclock them to the max anyway, remember the 5ghz clocker?

      --


      Get paid to search..It's geniune and
    2. Re:need for speed? by ponos · · Score: 1
      For >95% of users, I see no need to have computers faster than 2Ghz. Maybe I'm getting old... oh, and music these kids listen to...

      Well, maybe I'm getting old, too. I remember a few years ago when I was reading a review in a magazine, a phrase stuck and I never forgot it: "The pentium 120 is a massive overkill for the vast majority of users" Today most users think that a 1GHz CPU is not good enough for word processing.

      Anyway, just to be a little on topic, I'd like to say that BY FAR the most stable part of our computers is RAM. I have had 2x512GB PC2700 CL2 for roughly 2 years and it costs the same (I had bought it 180 Euros then). Plus, noone buys more than that. I was always a very aggressive memory buyer and even today you will have to pay a huge load of money for 1GB dimms. (and you cannot get PC3200 CL2 1GB dimms, as far as I know)

      P.

    3. Re:need for speed? by grumbel · · Score: 3, Insightful

      ### For >95% of users, I see no need to have computers faster than 2Ghz.

      As long as there are games and a large number of computer users who want to play them, there will be a need for faster CPUs. While on the graphic side the main work is already done by the GPU, the physics and AI are still done by the CPU. And oposed to the graphics, where games are already quite advanced, AI and physics tends still to be rather primitive in games and will for sure need a lot of additional CPU.

    4. Re:need for speed? by krenn · · Score: 1

      Umm thats a sucker bet friend. Remember the
      president of IBM (Watson?) who thought there'd be no need for more than a handful of computers? Remember Ken Olsen (founder of DEC) who wondered who'd want a personal computer? Remember Bill Gates who wondered why you'd need more than 640K (that one may be apocryphal)? We programmers are masters at wasting CPU cycles :-). Adding to an old saw, you can never be too rich, too thin, or have too fast a processor.

    5. Re:need for speed? by Anonymous Coward · · Score: 0

      Well, to just say AI and physics downlplays the CPU's work. AI, physics, sound processing (the soundcard doesnt do it all), networking, input processing, and feeding the GPU. And probably a dozen other things. All of those need some serious improvements. 3D sound has come a long way though.

    6. Re:need for speed? by funaho · · Score: 1

      Trying to run an all-software PVR (like MythTV) at HDTV resolution definitely requires more than 2 GHz. I'm considering upgrading exactly for this reason.
      This doesn't affect many users right now but it certainly will in the coming years, especially when the mandatory shutdown of the NTSC signals happens and HDTV becomes the norm instead of the exception.

    7. Re:need for speed? by affliction · · Score: 0

      How intensive is the physics in a game like Half-Life 2. My machine bogs significantly when, say, a dozen barrels explode at once. Would it make sense to offload your physics and maybe AI onto it's own piece of silicon? Maybe just another small chip on a video card?

    8. Re:need for speed? by Anonymous Coward · · Score: 0

      A little more than 15 years ago nobody saw the need to have computers faster than 8Mhz.

    9. Re:need for speed? by shish · · Score: 1

      With the exception of the latest games, my 200MHz desktop is still doing all I need quite happily...

      --
      I mod down anyone who says "I will be modded down for this", regardless of the rest of their comment
  38. bring on the diamond wafers by AviLazar · · Score: 2, Informative

    When they get off the silicon and hop onto those nice diamond wafers (there is an article in wired), then we will see faster processing.

    The main problem - our largest producer (Intel) said they would not stop utilizing silicon until they made more money from it...We know that the industry likes to stagger upgrades. Instead of giving us the latest and greatest - they give us everything in between in nice "slow" steps so we spend more money. Personally, I wouldn't mind seeing the jumps of 1ghz at a time. This year 2.0 ghz, next year 3.0, following year 4.0, etc...and then eventually increase it further so its 5ghz at a time, etc. et al.

    --

    I mod down so you can mod up. Your welcome.
    1. Re:bring on the diamond wafers by rnd() · · Score: 1

      The industry does not conspire to give us slow chips. It just simply does not make business sense for AMD or Intel or IBM or any of the others to spend the required R&D dollars unless there is going to be a return on those dollars in the form of a couple of years of CPU sales.

      Suppose you could start a microprossor company that could release chips on the schedule you mention. The question to ask is, how much money would they need to charge for those chips to pay for the continued R&D needed to make the next generation?

      The reason we have the current status quo is because people are not willing to pay enough for the bleeding edge to justify more frequent product releases.

      Sure, some small percentage of microprocessor purchasers would benefit from being able to pay a lot of money for faster improvement, but there aren't enough of them to make it a good business proposition for Intel. Think about it, if there were a 10GHZ chip available right now, how many computing clusters would not have been built becuase well, the 10GHZ chip was fast enough to not require a clustering solution ... ?

      In reality, most computing clusters are built using not the latest bleeding edge processors but using dual proc configurations of 6 month old technology. Why, because the incremental difference for most parallelizable problems won't be significant enough to justify the cost of using 100 10GHZ machines instead of simply using 25 dual proc 2GHZ machines.

      What remains is a small niche: hard to parallelize cluster computation (which is really why people buy Cray's etc) and high end workstations. Still, for many workstation tasks, increasing L2 cache, speeding up RAM, etc., have made sufficient improvements to keep customers unwilling to drop multi-thousands of dollars for something like a 10GHZ processor.

      --

      Amazing magic tricks

    2. Re:bring on the diamond wafers by AviLazar · · Score: 1

      I know Intels reasons for doing it (I thought I said it) - so isn't that conspiring if they are staggering their chips for a purpose other then the inability to make something better?

      They have already had years and years of silicon; how many millions did silicon cost that it could not have been recouped by now ten-fold or more?

      Think of it this way - back in the early-mid 90's we would see upgrades going from 33 mhtz, to 66, etc. Small increments (by todays standards) now we see increments going up by 200-500 mhtz at a time. THat is what I am implying. When are going to stop from going to 200-500 mhtz increments to 1 ghtz?

      Also, I think as fast as we make our computers, someone will be able to make a nice bloated software to tax it. Isn't the software industry essentially waiting for the hardware industry to make faster components so they can make more demanding programs?

      The reason why most enterprises uses second or third generation technology as opposed to first gen is not the price (whats an extra 10-20 grand for a multi-million/billion dollar company?). It is the support, and technical problems. The company I work for will not utlize a new program until revision 1 comes out (for the most part) and it will not use the latest generation in hardware just in case there are serious flaws. We typically wait until it becomes second gen, because then most of the bugs have been worked out and if we call tech support we are less likely to get "well we have never heard of this problem before, thanks for reporting it"

      --

      I mod down so you can mod up. Your welcome.
    3. Re:bring on the diamond wafers by Anonymous Coward · · Score: 0

      Bullshit. There's currently no way of doing both types of C-semiconductors. To be useful, you need p and n semiconducturs, only one of them is possible with diamond. Superconductors are a better bet.

  39. Actually this is sort of like competition by melted · · Score: 2, Interesting

    When there's no free ride, programmers will have to compete with each other on who can squeeze that last bit of performance out of existing hardware. So you can kinda sorta predict the revival of the performance-conscious programming.

    1. Re:Actually this is sort of like competition by British · · Score: 1

      You are correct. Hardware has done it's part to speed things up, now it's software's turn to speed up. We need more Future Crew-like developers in the world. :)

    2. Re:Actually this is sort of like competition by octal666 · · Score: 1

      Yes, and at last we could forget OO-programming and return to C and ASM!

      --
      DON'T PANIC
    3. Re:Actually this is sort of like competition by I8TheWorm · · Score: 1

      That's why everyone should code in Visual Basic. Because RAD stands for Rapid Application Dynamics!

      For those who couldn't tell... </funny>.

      --
      Saying Android is a family of phones is akin to saying Linux is a family of PCs.
  40. 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.

    1. Re:Two birds, one stone by xXunderdogXx · · Score: 1

      Whenever I view a page without having the right language pack installed (see parent) I always get the feeling the authors are incredibly confused and impatient to the point of panicking. Anyone else get that?

    2. Re:Two birds, one stone by sharkey · · Score: 1

      What language pack do you think Slashdot requires, anyway?

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
    3. Re:Two birds, one stone by WMD_88 · · Score: 1

      Yeah, I do! It's hilarious. It's like a page I was at yesterday: IBM PC???????

    4. Re:Two birds, one stone by dickrichardv8 · · Score: 1

      In Mozilla, go to Tools, then to translate page and click once to get English. It's not really hard to do. If you are running IE, then I don't really don't know how to help.

  41. 10ghz. Huh??! by Anonymous Coward · · Score: 1, Informative

    Raw speed isn't measured in Megahertz anymore. Actually, it never really depended on MHZ, it was always MFLOPS. For years, and finally getting due recognition, AMD has destroyed Intel despite having a slower mhz core. MFLOPS was and is the key.

    Brooklyn.

  42. where is it? by Fr05t · · Score: 2, Funny

    "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"

    Santa was unable to deliver your 10Ghz system this year for the following reasons:

    1) Santa's Flying Car has not arrived

    2) Santa could not use his sleigh because it failed the new FCC saftey requirements for subobital ships (something about flaming reindeer poo falling from the sky).

    3) The OS for the new 10Ghz computer is Duke Nukem Forever which isn't currently available - maybe next year or decade.

  43. Been coding for the future architectures for years by Anonymous Coward · · Score: 0

    My code won't perform adequately until processors have 1GB L2 cache.

  44. Yeah by Aggrazel · · Score: 2, Funny

    And for that matter, where's my Mr. Fusion, Hovercar conversion, Jaws 17 and perfected weather service? Aren't those supposed to be done by 2015?

    1. Re:Yeah by HexaByte · · Score: 1

      Unless I've been asleap for 10 years, it's only 2005, so they've still got ten years to please you!

      --
      HexaByte - he's a square and a half!
  45. Defect rate by grahamsz · · Score: 1

    All semiconductor manufacture processes have defects, and when a defect occurs it ruins the chip.

    Typically defects occur at random so there will be X defects per cm^2 (in this case X should be 1).

    So the bigger you make the individual chip dies, the more likely the case that there will be a defect in one of them. Hence larger chips have far lower yield than smaller chips.

    This is the main reason that very few digital cameras have sensors the size of 35mm film... since you'll probably end up with a yeild of less than 0.5.

  46. Your 10ghz is waiting.. by nurb432 · · Score: 2, Funny

    Just click here.. and send me your CC number, name and billing address ill get it shipped right out to you.

    Free shipping if you act in 24hours..

    But wait.. theres more..

    --
    ---- Booth was a patriot ----
    1. Re:Your 10ghz is waiting.. by SoTuA · · Score: 1
      Just click here..

      Where? WHERE?!?!? You forgot the link, YOU INSENSITIVE CLOOOOOOOOOOOOOOOOOOOOOOOOOOOooooooooooooooooooooo ooooooooooooooooooooooo.....................

  47. are you serious? by willCode4Beer.com · · Score: 1

    Why should a car have more than a 50hp motor ?
    Why put more than a 25hp motor in a motorcycle ?
    Why should anybody want to get a plasma flatscreen TV?
    Hell, what good is color TV?

    --
    ----- If communism is a system where the government owns business, what do you call a system where business owns govern
    1. Re:are you serious? by Anonymous Coward · · Score: 0

      There's always someone who doesn't read the real question, but makes a guess as to what's being asked and replies to that question they made up in their own head. Go back to school and re-do comprehension.

  48. ARGH DIE by Anonymous Coward · · Score: 0

    Man, I'm just gonna redirect tinyurl.com to localhost, fuck this troll shit.

  49. Moore's Law is dead by johnjay · · Score: 1

    Long live Moore's Law

    (Since I don't know any better, I'm going to keep betting on Moore's Law and the inexorable genius of the hardware engineers.)

  50. Does that mean... by Anonymous Coward · · Score: 0

    Does that mean that I have to learn how to code properly?

  51. Moore's Law isn't Speed Doubling, it's Transistors by unfortunateson · · Score: 3, Insightful

    The fallacy here is that the clock speed has to keep doubling. Moore's law says that the number of transistors on a chip doubles each 18 month period, and we're still pretty close to that.

    Intel has just caved on the speed doubling in particular, by knocking the clock speed off their product designations, mainly because the Pentium M chips were running significantly faster than the same-speed P4's. AMD's Athlons have been 'fudging' their numbers by having the product number match not their clock speed, but that of the roughly equivalent P4 chip.

    Meanwhile, cache sizes are up, instruction pipes are up, hyperthreading has been here a while, multi-core chips are coming down the pike... we're still getting speed gains, just not in raw clocks.

    At the same time, the Amiga philosphy of offloading to other processors is truth, with more transistors on the high-end graphics processors than there are on the CPUs!

    I hate to say it, but what do you think you need 10GHz for anyway? Unless you've got a REALLY fat pipe, there's a limit on how much pr0n you can process ;^)

    The high-end machines do make good foot-warmers in cold climes.

    --
    Design for Use, not Construction!
  52. Double channels = twice the transistors? by jfonseca · · Score: 1

    Double channels have to have twice the transistors, right? If that's true then Moore's law lives on. Think of it as quad-processor machine in one cpu case....that's 4 times as many transistors as 1 CPU. Or am I missing something here?

    --
    Broken Hearts are for Assholes. - Frank Zappa
  53. BUT (Re:And that is why...) by Anonymous Coward · · Score: 0

    Slashdot can't imitate Hunter S. Thompson. He can actually write!

  54. Limit is about marketing and ROI, not engineering by count0 · · Score: 1

    I fully agree that we *could* see significant speed increases. However, the benefit for AMD and Intel in boosting speeds just isn't there - Intel delayed their 4Ghz offering not because they couldn't bin some chips into a 4ghz bucket, but because the return for hitting higher clock speeds just isn't there - there's not enough of a market, they need to get the return out of existing investments before moving on, and there are few applications that demand that kind of horsepower.

  55. 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.

    1. Re:GaAs and Relational Calculus by Dr.+Cody · · Score: 1

      (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.")

      That has to be the worst Bond villain name I have ever heard.

    2. Re:GaAs and Relational Calculus by Anonymous Coward · · Score: 0
      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.
      Bwah? I think it's entirely possible that there's not a single true fact in this entire paragraph. How'd you get modded +3:Interesting? Lessee... the notion that government grants for supercomputers started in 1985 with the CM1; the idea that DARPA's investment harmed the industry -- uh, I think RATHER NOT; the idea that Cray actually had GaAs viable; and best of all, the idea that GaAs was cheap to manufacture. Let's see, tallying up: yep, 100% BS. Nice job, even on Slashdot.
      Whenever the government "picks winners" rather than letting nature pick winners, the technologists and therefore technology loses.
      Since when are supercomputers commodities? Quite the opposite: the industry has massive networking costs, huge initialization costs, very few customers, and exceptionally strong constraints. This is exactly where government grants prove superior to the market.

      Oh, I'm sorry, my bad. I forgot you're one of those religious nuts who think that the market is always good and the government is always bad because you've never taken economics 101. Tell me again, grandpa, about how the internet was created entirely without government funding or direction.

    3. Re:GaAs and Relational Calculus by cloudturtle · · Score: 1

      Actually, AFAIK, the complaint about not using the GaAs technology (by Finkelstein, in addition to his deadness) is unwarranted.

      Now it is true that GaAs were superior to silicon at one time. Way superior. They were able to hit a GHz way back in the day. I don't think their density was as high, but their speed was insane. Now it is only fair to mention that their only use (AFAIR) was in vector computers. [now this is something i don't entierly understand. Maybe it was becuase all early Crays (Cray 1 & 2, ect.) were vector, but this tech never seemed to make its way in to standard processors.]

      The thing though, was that around the time silicon started making its way to 1GHz, GaAs became obsolete. They were more expensive to make, had a lower density, and a much more limited purpose. Now, even Cray uses silicon to manufacture their vector processors.

      So, i find it difficult to blame some dead dude for not utilizing an old technology that has little purpose today. At one time GaAs was a cool tech, not silicon has surpassed the hell out of it, at least in computers.

    4. Re:GaAs and Relational Calculus by Baldrson · · Score: 1
      Lessee... the notion that government grants for supercomputers started in 1985 with the CM1;

      No, but the trend away from government as lead customer to lead investor started around that time.

      That trend appears to be reversing finally with the long and sordid series of failures of government investments.

      Tell me again, grandpa, about how the internet was created entirely without government funding or direction.

      Well, anonymous coward whipper-snapper, look at the history of Ethernet and compare MAC addressing with IP addressing for a good example of the "benefit" of government direction of networking standards. We had MAC addresses around the same time we had IP addresses (maybe a little before) and the braniacs within the govt agencies decided to drive that brain-dead standard into all networking, including local area networking, while MAC addresses would have been superior.

      Now, 3 DECADES later we're seeing IPv6 attempting to reinstitute MAC addresses but there is so much brain damage done by government picking winners we will probably see China go IPv6 before the US -- where MAC addresses were first developed.

    5. Re:GaAs and Relational Calculus by poot_rootbeer · · Score: 1

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

      But isn't the government part of the "nature" system that you believe should pick winners?

      It's not like they passed a law outlawing the development of alternate technologies. They just assumed the role of a large technology customer, and invested in the "winner" they had picked. Not unlike any other company that invests in technology.

    6. Re:GaAs and Relational Calculus by Alomex · · Score: 1

      Danny Hillis' "Connection Machine"

      Ah, another crock idea with-cool-sounding-name from the MIT Media Lab. No wonder half of the lab wants to walk away and change their name.

    7. Re:GaAs and Relational Calculus by Anonymous Coward · · Score: 0
      Well, anonymous coward whipper-snapper, look at the history of Ethernet and compare MAC addressing with IP addressing for a good example of the "benefit" of government direction of networking standards. We had MAC addresses around the same time we had IP addresses (maybe a little before) and the braniacs within the govt agencies decided to drive that brain-dead standard into all networking, including local area networking, while MAC addresses would have been superior.
      Yeah, 20-20 hindsight's a bitch isn't it? But it's all fine and dandy to point out nitpicks in standards turn away from the mote in one's eye: where's that industry-driven 1980's Internet thing? I didn't see one. Did you? I looked under the couch.

      Y'see, there wasn't one. And how about that industry-driven race to the moon in the '60s? Pretty impressive seeing Morton Thiokol doing that all by itself.

      You can point to errors in governmental direction all you want, but the fact remains that for some projects, if you just have the market, nothing would ever get done, because it's not in the self-interest of a firm to do it. Infrastructure is the classic high-entry-level, high-networking industry. And such things work very badly with the market. They're not commodities.

      Supercomputing is exactly this kind of industry. Very expensive to start up research, very few outlets for purchase of goods, high networking, very large constraints on how you're able to sell goods. This is a worst-case scenario for the market. As a result they were very dependent on government grants, either to them or to universities specifically to buy a supercomputer, in order to drive the industry. And frankly still are. Were it not for government technology grants, Cray wouldn't even exist as a corporation. Because the market just wouldn't sustain supercomputer companies. Certainly the occasional contract with NSA and DOE wasn't sufficient. It's a technology we all benefit from now because of those evil government villains who had the forsight to realize how important the technology was then.

      Sorry to shake your faith in the All Encompassing Power of the Market.

  56. Moore's "Law" by dogmatixpsych · · Score: 1

    Moore made a prediction about how the number of transistors in computer chips change over time. By no standard is his prediction a law. It is called a law because it has held true for the most part over time and it makes a prediction about the progress of technology. Furthermore, Moore's Law really has nothing to with the speed of processors. So arguing about whether we should or shouldn't have 10 GHz processors according to Moore's Law is pointless.

  57. FCC? by N.Muntz · · Score: 1
    or FAA

    Do I hafta say it?

    --
    You know it....
    1. Re:FCC? by Fr05t · · Score: 1

      " or FAA"

      yeah the other F word people on slashdot like to complain about ;)

    2. Re:FCC? by Kehvarl · · Score: 1

      You think that's going to stop the FCC?

  58. absolutely by willCode4Beer.com · · Score: 1

    Like how AMD has been able to make instructions take fewer clock cycles to run.
    If an operation can execute in 3 instead of 4 clock cycles the gain in speed is obvious.
    How both Intel and AMD have built branch prediction.
    We'll probaly start to see chips come out with common compiler generated routines built in (hardware peephole optimization anyone?).
    We may see some speed increases occur as the transistor count goes down from engineers finding more efficient ways to layout a chip.

    Where there is a will (profit), there is a way.

    --
    ----- If communism is a system where the government owns business, what do you call a system where business owns govern
  59. Nit by PhysicsGenius · · Score: 0

    There is no corollary (deduction or inference from axioms) about the change in price. There is an assumption of it.

  60. Where is 10Ghz PC? by 10Ghz · · Score: 1

    Well, I have been here for a while already, but I'm not politically correct

    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    1. Re:Where is 10Ghz PC? by Anonymous Coward · · Score: 0

      HA. Prove you're not politically correct. Speak some taboo truths about blacks or something.

  61. Concurrency ... again ... by C+A+S+S+I+E+L · · Score: 2, Insightful
    Concurrency is the next major revolution in how we write software

    ...as we've been saying for, oh, at least the last 20 years, which is about the time I was writing up my Ph.D. thesis on concurrent languages and hardware.

    As far as I can see (being slightly out of the language/computer design area these days), concurrent machines and languages aren't taking off for the same reasons they didn't take off in the 1980's:

    • Implicitly concurrent languages (ones where the concurrency comes for free) are either next to useless (since they tend not to have state, and have problems with a stateful world containing things like, oh, I/O), or end up not being very concurrent at all once they're running;
    • Explicitly concurrent languages (ones with concurrency constructs) are tricky to program with, and debug, if you're trying to exploit the concurrency; shared memory (tricky at the hardware level) gives you multithreading, otherwise you're into the process world with very little in terms of shared objects etc.
    • Concurrent hardware tends to have wacky constraints in order to operate with any degree of efficiency (Inmos Transputer anyone?) and is, again, a pain to program;
    • The fancy concurrent hardware is custom-built, and by the time the boffins have built a concurrent machine that runs reliably based around processors of speed X, delivering concurrency of degree Y, Moore's Law dictates that you can go to your local computer store and buy a $1000 PC with processor speed greater than X * Y.

    There's more than a handful of generalisations there, but in short: Moore's Law means that nobody is going to buy a highly concurrent computer when consumer PC's are still getting faster, and the people who really need high parallelism (modellers and the like) have their own special-purpose toys to work with.

    1. Re:Concurrency ... again ... by RockClimbingFool · · Score: 1
      Yeah, but multi-core processors haven't been on AMD's and Intel's roadmap before. They are now and a real hard look into concurrency will be required to get the increases in performance that multi-core archetecture brings.

      RTFA. Consumer PC's are not getting faster anymore.

    2. Re:Concurrency ... again ... by smallpaul · · Score: 1

      The article is about how PCs themselves are becoming concurrent processing devices thanks to hypertheading and multicore. This is the way that the chip designers are taking advantage of additional circuits. Cranking up CPU speed is not as easy anymore.

  62. Re:Moore's Law isn't Speed Doubling, it's Transist by Anonymous Coward · · Score: 1, Informative

    Actually, Moore's law states that transistor channel length will halve every 18 months.

    But thanks for playing!

  63. Keywords from TFA by willCode4Beer.com · · Score: 1

    ".. with most of their traditional approaches ..."

    So, we find non-traditional approaches. So, yes your V10 gives out at 200mph. But, then some guy comes up with an SR71 Blackbird. Then some other guy builds a rocket. Then.....

    It may be aero-dynamically impossible for a bumble-bee to fly but, its not physically impossible.

    --
    ----- If communism is a system where the government owns business, what do you call a system where business owns govern
  64. I like 'em slow. by HexaByte · · Score: 1

    I like 'em slow. That way I can go get a cup of coffee, talk to my co-workers, etc., and just tell the boss "It's still booting" or "I'm running a large spreadsheet".

    Remember the old days when we didn't expect a computer to be as fast as lightning?

    Slow down and listen to the sound of the files being saved to floppy.

    --
    HexaByte - he's a square and a half!
  65. How fast is 3 GHz? by garethw · · Score: 1

    I find that few people - even tech people - really appreciate just how fast 3GHz is.

    To put it into perspective, consider that at that clock frequency, light travels about 4 inches in one clock cycle.

    Mind boggling.

    --
    garethw
  66. Instead of asking about where it is by EM+Adams · · Score: 2, Interesting

    Start researching how to build better computers and start a company. You have some options to explore -

    1) DNA/Molecular computers
    2) Atomic switches
    http://www.physicsweb.org/articles/news/ 9/1/2/1
    3) Betacomputation (Switches made from neutrons and protons that can be on/off by adding/removing electrons bound inside of the hadronic structure)
    This makes for good power supply too http://www.betavoltaic.com/
    4) Positron/electron photon exchange
    (Yes Virginia, antimatter/matter changes the phase of absorbed photons)
    5) Integrated silicon/optic chips
    6) Black holes (See Sci Am Dec 2004)

    Also for all of you aspiring scientists out there do yourself a favor and join the present by reading about nonlinear/nonunitary mechanics
    http://www.i-b-r.org/ir00018.htm
    You'l l save yourself a lot of time by not modeling nonlinear processes with linear equations and infinite corrections under 10^-13 m (ultraviolet divergences).

    --
    Posthuman since 2001.
  67. No surprise!! by CaptScarlet22 · · Score: 1

    There is no surprise here people. IMHO there hasn't been any new technology in the past 50 years, for the consumer. Sure everything is computerized, runs fast, does a crap load of things...But the basic make up is still the same. Cars are still the same, Planes are still the same, houses are still the same...washing machines, blenders, The basic make up of just about everything is still the same as it was for your parents or grandparents. There nothing new here, hasn't been for awhile... Nano looks promising, cloning looks good...But it's so far off, I won't see anything come from them in my life time.

    I might not be up on all things new, but I havn't seen anything Differnet in a very long time.

    What we need here is a new composites, new minerals....Something different.

    Captain Scarlet............out

    --
    It's left blank because I have nothing to say to you punks!
    1. Re:No surprise!! by drspliff · · Score: 1

      You haven't seen anything Different? May I mention one word.. Dyson

      The world is full of innovation, and Intel and the other big guys are just waiting for the next big thing (aka Cell processors), sure they'll do exactly the same as before - but internally will be completely different

  68. Other disappointments... by NiKnight3 · · Score: 1

    You have dollars? Where can I get me somma those? Guess it's just another thing that I predicted I'd have 5 times more than what actually happened.

  69. Apple CPUs catching up....? WTF? by TibbonZero · · Score: 3, Interesting

    And to think, that apple's CPUs are nearly at the same 'number speed' in the mhz race now!

    Who would'a ever thought to see that happen?

    --
    Tibbon
    tibbon.com
    1. Re:Apple CPUs catching up....? WTF? by Anonymous Coward · · Score: 0

      Well, IBM seems to be a better CPU-manufacturer than Motorola.

    2. Re:Apple CPUs catching up....? WTF? by DebianDog · · Score: 1

      Yeah and the REEEAALLYY cool thing is my 3 year old, dual 533 MHz G4 is faster than my buddies new Dell. He hates that!

      Look for Dual G5's at 3 GHz on the 10th of January. ;-)

    3. Re:Apple CPUs catching up....? WTF? by javaxman · · Score: 1
      Yeah and the REEEAALLYY cool thing is my 3 year old, dual 533 MHz G4 is faster than my buddies new Dell. He hates that!

      That's what the sucker gets for buying a Celeron and running XP on it.

      Oh, and who saw PowerPC CPUs catching up in clock speed ? Probably some engineers at Apple, Motorola and IBM, I'm guessing...

    4. Re:Apple CPUs catching up....? WTF? by DebianDog · · Score: 1

      Actually the VERY BEST thing is I do not have to run windows ;-)

    5. Re:Apple CPUs catching up....? WTF? by Anonymous Coward · · Score: 0
      Hardly. The pitiful G5 can't even reach 2.5 GHz without water cooling. Steve Jobs was lying out of his ass when he said G5 can reach 3 GHz in a year (in June 2003).

      Before you say, the water cooling is not there because of aesthetics or silence, it's because the CPU puts out too much heat, period.

  70. Moore's Second And Third Laws by nick_davison · · Score: 1

    Moore's Second Law:
    Every 18 months there will be twice as many stories saying Moore's law can't continue.

    Moore's Third Law:
    In 18 months, with hindsight given to whatever the next advance is that they missed, they will look twice as stupid.

  71. What I need 10 ghz for by way2trivial · · Score: 3, Informative
    better than realtime video transcoding maybe?

    authoring a DVD in less than an 4 hours from the dv-avi source?

    my own CGI production in my lifetime?

    --
    every day http://en.wikipedia.org/wiki/Special:Random
    1. Re:What I need 10 ghz for by Paul+Jakma · · Score: 1

      Why do you think this requires GHz to do?

      There's nothing that says amount of work CPUs can do must scale with (and only with) clock frequency. Eg, Ancient SGI O2's can do real-time MJPEG PAL or NTSC encoding, despite clocking between 175 to 400MHz. Ok, the encoding is done on a seperate dedicated chip (a 66MHz clocked 128bit SIMD vector unit)[1], but with todays transistor budgets no reason that kind of functionality couldnt be integrated into a CPU (already has to an extent - the various SIMD instruction extensions for PC CPUs).

      1. Hmm, a UMA system with MIPS CPU with additional MIPS derived vector processing units, that sounds
      familiar

      --
      I use Friend/Foe + mod-point modifiers as a karma/reputation system.
    2. Re:What I need 10 ghz for by Anonymous Coward · · Score: 0

      Bah, I do all those things you "dream of" with something you consider is "throw away"

      it's call clustering, and yes, you need to break away from your fisher-price OS from microsoft and use a Unix either BSD,Linux or OSX.

      funny how all the big movie companies and CGI companies do this all the time and you never bothered to look into it.

      and yes, maya is available for linux.

      Oh i also create DVD masters on DLT tapes to send to the pressing house on linux, if you are wondering about "professional" work.. Scenarist will run under wineX and you can not get any more profesional DVD authoring than Scenarist.

      i suggest you quit making excuses and do what you want.

    3. Re:What I need 10 ghz for by ratboy666 · · Score: 1

      The job of coding an MPEG video stream can be done in parallel. At each I frame there is a natural break.

      So, a 2 processor core could do your DVD in 2 hours, 4 processors in one hour, and 8 in 1/2 hour.

      Of course you end up with i/o bottlenecks...

      ratboy

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    4. Re:What I need 10 ghz for by evilviper · · Score: 1
      better than realtime video transcoding maybe?

      I do that already, on my puney 1.66GHz Athlon XP.

      Clearly, your problem is the gross ineffeciency of the software you use, not the hardware. Programmers have, for much too long, programmed grossly ineffeciently, depending on the improvements in hardware to make their crappy software tolerably fast.

      I use mplayer/mencoder for video encoding, myself, but anything based on ffmpeg/libavcodec/lavc should be nearly as fast. There are even numerous options for Windows, if you're stuck with it.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  72. suckered! by Jah+Shaka · · Score: 0

    Sounds like they suckered you and gave you one of them Apple boxes Instead of a new Intel P4 system... i got dual 3.6ghz procs for christmas which i overclocked to 4ghz each giving me 8ghz of pure power! So i dont know about you turkeys, but im close to 10ghz over here...

  73. Image prosessing by saigon_from_europe · · Score: 1
    What else would it help to have the speed for?
    Image processing in CAT systems, for example.
    --
    No sig today.
  74. BeOS by Anonymous Coward · · Score: 1, Funny

    Now that the only way up is through more CPU's, I think it's time that the inherently multithreaded BeOS makes a big comeback.

    Yay BeOS!

  75. moderate the posts themselves by l3v1 · · Score: 1

    I mean please let us give -10 "junk" "yesterday's news" "no sane human being interested" "FUD" "poster is an analphabet [i.e. can't read the news, just post]" whatever.

    First, most of said "bugs" were fixed the day before last blue moon. Second, there are "bugs" mentioned which are the fault of 1). windows 2). user (which means they can't freaking configure the darn Thunderbird to store the mails where they know it's most safe). This last one is as saying an applciation is faulty and buggy because it has a default store directory option which it uses if nothing else is specified. Come on. Whatever. To the malformed URL "bug": you can do that on every and each browser, huw is that a sw bug. Get lost.

    Get a life, post news. Junk we have a'plenty already.

    --
    I am putting myself to the fullest possible use, which is all I can think that any conscious entity can ever hope to do.
  76. No big deal really by hattig · · Score: 1

    The problem was Intel's P4 design that didn't take heat into consideration. It hit 3GHz and aside from bus speed bumps, cache bumps, and an IPC lowering redesign (Prescott) that has so far allowed it to attain 3.8GHz. When did it hit 3GHz? Was it 2 years ago? That's pretty abysmal in my opinion.

    Of course, AMD has been slowed down as well, having not done many speed bumps in the past year, aside from a 2.6GHz boutique release. However AMD will probably get 2.8 and 3.0GHz processors out of the door this year.

    Of course, for Apple, they've gone from 1.2GHz G4s to 2.5GHz G5s. The slow-down was earlier for Apple, and they've got over it, and hit another one. Still, those processors are from different companies.

    Dual core is a logical progression, when you can do it and there is a real benefit to doing it (OS dual support, application multi-threading, etc). It can keep the power consumption lower (you don't need to push the processor to the maximum), and it spreads the heat sources out, instead of having one extremely hot core, you have two merely hot cores to cool.

    The article wibbles on about GHz, but what matters is performance. Whilst benchmarks aren't ideal, I'm sure a graph of Spec Rate performance on single processor (where a processor can have multiple cores, of course) and multiprocessor has been improving steadily over that time. 2 years ago Athlon XPs were pushing 900 in SpecFP and stuff, yet high end Athlon 64s now push 1700+. Systems are getting faster! It is just the value of GHz as a useful system performance indicator is no more, and hasn't been for around 5 years to be honest. People are waking up to that.

  77. I was being facetious and I am wrong by willCode4Beer.com · · Score: 1

    I appologize to you.

    A bit difficult to understand was your grammar. :)

    --
    ----- If communism is a system where the government owns business, what do you call a system where business owns govern
  78. 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.

    1. Re:Concurrent Applications are not The Answer by TeknoHog · · Score: 1
      ..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-

      This is already being done with decent compilers and decent languages. It requires that the language is suitably high-level (unlike C, for example) so that the compiler has more freedom to make optimizations. HLLs should be nicer for programmers in many other ways too.

      The relevant experience I have is with Fortran 90 and the PGF compiler back in 2001, on a dual P3 machine. The compiler produced parallel code to utilize both CPUs and their vector instructions (such as SSE).

      So, this has been done for ages already, but people need to ditch low-level languages like C for this scenario to work.

      --
      Escher was the first MC and Giger invented the HR department.
    2. Re:Concurrent Applications are not The Answer by Anonymous Coward · · Score: 0

      This sort of thing always makes me smile.

      >it's hard to do multi-threaded programming

      Has anyone heard of QNX? Distributed applications are a snap to write (not only are they multi-threadded, but they can communicate across different machines via a network]. Given Microsoft normally invent everything about 20 years after someone else has done it - they should catch up to where QNX 2 was in the late 80s [still VERY capable of supporting distributed applications]. Get to it Microsoft - you've got more inventing to do :)

      Btw, if I can write distributed apps in QNX, anyone with a bit of C programming experience can.

      Your Friendly

      AC

    3. Re:Concurrent Applications are not The Answer by eraserewind · · Score: 1

      It all depends on the framework. Web server stuff is essentially multi processs or multi threaded, but nobody claims it's particularly hard to do, because Apache, etc. provide a suitable way for it to be implemented, so the coder is only writing the interesting bit, and leaving all the multithreading to the server. If someone builds a suitable framework for a particular application domain, then everyone making apps in that domain get their multithreading essentially for free.

      But, you are right, the vast majority of programmers are not suddenly going to start writing code with pthread_create calls in it, because it's wasting time solving a code problem that is better spent solving a business problem.

  79. Bad trendlines... by thesp · · Score: 1

    ...can really spoil your conclusions. Examine Figure 1 in the article. Log-log graph, with a two-kinked trendline. The article uses this figure to justify the statement that

    "Around the beginning of 2003, you'll note a disturbing sharp turn in the previous trend toward ever-faster CPU clock speeds."

    However, these trendlines are meaningless; they are plainly wrong. For a start, all the data points are to one side of the trendline. That's a bit glaring, even if you're not a statistician. More interestingly, if you just consider the points, rather than the trendlines, you'll find a single trendline, linear in log-log space, that fits the data, up to the present day. It has a similar gradient to the supposed 1980-1994 trendline. During the 1995-2005 period the points were clustered slightly above this line, but the effect is that of a big technological push - like a region of compressed time on the graph, just what you'd expect with the amount of money pushed into the industry about this time. Otherwise, pseudo-Moore's Law is on track. Now, in the development labs, there's another story. Exponential growth is already hitting up against a wall, and we must turn to QIP technologies to sort that out.

  80. Re:Should always specify North or South. by BitchKapoor · · Score: 3, Insightful
    This means your CPU could be spread out over larger areas with little to no performance hit.

    That's not true at all. At a mere 2GHz, light can only travel 15cm (6in) through free space in one cycle -- hardly a long distance. Add in modulation and switching delays, and you really can't ignore the board-level latency even with optical interconnect. On the other hand, even on-chip communication takes multiple clock cycles these days, so maybe it wouldn't be that much worse..?

  81. Speed and performance by Anonymous Coward · · Score: 0

    The processor is only as good as the software it runs. In other words, even if you have a fast processor, it's not going to really help unless the programs you run, are actually efficient.

    Maybe a bad analogy, but kind of like driving a car that can go 200 miles per hour, on a roadway that is 80 miles per hour.

  82. what a troll by GunFodder · · Score: 1

    Why would anyone throw out the language/runtime with built-in multithreading support when system processors are becoming increasingly parallel?

  83. I'm betting on hardware by scotay · · Score: 1

    Economics will favor hardware acceleration

    I believe the software industry is still in its infancy and humanity's physical pursuits (hardware) will always outpace our intellectual pursuits (software). It remains simply too expensive to fix performance by assuming the software industry will deliver ubiquitous quality. Too many amateurs and those learning on the job in this industry (myself included) and that is not going to change anytime soon.

    The complaining about limits in hardware and such generally comes from Pentium IV owners (myself included). Not all future architectures will be as dismal. Even for Intel. These multi-channel future baselines will be good. Reminds me of the Amiga days. When developers could assume multiple channels of DMA without penalty and concurrent access to memory while custom chips were displaying graphics and playing sounds, they were freed to do amazing things with the software.

  84. On a related note by EM+Adams · · Score: 1

    Computability at the Planck Scale
    http://www.arxiv.org/pdf/gr-qc/0412076

    --
    Posthuman since 2001.
  85. Bottleneck by CyNRG · · Score: 1

    Faster processors MEAN NOTHING!

    Your computer is as fast as the slowest hardware component that is used. Additionally, if the hardware component doesn't provide enough capacity, then it causes slowness.

    Traditionally, the order of slowness is (slowest first):
    1. Network
    2. Disk
    3. Main Memory
    4. CPU

    (I'm not counting peripherals)

    CPU is last. Concentrate on more memory and really fast disk. This gives you more for your money.

    Now, use (or write) really good software. That would be non-Microsoft. Put Linux on on your box and double the speed right away.

  86. RTFG by Anonymous Coward · · Score: 0

    Read the fine graph. Look at the data points and ignore the author's blue lines for a minute. There is nothing in the data that suggest a hard limit has been reached. OK... the rate of change slowed down a little in 2002. That's all.

  87. OT: Your sig is wrong by tomhudson · · Score: 1, Offtopic
    Educational Sig: Referrer is spelled with two r's, not one. HTTP_REFERER has a typo.
    No, referrer has 4 r's, not two:
    R - E - F - E - R - R - E - R
    If you're going to be pedantic, at least get it right :-)
  88. TFA's author doesn't know what he's talking about by CTho9305 · · Score: 1

    Today's CPUs sport some more powerful instructions, and they perform optimizations that range from the pedestrian to the exotic, including pipelining, branch prediction, executing multiple instructions in the same clock cycle(s), and even reordering the instruction stream for out-of-order execution.
    Calling any of those "optimizations" is a stretch, in my opinion, unless a V8 engine (or maybe two 4-cylinder engines with a shared gas tank and transmission) is an "optimization" of an inline 4.

    Note that some of what I just called "optimizations" are actually far more than optimizations, in that they can change the meaning of programs and cause visible effects that can break reasonable programmer expectations.
    Not on any "normal" CPU (see explanation below).

    But in recent years they have been willing to pursue aggressive optimizations just to wring yet more speed out of each cycle, even knowing full well that these aggressive rearrangements could endanger the semantics of your code.
    They won't affect the semantics of code unless the CPU has a design problem (again, see below).

    Two noteworthy examples in this respect are write reordering and read reordering: Allowing a processor to reorder write operations has consequences that are so surprising, and break so many programmer expectations, that the feature generally has to be turned off because it's too difficult for programmers to reason correctly about the meaning of their programs in the presence of arbitrary write reordering. Reordering read operations can also yield surprising visible effects, but that is more commonly left enabled anyway because it isn't quite as hard on programmers, and the demands for performance cause designers of operating systems and operating environments to compromise and choose models that place a greater burden on programmers because that is viewed as a lesser evil than giving up the optimization opportunities.
    Actually, you reorder them inside the processor, and then do a check to make sure your reordering did not affect the functionality before actually committing to memory (some instruction sets allow memory access reordering, and have explicit instructions to specify that certain operations must happen before others). As it is right now, your top-of-the-line x86 chip is going appear to execute a program exactly the way it would if it only did one operation at a time, and everything in order. A HUGE amount of work goes in to implementing "precise interrupts" - making sure that at any point, if you interrupt the CPU, all instructions before the current PC (program counter) have executed to completion, and no subsequent instructions have started execution).

    Basically, the way instruction reordering works is that instructions are fetched from memory in order, and their dependencies are evaluated. They're given tags (unique IDs inside the CPU), and their tags are added, in order, to a queue at the end of the pipeline. Then, they flow through the actual execution units out of order. As they execute, they update a "speculative state" - results are sometimes stored in an entirely separate register file called the "future file". An instruction can only affect "architectural state" (programmer-visible state) when it is the oldest instruction in the queue at the end of the pipeline. If an instruction has an exception (divide by zero, software breakpoint, interrupt), all subsequent instructions are squashed - you can do this because the queue is added to in order, and the machine looks just like an in-order machine would.

    It's worth noting that various researchers have looked into the optimal pipeline depth - basically, due to various sources of overhead (flip flops cannot store values instantaneously, there is clock skew on a chip, and other higher-level factors like data dependencies), they conclude that 6-8 gate delays

  89. logarithmic scale and light speed by notany · · Score: 1

    One thing to notice in ddj-diagram is that the x-axis is logarithmic. Jump from 1 MHz to 1 Ghz in speed equals to jump from 1GHz to 2 Ghz. I think we are doing just fine.

    One thing to consider is that electrical signals in chips have maximum speed of 2/3 of light speed.

    Homework: how many centimeters (or inches) electrical signal travels in one clock cycle when processor is running 1Ghz and 10Ghz.

    Yes! it is kind of hard to design chips when bits in other side of the bus are different form opposite side.

    --
    Dyslexics have more fnu.
  90. Longhorn Screwed? by SVDave · · Score: 3, Informative

    According to Microsoft, an average Longhorn system will need to have a 4-6GHz CPU. But if when Longhorn arrives, 4GHz CPUs are high-end parts and 6GHz CPUs don't exist, well...I don't predict good things for Microsoft. Longhorn in 2007, anyone? Or maybe 2008...

    1. Re:Longhorn Screwed? by Anonymous Coward · · Score: 0

      Well, it's the new year, so it'll have to be 2008 now since Longhorn is perpetually three years off. Expect an official announcement any week now.

    2. Re:Longhorn Screwed? by Anonymous Coward · · Score: 0

      You speak ill of Longhorn but we all know you'll be first in line to pirate your copy. Everyone talks a big game but they still want the software, they just don't think Microsoft deserves to be compensated for it, that's all.

  91. Re:10ghz. Huh??! by JFitzsimmons · · Score: 1

    For science, yes perhaps, but the everyday user is not doing that many floating point calculations. Even if they are, they won't need them done at the speed that a scientific application would.

    Flops are more important for scientific applications, which is why you usually see all the large modern supercomputers measured using this unit of measurement; universities and research groups are the targeted audience.

    For the normal user, floating point calculations aren't as important, so hertz is a decent standard for rating a CPU's speed. MIPS (millions of instructions per second) is also a halfdecent measurement system for the general person, but it can only be used to compare CPUs of the same architechture.

    --
    Beware he who would deny you access to information, for in his heart he dreams himself your master. -Anonymous
  92. good quotes by willCode4Beer.com · · Score: 1

    http://curbstone.com/_pigs.htm

    "Everything that can be invented has been invented."
    Charles H. Duell, Commissioner, U.S. Office of Patents, 1899

    "I think there's a world market for about five computers."
    Thomas J. Watson, Chairman of the Board, IBM

    "The bomb will never go off. I speak as an expert in explosives."
    Admiral William Leahy, US Atomic Bomb Project

    "This 'telephone' has too many shortcomings to be seriously considered as a means of communication. The device is inherently of no value to us."
    Western Union internal memo, 1876

    "Heavier-than-air flying machines are impossible."
    Lord Kelvin, president, Royal Society, 1895

    "Professor Goddard does not know the relation between action and reaction and the need to have something better than a vacuum against which to react. He seems to lack the basic knowledge ladled out daily in high schools."
    1921 New York Times editorial about Robert Goddard's revolutionary rocket work

    "Man shall never reach the moon, for such a quantity of gunpowder would be needed as to gravely injure the crew."
    Children's Encyclopaedia, 1926

    "Man will never reach the moon regardless of all future scientific advances."
    Dr. Lee De Forest, inventor of the vacuum tube, father of television and owner of over 300 patents

    --
    ----- If communism is a system where the government owns business, what do you call a system where business owns govern
  93. 4GHZ CPU, 256 GB RAM and no hard drive by arhar · · Score: 0

    This is not 10 GHZ, but due to lack of hard drive (who needs hard drive slowing things down if you have 256 GB of RAM?) and 4 GHZ CPU, this is probably going to be ten times as fast as today's desktops.

    Don't let the horrible site design alarm you, this is a real thing, and was displayed at this year's CES. Right now, it's gonna cost about $14K, but will drop in the near future.

    1. Re:4GHZ CPU, 256 GB RAM and no hard drive by settsu · · Score: 1

      Is this option available for that dough?

      If you don't understand what you're reading, the action-packed demo movie won't help.

      But it does include an intense space sequence featuring high-speed satellite fly-bys!

  94. We made progress by megarich · · Score: 1

    Well maybe we don't have 10G, but we do have 64bit!!!

  95. Game developers are already there by Animats · · Score: 1
    I've been thinking that for about as long myself. But this time, it looks like concurrency is real. Because we're really hitting the wall on single processor speed, but not cost per transistor.

    But that concurrency might not be in the main CPU. It will be in the graphics processor. Graphics processors don't have the von Neumann bottleneck - with enough hardware, you could have one processor per pixel without changing the application level programming model. Shader languages, from Renderman on, are explicitly one program per pixel.

    The Playstation 2 is the world's largest selling non von Neumann machine. The PS2 is two very capable vector processors, an underpowered MIPS CPU, and a frame buffer. Its vector processors are wierd; they're nothing like a standard CPU. Yet, with difficulty, programmers are doing work in them. Not just graphics, either - physical simulation and planning.

    The game development community is already dealing aggressively with concurrency. Pretty well, too.

  96. 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.

    1. Re:GaAs??? GaAs is material of the future... by Anonymous Coward · · Score: 0

      IBM got burned on X-ray lithography (Fishkill NY) also.

    2. Re:GaAs??? GaAs is material of the future... by loose+electron · · Score: 2, Insightful

      GaAs has a big problem with yield loss in manufacturing.

      As such, it is ok for small stuff (under 20 transistors)but is not going to fly for million transistor CPU's

      --
      www.effectiveelectrons.com "chips that work" Analog, RF, Mixed Signal
    3. Re:GaAs??? GaAs is material of the future... by k98sven · · Score: 2, Insightful

      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.

      I'd think the more likely reasons would have to do, for starters, with consumers not wanting or being able to afford a computer that requires constant cooling with liquid nitrogen (or even worse, liquid helium) to work.

    4. Re:GaAs??? GaAs is material of the future... by FuzzyDaddy · · Score: 2, Insightful
      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... ;-)

      I haven't been in the superconducter field for ten years now... what's the technology being used for the switches/logic gates?

      As for GaAs, it's alive and well in the world of RF (analog) amplifiers going up to 100 GHz - I think the current technology uses a 6" wafer. (see, for example, WIN Semiconductor)

      --
      It's not wasting time, I'm educating myself.
    5. Re:GaAs??? GaAs is material of the future... by ChrisMaple · · Score: 3, Informative

      Vitesse had CMOS GaAs as small as 0.35u and had to abandon the technology when smaller geometry silicon caught up in speed with GaAs. The money wasn't there (in 2000) to make a smaller geometry fab. Also, my understanding is that at smaller geometries the advantage for GaAs is reduced. Indium phosphide is another possible technology. The big problem is that a huge heap of money will be needed to develop a high speed, high integration replacement for silicon, and there's no guarantee that it will ever pay off. For the forseeable future, consumer processors will remain silicon.

      --
      Contribute to civilization: ari.aynrand.org/donate
    6. Re:GaAs??? GaAs is material of the future... by PaulBu · · Score: 1

      Not only that, but you look at the power dissipated by 20 transistors (actually if it is, say, InP, you can talk about 100 transistors) and multiply it by the number required to build a CPU... ;-) You do not want to dissipate (and somehow take off the chip) a megawatt per CPU even in the supercomputer box, not to mention anything smaller than that!

      Paul B.

    7. Re:GaAs??? GaAs is material of the future... by drinkypoo · · Score: 2, Insightful

      Given that a liquid nitrogen cascade cooling system is beyond the reach of most consumers, so-called "high temperature superconductors" are basically out of the question. Until we actually have cost-effective room temperature superconductors, I kind of doubt we're going to see much of this. Unless you mean something different than "superconductor" when you say superconductor, I'm at a loss as to where you are going with this.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    8. Re:GaAs??? GaAs is material of the future... by PaulBu · · Score: 1

      I was not talking about the consumer market here (yes, I understand that the original poster wanted a 10 GHz processor under his desk, but I did not had that in mind). What consumers really want is a nice thin client in there, hmm, cellphone with a laser projected image directly on there retina and lots of bandwidth and computational power upstream.

      People who provide THAT power and bandwidth CAN afford whatever cooling is needed if they can get more bang per buck. My favorite SCE project was to allow telcos to replace 5 racks of routers with one rack, half of that densily packed SCE, half cooler compressor and electronics, same number of lines, all running at 60 GHz rather than 10...

      And yes, you need LHe cooling for this stuff, but you would be surprized at how advanced modern pulse-tube coolers are. Without disclosing anything that I am not supposed to disclose ;-), check out this NASA presentation about space-qualified coolers: here,
      if this would become any kind of a mass market a cooler like this would cost a couple thousand $$, maybe a bit too costly for your home, but definitely affordable for telco/service provider market.

      Paul B.

    9. Re:GaAs??? GaAs is material of the future... by PaulBu · · Score: 1

      I was not talking about consumer electronics, see my reply a couple of posts up...

      Paul B.

    10. Re:GaAs??? GaAs is material of the future... by PaulBu · · Score: 2, Informative

      I haven't been in the superconducter field for ten years now... what's the technology being used for the switches/logic gates?

      Hmm, I am wondering what kind of logic were you using 10 years ago! ;-) Good old latching stuff? No, it was 1994, SFQ and Nb triulayer was already out there in the field, actually I did come to this country to work on it some time in '92, I guess...

      Yes, it is SFQ/RSFQ (Single Flux Quantum) logic, counting individual magnetic flux quanta, but no, it has nothing to do with now over-financed "quantum computing". ;-) We can put tens of thousands Josephson junctions per chip now, all connected with matched superconductor transmission line (i.e., no RC time constants, nor F*CV^2/2 power), though which picosecond-wide pulse fly just fine. If you are interested, I can tell A LOT more -- hey, I'm one of the people who are still interested in pursuing this technology...

      As for GaAs, it's alive and well in the world of RF (analog) amplifiers going up to 100 GHz

      And with InP you can go to 150 GHz and maybe higher amplifiers (though not broadband), but there is a huge difference between being able to amplify a signal and being able to do any kind of meaningful digital logic at fixed power consumption... Actually, time for me to get off /. and get back to those pesky transistors... ;-)

      Paul B.

    11. Re:GaAs??? GaAs is material of the future... by crgrace · · Score: 1

      I work on CMOS analog chips and am interested in getting into III-V design (particularly data converters in Indium-Phosphide). Where do you work? Reply here are email me at carl_r_grace@yahoo.com

    12. Re:GaAs??? GaAs is material of the future... by Pavan_Gupta · · Score: 1

      Interesting points -- but it looks you've neglected to explain the High Temperature Superconductors which made waves in the late 80s. In fact, a company called Superconductor Technologies out of Santa Barbara, CA received exlusive rights to certain Thallium compounds disovered by the University of Arkansas which become superconductors at temperatures as high as ~120K! That's well within the range of liquid nitrogen cooling (which provides 77K).

      Theoretically, that could mean that users would only need a few watt cooling device to maintain a liquid nitrogen cooling system (as is already maintained by some of the higher end overclockers). The possibility that resistance could go down 2 orders of magnitude (realistically), and theoretically could go down infinitely, leaves chip manufacturers with IMMENSE room to work with. The idea that your processor might loose integrity at high clock cycles -- due to heat (and many other things) drops to nill, and could open the flood gates to super fast computers on the desk.

      You're absolutely correct, Paul, that using thin clients connected to an ultra fast backend would work in a situation where someone's pushing a traditional superconducting device, but I'm willing to say that superconductors are no longer something only big institutions can fancy, but something that anyone can enjoy. For example, to break down the cost of this issue, I found a fact from hyperphysics.com that said, "The amount of liquid helium to operate an MRI device costs about $30,000 per year. It has been estimated that the use of liquid nitrogen superconducting magnets could save $100,000 per year in overall operating costs for each MRI device."

      I forsee the day that a user will be able to use a superconducting set of electronics on the desk. Your idea is not wrong, but HTS will be the future.

    13. Re:GaAs??? GaAs is material of the future... by FuzzyDaddy · · Score: 1

      No, I was building magnetometers - strictly analog sensor stuff. Flux transformers and Squids, integrated using YBCO. (For John Clarke at Berkeley)

      --
      It's not wasting time, I'm educating myself.
    14. Re:GaAs??? GaAs is material of the future... by PaulBu · · Score: 1

      OK, I surely know John Clarke, but for my like I was trying to steer clear from analog SQUIDs, pushing for digital stuff.

      Paul B.

    15. Re:GaAs??? GaAs is material of the future... by PaulBu · · Score: 2, Informative

      STI and Conductus were successful in marketing PASSIVE HTS components (analog filters for cellular basestation receivers) and their main accomplishment was, actually, making "normal" systems engineers not to be scared of having a cooler in the system (providing a reliable cooler was also important ;-) ). The brilliant marketing gimmick was that they actually packaged a traditional filter and a switch in parallel with their SC filter in the same box, so if the cooler would fail the system would fall back to the traditional normal design, with some loss of capacity, of course, but at least it would still function.

      As to digital logic, it is REALLY hard to make reproducible Josephson jucntions (active elements in SCE circuits) in HTS. One can make 2-4 of them for SQUID sensors (and it is a bit market for HTS too), but for digital stuff you need thousands and millions of them. In certain way HTS vs. LTS is similar to GaAs vs. CMOS -- it is easy to make a really nice, but simple, analog front-end in one, but the other can handle much more processing.

      Replacing metal wiring on transistor chips with superconductor wiring will not help that much, yes, part of the RC constant which takes care of wire resistance, will be gone, but you'd still dissipate F*CV^2/2 power to charge/discharge the line. To fully utilize SCE logic one needs to use SCE active elements (current-sensitive JJs, not voltage-sensitive transistors).

      I forsee the day that a user will be able to use a superconducting set of electronics on the desk.

      Me too! ;-) It definitely can be done IF some larger system is built and verified first, then technology becomes a commodity. Check out, for example, this presentation by my former advisor and one of the godfathers of the whole field, seach for PeT workstation... ;-)

      Paul B.

      P.S. There is another fundamental reason to chose LTS, rather than HTS superconductors. The beauty of SFQ logic is that it uses almost quantum-limited amount of energy per switch. When one starts increasing temperature, thermal noise becomes too high (yes, even at 77K) and the main advantage -- tiny energy dissipation, which allows for very dense packaging -- goes away.

    16. Re:GaAs??? GaAs is material of the future... by 14erCleaner · · Score: 2, Interesting
      You would not want to build a processor out of those, Cray tried with Cray 4 and failed... ;-(

      I worked at Cray Computer, so I know something about this... The Cray-3 (also GaAs) was working OK when the bankruptcy hit, and the Cray-4 would probably have worked.

      The failure of Cray Computer was due to competition and missing market windows, not due to the choice of technology per se. (Admittedly the late deliveries were due to difficulties with getting the processors working, but much of that was due to aggressive circuit-board designs that led to problems with open contacts, and the difficulty of repairing them).

      btw, the 10th anniversary of the CCC bankruptcy is coming up on March 24th. My, how the years fly by sometimes.

      --
      Have you read my blog lately?
    17. Re:GaAs??? GaAs is material of the future... by Anonymous Coward · · Score: 0

      The main issue with MRI and HTS is that as of yet, the known HT superconductors can't handle the current density in NMR/MRI coils. These things press the limits of 'conventional' superconductors as it is.

      But yes, it is something to hope for. But I'm a bit pessimistic. It's hard to say since HTS isn't understood.. but it's a quantum phenomenon, and those things tend to get sticky when temperatures go up and quantum decoherence times go down.

      I doubt it's theoretically impossible.. but neither is keeping an ice cube from melting on the surface of the sun.. Just increasingly difficult.

    18. Re:GaAs??? GaAs is material of the future... by PaulBu · · Score: 1

      Do not get me wrong, Cray-4 would be a technological marvel, as all the previous ones (I've had a chance to see one of its boards once! ;-) ).

      but much of that was due to aggressive circuit-board designs that led to problems with open contacts, and the difficulty of repairing them

      But did not it have at least something to do with 1) low level of integration of the chips, thus need for more wiring on the board and 2) necessity to take all that frigging heat off safely.

      The failure of Cray Computer was due to competition and missing market windows

      The end of Cold War did not help much either...

      btw, the 10th anniversary of the CCC bankruptcy is coming up on March 24th. My, how the years fly by sometimes

      I second that!

      Paul B.

    19. Re:GaAs??? GaAs is material of the future... by HyperCash · · Score: 1

      Actualy. The Cray 3 used GaAs. There is a piece of on on display next to a full Cray 1 and full Cray 2 at the computer museum in Mountian View CA. I do beleive that only 1 Cray 3 was produced, however.

      Just thought I'd let you know that it has been done.

      --HC

      --
      So I'm jump'n up and down screaming show me the money.
  97. When? by Anonymous Coward · · Score: 0

    When I will be able to visualize this fractal http://http//www.superliminal.com/fractals/bbrot/b brot.htm in real time, I will be satisfied with the processors speed.

  98. Re:Moore's Law isn't Speed Doubling, it's Transist by stratjakt · · Score: 2, Interesting

    I hate to say it, but what do you think you need 10GHz for anyway? Unless you've got a REALLY fat pipe, there's a limit on how much pr0n you can process ;^)


    Photorealistic (or at least much better than the current high-end) rendering in real-time, I have some database apps that do a whole lot of number crunching, I have plenty of large projects that take 20 minutes to compile on a 3.06 P4 - CPU speed is the bottleneck on all of these.

    A 10 Ghz CPU would probably bring with it 2GHz+ BUS and RAM.

    You can never have too fast a CPU or GPU, too much RAM or too much HDD space.

    A multicore CPU is great, but no substitute for raw speed. It's like comparing a bullet train to a fleet of honda escorts. The cars can move the same group of 1000 people, but the train does it so much faster and more efficiently.

    --
    I don't need no instructions to know how to rock!!!!
  99. 6.40 GHz is all anybody should ever need by Anonymous Coward · · Score: 0

    'nuf said.

    1. Re:6.40 GHz is all anybody should ever need by jasonditz · · Score: 1

      He's got a point:

      Even if there might someday be a compelling reason for faster CPUs, there just isn't yet.

      As far as I'm concerned, we hit the wall years ago. The system I'm typing on now is a 1.1 Ghz Duron with enough RAM to run SuSE at a nice rate. My laptop is a 400 Mhz G3 that also, in all honesty, is as fast as it needs to be. Both are now about 4 year old technology.

      Until the new killer app comes out that absolutely needs a faster processor, most people are going to keep buying on the low end, and companies like Intel are going to see dwindling returns on new chips.

    2. Re:6.40 GHz is all anybody should ever need by Anonymous Coward · · Score: 0

      "Until the new killer app comes out that absolutely needs a faster processor"

      Um, would that be Longhorn?

  100. Here comes the hertz gang again :\ by Mordaximus · · Score: 2, Interesting

    Which processor outperforms which:

    1a)486-25SX
    1b)486-25DX

    2a)PIII - 450
    2b)G4 - 450

    3a)G3 - 300
    3b)Playstation 2 - 300

    Moral of the story : there are far, far more important performance measurements than clock frequency. If you think otherwise, you might as well slap a VTEC sticker on your case.

    P.S. As other's have pointed out, Moors law has nothing to do cpu frequency.

  101. ubiquitous?? by Anonymous Coward · · Score: 0

    SO you want to make it more... etheral? Dude, it's called ENGLISH. Quit using bloglish.

  102. "speed" of electricity by lingqi · · Score: 1

    the proper term is probably "signal," but anyway, depending on your dielectric and how you set up your lines, your speed varied but almost all of them is a fraction of c. IIRC coax is ~25cm / 1nS, FR4 (PCB material) is ~18cm / 1nS, and internal wiring in chips are actually slower, which means clock distribution is a very big deal within that 1.x sq.cm of silicon.

    --

    My life in the land of the rising sun.

    1. Re:"speed" of electricity by Anonymous Coward · · Score: 0

      18cm/1ns = .18/.000000001 m/s = 1.8e8 m/s = 0.6c = 3/5ths the speed of light

  103. Re:Limit is about marketing and ROI, not engineeri by willCode4Beer.com · · Score: 1

    I am tempted to agree but there is still a high demand for a "yet faster" machine. Its just not with infinite price. So, the second part of the engineering task is to keep the production costs inline while attempting to meet the demand.

    It generally appears that if you can get the price of a high end chip below ~$400 its going to sell.

    The companies are pretty good about getting the prices down once production is up. Compare a 1ghz chip today with one 2 years ago. You can even pick up a knock-off one now (microtel? I forget the name).

    --
    ----- If communism is a system where the government owns business, what do you call a system where business owns govern
  104. Do we really need it?! by adeydas · · Score: 1

    While the idea of having a superfast processor is a pretty exciting thing in itself, the question that arises is whether we really need it? For one, most of the time the processor is idle or uses only a little %age of its power for the very simple reason that we need only a little power of the processor for tasks like web surfing, etc. Games requires a bit more though. I can only see the utility of a super processor in high-end animations or computer modelling, etc and not every John and Jenny do that, I presume.

  105. 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.

    1. Re:Intel is to blame for this absurdity by Tumbleweed · · Score: 1

      Instead, their next gen processor is a 2ghz Pentuim M dothan.

      Well, the 765 is, I believe, a 2.1gHz part.

      I keep seeing people saying that the Pentium M will form the heart of the upcoming multi-core Pentium 4, and everything official or even semi-official that I've seen says this is not the case. Unfortunately.

      I'm an AMD fan, but I've gotta admit to being mightily impressed with the Pentium M design. I'd love a desktop version (add SSE3, on-die memory controller with higher FSB & faster memory interface), and hey, dual core while you're at it), but I don't see Intel moving towards this at all. Weird.

      I'm also hoping that IBM goes with an on-die memory controller for the PowerPC FX processors; it sure couldn't hurt!

    2. Re:Intel is to blame for this absurdity by eander315 · · Score: 1

      Well said. They've been using deceptive and monopolistic practices for years, but aside from a few poeple in the IT industry (and maybe high-end gamers), the computer-buying public has never noticed.

  106. Limits, Always by Muttonhead · · Score: 1

    I started with a 4.77mhz PC XT computer (Leading Edge) and years and years of PC Magazine subscriptions. They were always predicting the end of Moore's law. And they were always wrong.

  107. NIH = Bloat by k98sven · · Score: 1

    The algorithms chosen *are* important, and in some cases you shouldn't simply reach into the API toolbox and use the third-party solutions. There is no substitute for knowing how to write your own sort routines, specialized linked lists, and binary trees.

    However, this leads to people going too far in that direction as well, which is just as problematic. People re-invent the wheel for no better reason than that their own inflated egos make them believe they can do everything better. Or because the available routines differ in some completely insignificant respect from what they'd prefer.

    The result: Lots of programs duplicating effort, creating bloat. You have Gnome, KDE, Mozilla and OpenOffice all with their own set of widgets and APIs. It's fragmentation and duplication of effort for no good reason, and so the casual Linux (in this case) user ends up having to store all four of them in memory.

    I think that the Not Invented Here syndrome is a far more important factor in creating 'bloat' than people chosing inefficient algorithms.

  108. You obviously haven't studied geometry by Chemisor · · Score: 1

    > 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!

    True, but your thinking is just SO 2D! What we need is to make the L2 cache into a sphere and paint the CPU on the surface. Then you put the clock in the center, guaranteeing synchronization at every point. When are chip manufacturers going to leave Flatland?

    1. Re:You obviously haven't studied geometry by mikeee · · Score: 1

      A good idea, and more layers will happen, but

      a) fabrication is hard
      b) you still have the distance problem, you just got a one-time gain
      c) How are you going to remove the heat from the center of that sphere? You can reduce voltage, but that'll slow the signals down again...

    2. Re:You obviously haven't studied geometry by Chemisor · · Score: 1

      > a) fabrication is hard

      No it isn't. All you need to do is create your etching maps as projected on a sphere and illuminate the entire surface at once. I doubt it is any more difficult than doing it on a flat surface; just add more projectors and account for distortion at the surface. The etching process is exactly the same, since only the surface is etched.

      > b) you still have the distance problem, you just got a one-time gain

      The sphere gives you diametric connectivity, which will always be pi/2 times shorter than the surface distance. I think that's a pretty good gain. Furthermore, with the clock at the center, the propagation time becomes irrelevant, since you will no longer have to synchronize two different areas by surface transmission. This will allow the chip designer greater freedom of layout, since every point on the sphere is in synchrony with any other.

      > How are you going to remove the heat from the center of that sphere?

      You won't. You put cool curcuits in the center and hot circuits on the surface. This is possible because memory circuits, which should be in the center, generate less heat than the ALU circuits on the surface (this also allows equal memory latency for all parts of the CPU). Then you take the CPU ball and float it in a nonconductive coolant. Hey, if they can make a nuclear reactor work like this, how hard can it be for a CPU?

    3. Re:You obviously haven't studied geometry by 3x37 · · Score: 1
    4. Re:You obviously haven't studied geometry by HiThere · · Score: 1

      > How are you going to remove the heat from the
      > center of that sphere?

      You won't. You put cool curcuits in the center and hot circuits on the surface. This is possible because memory circuits, which should be in the center, generate less heat than the ALU circuits on the surface ...


      Yes you will. You remove the heat with silver or copper wires that connect to a heat-sink (probably indirectly). You don't need to remove as much heat, but you still want to remove it so the center doesn't get hotter than the surface.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    5. Re:You obviously haven't studied geometry by Chemisor · · Score: 1

      > but you still want to remove it so the center doesn't get hotter than the surface.

      Now this I don't understand. My DRAM chips are sitting in a case with relatively poor ventilation and are still managing to keep from overheating by simple air cooling, with no heat sink at all. Granted, heat retention will be greater inside the sphere, but with the CPU being immersed in an essentially bottomless heat sink in form of liquid coolant, I don't see how the circuits in the center could keep heating the sphere faster than the coolant can draw it away. Remember, even red-hot steel balls can be easily quenched in a barrel of water, and it only takes a second or two.

    6. Re:You obviously haven't studied geometry by HiThere · · Score: 1

      If you were to surround them with a hot spherical shell, then they would become HOTTER than the average temperature of that shell. Because they, themselves, are generating heat, but have no place to reradiate it.

      This is the basic reason that we don't currently use 3-D circuits. There are others, but managing heat is a hard problem.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  109. Resistance Capacitance Constants by Ironsides · · Score: 1

    Resistance and Capacitance becomes a problem at the higher switching rates and the longer distances. Capacitance over long pairs of wires creates cross talk between the two (one reason why power lines are croseed every now and then is to create some induction to offset this). Another is that the longer distances increase the resistance on the wires. This causes the recieved voltage to be lower and can sometimes be to low to trigger a voltage high reception. This can be offset by making the wires wider but is still a problem. A third is the combination of Resistance and Capacitance call an RC constant. This problem is basically that when you go from high to low or low to high signal propogation takes longer. Causing the recieving end to wait more until it can make sure that the incoming signal is either high or low.

    Take a basic AC electronics course and you should learn about most of these. Either that or a Digital Design (of Integrated Circuits) course.

    --
    Fly me to the moon Let me sing among those stars Let me see what spring is like On jupiter and mars
  110. Santa is creating a beowulf cluster by Anonymous Coward · · Score: 0

    Santa is creating a beowulf cluster of the 10Ghz machines up north. As it turns out he is a computer Geek too.

  111. Itanium - Itanic by CaptainPinko · · Score: 1

    The OS would do all the dirty work of breaking up your application into pieces that can run concurrently for you.
    and yet the Itanium is still stuggling. The only sin greater than underestimating the technology of the future is to overestimate it.

    --
    Your CPU is not doing anything else, at least do something.
  112. 7 year old hardware by JawzX · · Score: 1

    My main system will make many of you laugh, but here it is:

    Beige Mac G3 tower, upgraded to 733MHz G3(ZIF), overclocked system bus to 100MHz, 768MB Ram (PC100), Original 24x Apple CD-Rom, HP 12x6x32 CD-RW Drive. WDC 20GB EIDE, Maxtor 10GB EIDE, Belkin 4 port PCI USB card, Adaptec PCI Ultra SCSI card, 6x IBM 10000rpm Ultra-2 Mil-Spec 1GB drives (RAID), 3DFX Voodooo 5/5500 PCI Graphics Card, various scanners, printers, monitors (2), Wacom Pads.

    So there it is, the manufacture date on my CPU is 1997. So what do I do with this system? Graphic design, large format printing (Epson Stylus 10000), Digital art (Painter/Photoshop/Illustrator), Play the SIMS (all available expansion packs), Play Quake 3, etc etc... Probably most of what the average person does with a machine and more.

    Sure my Quake framerates never break 60, and I have to actually WAIT for a gausian blur on a 200MB image, and most annoyingly there is no support for my VooDoo 5 under OS-X, so I still run 9.2.1 most of the time. But the point here is that with well written software there are VERY few people who would actualy bennefit from a 10GHz processor. My computer does all I need it to, and I demand a fair ammount from it. Right now my only real reason to upgrade is either for more HD space or to be able to run OS-X with full Quartz acceleration.

    Please, I Laugh every time I hear some fellow MacHead whine about being stuck at 3.2GHz, I mean really, GET OVER IT!

    P.S. My linux machine is a hacked EyeOpener running Debian/Knoppix. It sits on my end table to surf the web and check e-mail. It has 128MB ram, a 4GB HD, and does everything it needs to.

  113. Not Everything Lends Itself To Concurrency by snookerdoodle · · Score: 1

    Folks (like me ;-) who spend their careers developing server-side software are going to (like me ;-) read this article and go, "Look, bozo, not every problem has concurrency!" or, "We're already doing that the best we can!".

    Mainframe developers (I'm not one) have wrestled with load balancing issues for, like, eons. Sometimes parallel processors help. Sometimes, the problems are some other system (e.g.: database I/O). I don't think it was fair to act like even most software developers have been depending on Moore's Law. Anyone running on the edge of their performance bandwidth eventually looks for ways to work on parts of their problem concurrently.

    Mark

    1. Re:Not Everything Lends Itself To Concurrency by OldCrasher · · Score: 1

      I was quite surprise in doing some OCCAM programming on Transputers, by the level to which you could turn processes into something that ran well concurrently.

      Part of the problem we have at the moment is that setting up threads, or forking, is a tedious business and prone to debugging hell. In OCCAM you could write your procedures and where and when you wanted them to run serially or in parallel, put a case statement like structure that was headed with SER or PAR.

      Seeing this, it was easy to think of new ways in which you could decompose existing problems and then parallel-ize them to make the most of the hardware.

  114. Thanks to AMD, no by gosand · · Score: 2, 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.


    Dude, that is what Intel was doing until AMD came along and forced them to get into this "keeping up with the Joneses" routine.


    I can't decide whether to put a smiley face on this or not. I was being sarcastic, but for all we know it might be partially true!

    --

    My beliefs do not require that you agree with them.

  115. Right.... by leerpm · · Score: 1

    You do realize who the author of the article is? Herb Sutter, he works on the C++ compiler team at Microsoft and IS THE CHAIR OF THE ISO C++ STANDARDS COMMITTEE.

    1. Re:Right.... by OldCrasher · · Score: 1

      C++ has been a pile of steaming crap for better than 10 years. Review the success of Java in the period. Cross refernece with the continued us of C to do most (non-windows) systems programming.

      As for the Author being the Chair of the standards committee, this just goes to prove we all make mistakes once in a while.

      - The IQ difference between a worm and a human is such that it allows the worm to burrow deeply and get out of trouble.

    2. Re:Right.... by CTho9305 · · Score: 1

      He could be the lead architect of the Pentium 4 for all I care - CPUs with precise interrupts (every one I can think of) execute programs as if they were in-order, unpipelined processors.

      The Tomasulo design, originally in an old IBM floating point unit, did not support precise interrupts, but modern designs use reorder buffers (the queues I described) to add that support. If the CPUs did not act this way, debugging even non-optimized software would be extraordinarily difficult (since you wouldn't know which instructions were partially complete), and when there were exceptions or interrupts, the CPU would have to keep track of a LOT of internal state in order to resume execution.

  116. How would you cool it? by Ayanami+Rei · · Score: 1

    Keep in mind chips these days have all the transistors "facing" up so they can be mated to a substrate that removes heat. Creating a sandwich of components is probably not a good idea unless you completely change the manufacturing process, using 3d "pathways" to conduct heat and signals in and out of the core. Quite a bit more difficult to model and produce.

    --
    THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
  117. Hyperthreading software by andyh · · Score: 1

    Where is it? I see lots of software that states it works with a hyperthreading capable operating system, in the Win XP world for instance, but I haven't seen any examples of software that clearly states that it is hyperthreading capable.

    Is this a case of the emperors new clothes or is my limited exposure to XP software making me look foolish?

    I did a google search and haven't found any software that clearly states it is hyperthreading capable other than XP itself. Anyone have a list?

    Andy

    1. Re:Hyperthreading software by nostromo.operator · · Score: 1

      adobe premire pro 1.5. it's pretty neat to see it read "dual processor detected" in my single 3.4ghz. but ah, ...thats about it.

  118. the Amiga philosophy by Tumbleweed · · Score: 1

    The Amiga philosphy of offloading to other processors is truth

    Interestingly, this predated the Amiga. Jay Minor's (father of the Amiga) project prior to the Amiga was the Atari 400/800, which used the same type of hardware design. Certainly the 800 had other design limitations which killed it in the end, but that aspect of it was way ahead of its time. I sure wish Jay was still around today; it'd be fascinating to see what he'd come up with by now. :(

    I miss my Guru Meditation Errors! :)

    1. Re:the Amiga philosophy by Duhavid · · Score: 1

      It isnt the Amiga philosophy so much as it is the mainframe philosophy. Distributed smarts out at the devices, main CPU not concerned with IO so much.

      --
      emt 377 emt 4
  119. Q: "Where's My 10 Ghz PC?" by Anonymous Coward · · Score: 0
    A: If it was up your ass, you'd know.

    Now go fuck yourself faggot.

  120. Concurrency Revolution is off to a slow start by Anonymous Coward · · Score: 0
    I've started the Atomic Ptr Plus project to collect some of lock-free stuff I've already done. There's nothing there yet, it's still in the planning and organization stage. Figuring out what opensource license to apply is a major pain. There's no real instructions on how to fill out th e boilerplate and how that works when derivative copies are made is a real pain. OSI isn't a big help here. I'm leaning towards the Historical License which pretty much lets you do anything with the software.

    The win32 stuff you see in the list might get dropped even though it's already written since it's not clear I will have long term resources to support it. Something about the 100's of dollars required to replace all your win32 software when moving to the current win32 or win64 platform.

  121. I have a 3.2GHz machine under my desk and even that was because Santa was grumpy when he delivered my stuff. You probably just forgot to leave Santa a bottle of whisky by the chimney. I'm not sure what the fastest PC around is, say 4GHz.

    Remember, growth of computing power is exponential and when comparing trends it often makes sense to switch to a logarithmic scale. log(10GHz/4GHz) isn't too much of a deviation from the trend.

    --
    Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
  122. computation vs mhz by rich42 · · Score: 1
    todays systems get a lot more per MHZ than those of 10 years ago. I'd venture to guess about double for a mainstream Pentium 4 vs a Pentium I. More in other cases.

    An extreme example would be the human brain - quite "slow" - but gets a lot done each "clock cycle"

  123. 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.
  124. Pick your PB reference. by Anonymous Coward · · Score: 0

    I don't think this article said what you think it said.

    - or -

    Truly, your intellect is dizzying.

  125. Good by MightyMartian · · Score: 1

    Here you go, here's your 100ghz Pentium, cooled to 40 degrees Kelvin. Yes, we know the case looks like a chest freezer and sounds like a horny sperm whale, but clock speed's what it's all about. Yes, we realize that your electricity bill will quadruple and that they'll have to build another diesel-burning power plant to keep all these fine machines, but on the plus side, you've got a place to keep your beer!

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  126. I dare to disagree. by hummassa · · Score: 1

    My laptop is a Transmeta 700 with 300MB RAM. XP on it is impossibly slow. 98 is acceptable. Linux is fast and responsive, with a lot of services on, kde 3.3. My wife has a desktop Athlon 450 with the same amount of RAM. it's slower than my laptop, even with 98 and nothing else running.

    --
    It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
    1. Re:I dare to disagree. by tomjen · · Score: 1

      I had a classmate who got 98 to run on a 468 (laptop bought for less than $100).

      But if you want to avoid bloat get freedos.

      --
      Freedom or George Bush
    2. Re:I dare to disagree. by Garak · · Score: 1

      Strange, I've found XP to be faster than Linux/KDE on my PII400 laptop with 128Megs of ram. Under linux stuff like scrolling webpage in firefox is rough while under XP it scrolls smoothly. Loading times around around same.

      As much as I'm not a MS fan windows XP outproforms linux on the desktop for most task. I've hated win9x and ME but MS really got their act together with 2000, XP and 2003. Except of course on the secuity side. On most machines XP is much faster than 98. There are alot of variables in the HW, some is better supported than others. Playing video under linux with a PII 400 is almost impossible while XP will do it.

      Now for servers I'll never trust a microsoft product.

      --
      God, root, what is the difference?
  127. Herb is a genius by PhilHibbs · · Score: 1

    Herb Sutter, the author of the article, is a voice worth respecting. He's chair of the C++ standards committee, and although he now works for Microsoft, he isn't actually evil. He's Canadian, for a start. He is also actively steering the Microsoft C++ compiler towards standards compliance, and he even managed to get a room full of C & C++ programmers to give a spontaneous round of applause to the guy that implemented partial specialisation in MSVC++. That was at the ACCU conference in 2003.

  128. Re:This guy is trying to bring it back! by tomjen · · Score: 1

    Dont click that link.

    --
    Freedom or George Bush
  129. Irrelevant but personally freaky by JoshNorton · · Score: 1

    Hub Finkelstein is (was, actually - he died last year) the landlord for my place of business.

    --
    "Stupid! Stupid stupid stupid stupid! I touched the hot wire right there - I'm an idiot!"
  130. optical connections by Anonymous Coward · · Score: 0

    if we havee optical for sound on some audiophiles stereo rig, why not in a 3000 dollar computer??

  131. 3x10^8 m/s - not just a good idea, it's the LAW! by Anonymous Coward · · Score: 0

    No, seriously.

    Light - and information - can travel no faster than 3x10^11 cm/s.

    Your typical processor chip is what, a couple of inches across? Let's round that off to 5 cm for ease of calculation. And do a thought experiment...

    Even if calculations are performed instantaneously, there's still the little matter of the result - information - travelling to the next portion of the chip for the next calculation. If you're using the entire chip to do calculations, that means you have to wait for the data to go from one side of the chip to the other. In other words, the information needs to travel a distance of 5 cm (again, assuming calculations take no time at all).

    Thus, the upper limit on processor speed in Hz is the time it takes for information to physically cross the processor... in this case, 3 x 10^11 cm/s divided by 5 cm or 6 x 10^10 Hz... that's 6 GHz for those of you keeping count at home.

    Obviously, calculations take slightly more time than 0, so that slows the processor down even more... which means that a 4 GHz processor is probably pushing the upper physical limits of a 5 cm processor.

    The challenge now is obvious... to get any significant increase in speed, we must find a way to make the processor physically smaller (thus decreasing the distance that information must travel). And that's no easy task! For instance, to increase speeds from 4 GHz to 10 GHz (as the submitter asked for) requires shrinking the processor from 5 cm in size to 2 cm in size.

    Obviously, the faster speed you seek, the smaller you have to compact the processor... the hypothetical 100 GHz processor can be no more than 0.3 cm in size based on the speed of light alone (again, assuming an ideal processor that performs calculations instantly)!

    *That's* why processor power is slowing down a bit compared to the old axe of "doubling every 18 months" - because we're running up the speed of light and we can't break it... and we can't shrink component sizes by half every 18 months, either!

    --AC

  132. Another Flawed Law. by twitter · · Score: 2, Insightful
    Quoth the author:

    ?Andy giveth, and Bill taketh away.?

    That's only half right, because you don't have to let Bill take away. KDE3 runs well on a 233MHz PII and 64MB of RAM, almost a whole order of magnitude less of hardware than it takes to make XP happy. The picture is more drastic when you consider the virus load most XP setups must endure. You need a 2GHz processor just to keep running while your computer serves out spam and kiddie porn.

    The changes Dr. Dobbs so wants are already happening in free software. There's a reason things like Arts can play music, games and system noises all at the same time while software on M$ has trouble sharing sound devices. If Beowulf is not a 10 year head start on concurrency, I don't know what is.

    Quoth SVDave:

    I don't predict good things for Microsoft. Longhorn in 2007, anyone?

    Perhaps old Billy should put his money into processor development instead of SCO and FUD.

    --

    Friends don't help friends install M$ junk.

  133. Appreciation for a change by Anonymous Coward · · Score: 0

    This is really one of the best articles I've read in a long time. My compliments to the author.

    My favourite bit:

    I will speculate that today's single-threaded applications as actually used in the field could actually see a performance boost for most users by going to a dual-core chip, not because the extra core is actually doing anything useful, but because it is running the adware and spyware that infest many users' systems and are otherwise slowing down the single CPU that user has today. I leave it up to you to decide whether adding a CPU to run your spyware is the best solution to that problem.

  134. Re:TFA's author doesn't know what he's talking abo by PylonHead · · Score: 1

    Yes. This is exactly what I was thinking as I read that part of the article.

    My first thought was that the author had confused the optimization settings of his compiler with the in chip reordering that the processor was doing.

    --
    # (/.);;
    - : float -> float -> float =
  135. Re:3x10^8 m/s - not just a good idea, it's the LAW by Anonymous Coward · · Score: 0

    As a side note to the above, it's also why "three-dimensional" computer chips are of such interest - because you can fit more processors into the three-dimensional space that light can cross in a given amount of time, thus giving you the potential to do more calculations - or alternatively, being able to fit the same amount of processors in a smaller radius than in two dimensions (and not having to simply "shrink down" a two-dimensional circuit board). But again, the size limit comes into play because information can only move so fast.

    --AC (the same as above)

  136. Re:Asymptotic stanislaw obviate by Zoinks · · Score: 0, Redundant

    1) Make impact by thinking out of the box
    2) Leverage paradigm shift
    3) ????
    4) Profit!!!

  137. Time for software to go on a diet by gvc · · Score: 1
    As the article points out, increased processor power has been eaten by increased software bloat. Windows machines (and X11 machines) are as slow now as they've ever been.

    I'm not speaking of bleeding-edge applications, I speaking of how long it takes a menu to appear after you hit START, or how long it takes to open an editor for a simple text file.

    About a dozen years ago, a PC hacker laughed at my Unix box because there was a noticeable lag between touching a key and getting a response. He can laugh no longer. Unix systems aren't any better, but PCs have become dogs.

    But there is hope. If we put nearly as much intellectual energy into making software more efficient, perhaps we could actually harness the couple of orders-of-magnitude improvement in processor power that has occurred in the last dozen years.

    The processor designers have spent their energy making a well defined set of operations (with minor enhancements) run faster. The software designers have instead spent their energies making the core operations slower in support of more and more (dis?)functionality.

    1. Re:Time for software to go on a diet by EllF · · Score: 1

      I don't know, dawg. Vim opens pretty fucking quickly on my 2ghz laptop.

      --
      We who were living are now dying
      With a little patience
  138. Simple explanation of signal speed by elgatozorbas · · Score: 1
    Electromagnetical phenomena travel at the speed of light, which is equal to 1/sqrt((epsilon x mu)), with epsilon and mu material constants of the surrounding material.
    In vacuum (and approx also air) this is 3e8m/s. To compare other material parameters an epsilon_r and mu_r are defined, relative to those of vacuum.
    Most other materials have a mu_r=1 (except ferrites etc), but an eps_r which can be very different. For silicon this eps_r is about 12, therefore the speed of light/electrical signals in silicon is sqrt(12)=3.5 times lower than in air.

    When the distance traveled becomes of the order of magnetude of the wavelength things can become problematic. For a 3GHz processor this is about 3.10^8/3.10^9/3.5=0.03m, or 3 cms. This effect will soon start to play. Another problem would be race conditions, i.e. different signals should moreless take equally long to reach their destination or you get into trouble.
    All of this a bit intuitive, hope anyone will correct possible mistakes, I am no expert in semiconductor technology...

    Z

    1. Re:Simple explanation of signal speed by ChrisMaple · · Score: 1

      We're not interested in eps_r in silicon when we're talking about signals going "long" distances in an IC. The relevant eps_r is that for silicon dioxide, which is 3.9.

      --
      Contribute to civilization: ari.aynrand.org/donate
  139. You obviously haven't studied chip design by Anonymous Coward · · Score: 0

    How do you deposit another fresh layer of uncorrupted substrate on top of a processed layer?

    Chemical vapor deposition? It's not as easy as it sounds.

    What about thermal expansion/contraction, thermal effects on timing, IR drop of a sandwich layer of substrate-oxide-metal-oxide-substrate-oxide-metal?

    How do you analyze process defects on the lower layers?

    And a host of other properties.
    If you want to do 3D, just make alot of chips and stack them together. That's the easiest way right now.

    1. Re:You obviously haven't studied chip design by Chemisor · · Score: 2, Interesting

      > You obviously haven't studied chip design

      Perhaps that's why I am able to come up with a novel idea? Because nobody told me it's impossible, it just might work. But, of course, I welcome constructive criticism.

      > How do you deposit another fresh layer of
      > uncorrupted substrate on top of a processed layer?

      With this technology it is already possible to do exactly that. It just needs a bigger nozzle.

      > Chemical vapor deposition? It's not as easy as it sounds.

      Neither was putting the man on the moon. But we did it anyway. Sure there will be engineering challenges here, but I see no theoretical problems with using CVD for this.

      > What about thermal expansion/contraction?

      Thermal effects in the sphere are no different from the ones in a flat plate. Also, there have been recent advances in painting transistors on flexible substrates, which could help on the surface layers.

      > thermal effects on timing

      How will they be any different from the ones in a flat CPU? Besides, you need to remember that with the clock in the center, timing is going to be far easier to implement.

      > IR drop of a sandwich layer of
      > substrate-oxide-metal-oxide-substrate-oxide-metal?

      Perhaps you could explain this problem to those of us who don't understand the reference?

      > How do you analyze process defects on the lower layers?

      Just as you analyze process defects on flat CPUs: by testing them. I don't think chip manufacturers actually look at each chip under the microscope to see if something went wrong.

      > If you want to do 3D, just make alot of chips and stack them together.

      I don't see how that helps with anything. If you have flat chips anyway, why not just spread them out?

    2. Re:You obviously haven't studied chip design by HiThere · · Score: 1

      > If you want to do 3D, just make alot of chips and stack them together.

      I don't see how that helps with anything. If you have flat chips anyway, why not just spread them out?


      It helps because it allows the communication paths to be shorter. There are lots of hard problems involved, but it's clearly the way to go, and we are already the first steps along the way. (Actually, the first steps along the way were the v-groove chips, I forget what they were called, that put the layers of the chips diagonally on the surface, so that transistors could be packed closer together. 1970's or 80's)

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    3. Re:You obviously haven't studied chip design by Anonymous Coward · · Score: 0

      No no no.... putting several men on the moon is nothing compared to the feat of building a high speed chip that works reliably and can be cheaply mass produced by the tens of millions (and yes I've done exactly that; I do know what I'm talking about).

      Building another substrate layer is not easy. You don't just spray silicon like a coat of paint! You need a perfect (~99.9999999999%) pure crystal. You would need to grow another layer of silicon crystal on top of a processed layer (including metal). Some people have tried this, but it is still has major issues. Simply put, that's why no one's doing it right now.

      There are serious thermal issues. When you sandwich together different materials there is serious risk of cracking over time as they heat up and cool down. We face this problem already in flip chip packaging, but now you want to add another layer of devices to it. You might get away with it, though. At least the silicon would expand together with the silicon, but the metal does not.

      As for "clock in the center" what do you think chips do already? We already do careful clock tree synthesis. You have to to minimize skew. But how do you think timing will be impacted if one layer is typically hotter than another? (Remember, heat dissipation is not uniform on both sides!)

      How do you connect both layers together? You would need to grow metal posts *through* the new substrate layer. You can imagine the chaos this would add. Again, think of building a perfect crystal, thermal properties, etc.

      How is signal integrity impacted?

      How do you supply enough power? That's what I mean by IR drop. IR drop is now a serious problem with 1 power grid as it is. How do you propose to power the second as well?

      "I don't think chip manufacturers actually look at each chip under the microscope to see if something went wrong."

      OH YES THEY DO! Every fab invests in electron microscopes for this very reason. When something goes wrong and an entire batch of wafers is destroyed (at millions of dollars in cost) you better believe they will analyze every last detail. underetching. overetching. oxidation. (yes it happens on metal alloys sometimes) reticle defects. dust on the reticle. electromigration failures.

      Sometimes people even spend rediculous sums to laser fix a particular wire in a chip to see if their proposed solution to a problem will work, though this is less feasible these days on flip chips.

    4. Re:You obviously haven't studied chip design by Chemisor · · Score: 1

      > You don't just spray silicon like a coat of paint!
      > You need a perfect (~99.9999999999%) pure crystal.

      Well, no, you don't. You just need pure crystals in the spots where the transistors are supposed to be. Perhaps it would be easier to create a grid of small pure crystals instead of a single perfect one. In fact, how about growing them chemically and then painting them on? You could even have P and N crystals made separately. I am not sure how to go about connecting them (monolayer deposition followed by CVD to fill the gaps perhaps?), but I think something like this could warrant some consideration.

      > When you sandwich together different materials there
      > is serious risk of cracking over time as they heat up and cool down.

      How about pre-cracking them then? Build in natural fault lines into the circuits and let them break, leaving the pieces connected with stretchable metal wires.

      > But how do you think timing will be impacted if one layer is typically hotter than another?

      But you will know about this situation at design time. At steady state the temperature gradient is constant, and with proper cooling should remaing that way. In fact, it would be more stable than in a flat circuit because of the ball's greater thermal mass.

      > How do you connect both layers together? You would
      > need to grow metal posts *through* the new substrate layer.

      No, you would grow the metal posts *while* you grow the substrate layer. Masking and etching should work just fine as long as the posts are wide enough to not suffer greatly from misalignment. You can also do inductive coupling.

      > How is signal integrity impacted?

      Why would it be? Signals travel on a spherical surface as easily as on a flat one. Look at Earth.

      > How do you supply enough power?

      Radially. Because the radial connections must already be thicker, they would offer a lower voltage drop, and by being able to route power directly to any point on the sphere you would be able to reduce the length of the power lines in the circuit.

      > When something goes wrong and an entire batch of wafers
      > is destroyed (at millions of dollars in cost)

      And that's another problem. Shouldn't they be thinking really hard about how to make the process cheaper? Take a look at Ball Semiconductor, for instance. They claim a 5 day turnaround time! If you could do that with your bad chips, perhaps you wouldn't spend too much time "laser fixing" a particular bad wire. It would cost less to just restart the process.

  140. Applications != System by angel'o'sphere · · Score: 1

    The problem with that guy is he is allways talking about applications.

    We all know a dual core CPU is not really twice as fast than a single core one. We all also know that an application is not necessarily twice as fast if it runs on a dual core or dual ship system.

    But thats not the point.

    Most of us run a system where ALLWAYS more than one thread is ready to be executed. More than one thread from different applications of course.

    The overall system can easily be nearly twice as fast (199%) with a dual core chip. As soon as the chip internal communication restrictions hit it from being truly twice as fast.

    E.G. my mail programming waking up and accessing my mail box while I listen to a song on iTunes and type this posting can easy run on the second core without slowing down the other core besides concurring about the memory bandwith.

    angel'o'sphere

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  141. Dr Dobbs/wikipedia by psmurf · · Score: 1

    I can't believe a respectable publication like Dr. Dobbs is citing Wikipedia as a source in this article...

    1. Re:Dr Dobbs/wikipedia by Anonymous Coward · · Score: 0

      I think that's awesome. Go Wikipedia!

  142. Less of "A Good Thing?" by ClayJar · · Score: 1

    If processor technology does indeed plateau, perhaps there would be hope for what the parent suggests. However, if we were to treat the English language and the brain as an example of code and fairly static processor power, we could use the post as an example of a simple application (more like a shell script than emacs, but an example nonetheless).

    Consider the following paraphrase:

    It _might_ be good if the rampant speed advance slowed significantly.

    Consider:

    Some may return to witing efficient code instead of writing anyhow and adding hardware until it runs acceptably. (Microsoft: I'm looking at you!)

    Desktop machines might _not_ become obsolete in under two years and might continue to be useful as more than just a router.

    Processor designers might spend more time creating innovative new ideas instead of raising clock speeds.

    Cooling and quieting technology might even have a chance to catch up with heat output.

    (Finally, my wild dream: Game writers might remember gameplay, not just better coloured lighting.)

    That's a character savings of approximately 25%. Obviously, there is good reason for the lack of optimization in the original parent post. It would not be worth the time and effort to optimise such a trivial bit of English code. If it were a manuscript for a techical manual (more like emacs than like a shell script), more optimizations would like be done.

    Programming parallels language usage. There will always be some who optimise to the Nth degree. In programming, these people sometimes make demos and kernels and clean, nice libraries; in language, they tend to be poets and lawyers and grammar nazis. There will be others who write large quantities of clean, but not hyper-optimized code. These are the application programmers and general writers. Then there will be the great, unwashed masses. Outside of programming, they either don't write more than an occasional postcard, or they write terrible fanfic. In programming, the postcards are quick-and-dirty shell scripts and utilities, and the terrible fanfic includes most of Microsoft (ever notice how they're always the main character in their software?).

    Anyway, the analogy is strained and breaks down easily, but it fun to just sit back and take a thought at it once in a while. It may be that we will get more efficient coders out of a slower processing environment, but then again, it could just mean that we end up with a lot more fanfic-quality applications that make the well-written code stand out as an enjoyable and welcome group.

  143. Computers are Fast Enough (For Now) by thelizman · · Score: 1

    Can anyone honestly say that todays top of the line computer is not enough (in practical terms)? Computer development usually lags behind software, but we have reached the point in the last three years where processors outpace the demands of software. The top of the line consumer level computer today (say, an Alienware ALX?) is roughly equivalent to a few hundred Pentium 133's from just a decade ago. Most apps today claim to run on hardware as slow as a PII-233, and most games will run on a 1 Ghz Athlon with 512 mb of RAM.

    Concurrency is just another buzzword. What we are going to find now that we've hit a glass ceiling on processor clockss is that we need to look at how our needs are changing. You don't need a super fast processor to run a PVR, play MP3's, run your cars engine, or to manage your to-do list. Any decent computer nerd can automate his entire house with an old windows machine. In terms of using computers to improve the standard of living, keep us entertained, and to advance civilization, we're nowhere near the limits just because we topped out on absolute processor clock speed. There are still factors which determine a processors power, and more importantly the processor itself is only one small part of the overall computing devices which we utilize.

    In the future, as our needs grow and change, so will the manner in which we implement technology. I'm willing to bet that 20 years from now nobody will care how fast their computer's clock can cycle.

    1. Re:Computers are Fast Enough (For Now) by OldCrasher · · Score: 1

      I dunno! I think your Pentium 133 is running slower than most. If todays 'average' PC is a 3GHz screamer that would make your new machine 22 times faster than the old Pentium 133 paper weight.

      There has been some improvement in how fast a single instruction operates on the latest Intel chip generations but nothing to get you being 'a few hundred' times quicker.

      The Athlons are a different game, AMD did tweak the instruction set to run faster, hence their nominal speed ratings are very different from their actual speed ratings. The nominal rating is what an Intel chip would (surely) have to be clocked at to achieve the throughput. But still not to achieves hundreds of times the performance.

      Personally, I need all the speed I can get. I need to get into the top 2 percentile of all Seti@home users... NOW!!! And that means Powwa!! Quad-10GHz processors... mummm!

    2. Re:Computers are Fast Enough (For Now) by fienna · · Score: 1

      hahaha - top 2%??? i'm gunning for top 0.5% seti@home user: fienna@nac.net Your rank out of 5313881 total users is: 28131st place. The number of users who have this rank: 1 You have completed more work units than 99.471% of our users. i should hit 10,000 units in about a month...

      --
      /not so /obvious
  144. Company Silicon Pipe susposedly solves this... by voxel · · Score: 0

    http://sipipe.com

    Transfer 20-25Gb/s from chip to chip easily, and 1-Gb/s per channel (wire/copper).

    --
    Modesty is one of life's greatest attributes
  145. Re:bloatware by Migraineman · · Score: 1

    Your comment makes me thing you've done embedded software development. I'm currently turning up some new hardware, and I'm disgusted by the software IDE. The "hello world" demo program compiled, with full optimization, to just over 65k of code. Yelchkk. I ended up writing a complete console monitor program, complete with initialization, in assembly in just under 4k bytes.

    The current mentality of "abstraction from the hardware layer" allows software folks to write code without knowledge of the underlying hardware, but the penalties are code bloat and an ever increasing appetite for cpu cycles. So while the cpu speeds keep increasing, the code performance stays about the same as more layers of abstraction are spackled on top. I have complete faith that someone will build an abstraction layer that allows a GHz SMP machine to run legacy single-thread code with the perfomance of a Pentium 2 366. And then the complaining about "we need better hardware" will continue ...

  146. Dual 4 by TibbonZero · · Score: 1

    I've told myself, that once they hit Dual 4.0ghz ones, i'll sell/trash/retire my 1.25DP MDD and go get a fulled loaded 4.0DP.
    And maybe a 30" screen to boot!

    --
    Tibbon
    tibbon.com
  147. Obligatory Simpsons Quote: by Gadgetfreak · · Score: 1

    Krusty: So he's proactive, huh?

    Lady: Oh, God, yes. We're talking about a totally outrageous paradigm.

    Meyer: Excuse me, but "proactive" and "paradigm"? Aren't these just
    buzzwords that dumb people use to sound important?
    [backpedaling] Not that I'm accusing you of anything like that.
    [pause] I'm fired, aren't I?

    Myers: Oh, yes.

    --
    "No fair, you changed the outcome by measuring it!" - Professor Hubert J. Farnsworth
  148. This ought to be awful... by hummassa · · Score: 1

    My wife has an antique Compaq 486 DX2/66 with 8MB RAM (I bought it to her when she entered her office as a DA, ten years ago). It runs 95 + Works 95 (It originally ran Win 3.11 but I upgraded it). No browser, no dial-up network. It's barely acceptable. It is in her office now, but I intend to get it back and make it run some LTSP client.

    --
    It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
  149. Still Asymptotic by abb3w · · Score: 1
    True we have found limits to materials hence we need to think out of the box and find new materials.

    They're working on it, and progress will be made as a result, but the difficulty finding such is the reason CPU speed increases have slowed. I expect that there may be one more breakthrough in my lifetime allowing another factor of 10 Moore's law style increase in single CPU speed with an 18-30 month doubling period. One. After that, we need to go *MP-- and probably before that, too.

    And, kook that I am ("Energy Profit Ratio!" "Hubbert Peak!" "Club of Rome Report!"), I suspect the energy demands of the increased speed CPUs may render them uneconomical outside of the most limited high-end demanding server applications.

    --
    //Information does not want to be free; it wants to breed.
  150. Lose the e-'s by severoon · · Score: 1

    The problem is electricity. If you have an electrical junction, current must flow through it as if at a stop light--one pathway goes while all other wait. This is the cause of 99.999% of waiting for stuff in a computer to happen. Light, on the other hand, does not have to wait for other light. Light beams simply pass right on through each other and keep on keepin' on. Furthermore, two light beams can interfere on a sensor in all sorts of complicated ways to convey all sorts of complicated information--one light pulse can convey one bit of information, but two can convey 4 or more, and so on.

    Optical computing, when it finally gets here, will provide so much computing power it will not be consumable, even by Bill.

    --
    but have you considered the following argument: shut up.
  151. I think you are getting a few things mixed up here by cybergrue · · Score: 1
    For one thing, the speed of light is finite, and at GHz speeds, becomes really small; something close to 10cm at 3Ghz (meaning that light will travel just under 10cm in one clock cycle at 3Ghz, that's about 4 inches). When traveling through a medium other then a pure vacuum, electrons and photons will travel at a slower speed still. That means that if we ever got a chip or wire transferring data at 20Ghz, the information will only travel about 1cm in a clock cycle. An aside. It has recently been proven that although it may be possible to send a signal faster then the speed of light (using quantum mechanics under strict laboratory conditions), the transfer of meaningful information is limited by the speed of light.

    Also, the idle time may be technically correct, however most modern processors use pipelining to overcome this. Pipelining is sort of like an assembly line for instructions in that instructions are queued in the processor. Say it takes 3 clock cycles to get the data for the instruction. A simple way to make the processor more efficient is to check what data an instruction needs when it enters the instruction queue, and hope that the data is loaded when the instruction gets executed a few cycles later. While that instruction is waiting, three or more instructions that are ahead in the same queue are executed. A pipeline stall occurs when something goes wrong with this process; either the data takes longer to load then was expected, or the queue empties. There was an artile on the Ars Technica web site a while back that explained pipeling in detail and better then I can.

  152. 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.

    1. Re:Actually, 56k is the hard limit by Anonymous Coward · · Score: 0

      Get a clue man. It's still not the "limit of copper". It's the limit of the protocol we speak over the copper lines.

    2. Re:Actually, 56k is the hard limit by Anonymous Coward · · Score: 0

      "That's why with ISDN there is talk of B and D channels."

      Strange, I needed cable to get the B&D channel.

      Oh, wait...

    3. Re:Actually, 56k is the hard limit by swordfishBob · · Score: 1

      Not sure about some of the international gear, but basic rate ISDN (2x64 + 16) in Australia is actually provisioned using a 192kbps bearer (as is frame relay for speeds up to 128k).

      --
      -- All your bass are below two Hz
  153. Hertz don't put you in no drivers seat by fm6 · · Score: 1
    What I find interesting is that supercomputer makers like SGI have been lagging on the hertz wars for years. They seem to find it more productive to focus on increasing their ability to do parallelism than on making individual processors faster.

    Another example of why processor speed isn't everything: my home system is a 1.1 gigahertz monster, designed as a server. Not the fastest system around, but close enough. But it doesn't really play AM's Alice very well, and if I want to run GTA3 at all, I'd need to spend a few bucks on a better video card. I'd sort of like to play Sims 2, but the necessary video card would cost more than I spent for the whole system. I'll never want to play it that badly.

    As long as I can remember, people have obsessed about processor speed, not realizing how little effect this has on most apps. (The big bottleneck most people face is RAM; retail economics result in most systems being shipped without enough.) Nowadays, nobody needs more than a couple hundred megahertz, unless they're running something really graphics intensive. And even there, the specialized hardware between your monitor and the rest of the system does most of the work -- I doubt that Sims 2 would run any better on your hypothetical 10 gighertz system.

    1. Re:Hertz don't put you in no drivers seat by Garak · · Score: 1

      Yea you hit the nail on the head here.

      The bottle necks in computing lately haven't been the CPU but the RAM and HD access. The CPU is running at like 4 GHz but its accessing upto 66Mhz PCI bus and up to a ~1Ghz memory bus... Now with the latest chipsets and processors they are improvingt the memory side of thing using wider memory buses and dual channel. Why don't they make multichannel boards? Need a fast machine? Pop in a few cheap 256meg dimms...

      Another thing I would like to see them do is to put more than one die in a package so 128megs of cache or high speed ram would be pratical. While we are on this subject why not put the full system in one package hardwired together in one epoxy package. Would make cooling simpler, one big heatsink for video, processor and ram.

      We don't need faster clocks speeds, we need wider buses(Athalon 64), faster ram(multichannel?) and more intergration(keeps cost low).

      In the mean while I'd love to get a cheap motherboard with more than 3 ram slots.(I know power is a problem with alot of ram)

      Another beef is why they still have parallel, RS-232 and PS2 ports on monther boards. USB has finaly reached its potential, lets do away with all the legacy crap, there's lots of adapters on the market for people wanting to use their old stuff. Same goes for PATA, SATA is getting cheap now dump the old crap. This will free up lots of board space so they can make smaller motherboards or add more slots..

      [/rant]

      --
      God, root, what is the difference?
    2. Re:Hertz don't put you in no drivers seat by fm6 · · Score: 2, Interesting
      Another beef is why they still have parallel, RS-232 and PS2 ports on monther boards. USB has finaly reached its potential, lets do away with all the legacy crap, there's lots of adapters on the market for people wanting to use their old stuff.
      I think designers had the same idea a couple of years ago: you saw a lot of "legacy-free" systems with an emphasis on cheapness and tiny form factor.

      But they didn't catch on for one simple reason: motherboards are a commodity. The pressure on price is enormous, so the only way you can turn a profit making them is to make a lot of identical motherboards, so you don't spend a lot of money on multiple assembly lines, or on retooling the lines you have between runs. So your cheap motherboards are a one-size-fits-all design -- and that means legacy ports.

    3. Re:Hertz don't put you in no drivers seat by evilviper · · Score: 1
      The bottle necks in computing lately haven't been the CPU but the RAM and HD access.

      On the contrary, they aren't the ONLY bottlenecks anymore, but they are still significant bottlenecks in many areas.

      There are many times I wished my CPU and/or HDD could be magically faster (never RAM, though).

      but its accessing upto 66Mhz PCI bus

      Has that EVER been a problem for you? Even HDTV, gigabit ethernet, etc., doesn't saturate a PCI bus. I would like to see PCI replaced in the near future, but for the new potential uses, not because it's currently a bottleneck for anything I've used it for.

      Another beef is why they still have parallel, RS-232 and PS2 ports on monther boards.

      First of all, I would like to say that USB is flaky. My keyboard is one thing I would much prefer is NOT dependant on the USB bus.

      RS-232 is still used for headless access. There isn't yet a standard for console access via USB or any other interface, and USB isn't well suited for the task anyhow. USB-RS232 adapters don't work if they are needed before the kernel has even booted.

      An adapter would work for my parallel port devices, but since USB to Parallel adapters cost more than the motherboards I buy, I'd rather spend $1 more on a motherboard that has a built-in parallel port. PCI parallel port cards aren't quite as expensive, but the issue is the same.

      Same goes for IDE... Sure I COULD buy an adapter, or a PCI IDE card, but I'd be better served by buying a system (for a dollar more) with an IDE interface. It's still plenty fast, and it's too soon to say that SATA is actually going to catch on, anyhow.

      Personally, I think a forward-looking company should dump everything you mentioned, and dump USB and Serial-ATA as well. Then, have the entire system based around Firewire.

      Firewire hard drives/DVD Drives. Firewire printers/scanners. Firewire everything. Then you are really reducing costs, eliminating everything legacy, and standarizing on one interface all around. Not to mention that devices could be used insternally or externally, without any modifications. No need for power connectors for every device either. You could have your computer in a closet, and run just one or two wires from it, to your desk. Really amazing things then become possible.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  154. Binary by Anonymous Coward · · Score: 0

    Fortunately, if you convert your current processor speed to binary you'll find you have that 10 ghz machine you are looking for

  155. Cell by Anonymous Coward · · Score: 0

    Seeing as the cell is going to (supposedly) be capable of 2 Teraflops as a 64-bit core chip, I'd say we're not too far off.
    By the way, I don't know what I'm talking about.

  156. BTW How fast can you flip bits without blinking? by cabazorro · · Score: 1

    How fast can you flip bits without blinking?

    The confluence of physics and information theory flows form the central maxim of quantum mechanics:at bottom, nature is discrete. A physical system can be described usinfg a FINITE number of bits. Each particle in the system acts like the logic gate of a computer.Its spin "axis" can point in one of two directions, therby encoding a bit, and can flip over, thereby performing a simple computational operation.
    The system is also discrete in time. It takes a minimumn amount of time to flip a bit. The exact amount is given by the theorem named after two pioneers of the physics of information processing, Norman Margolus of MIT and Lev Levitin of BU. This theorem is related ot the Heisenber uncertainty principle, which describes the inherent trad-offs in measuring physical quantities, such as position and momentum or time and energy.
    The theorem says that the time it takes to flip a bit, t, depends on the amount of energy you apply, E.
    The more energy you apply,the shorter the time can be. Mathematically, the rule is
    t>= h/4E
    where h is the Planck's constant, the main parameter of quantum theory.
    For example, one type of experimental quantum computer stores bits on protons and uses magnetic fields to flip them. The operations take place in the minimum time allowed by the Margolus-Levitin theorem.
    From this theorem, a huge variety of conclusions can be drawn, from the limits on the geometry of spacetime to the computational capacity of the universe as a whole.

    Quantum mechanics predicts that spactime is discrete. Distance and intervals cannot be measured to INFINITE precision; on small scales, spacetime is bubbly and foamy. The maximum ammount of information (matter) that can be put into a region of space depends on how small the bits are, and the CANNOT be smaller than foamy cells.

    Physicists have long assumed that the size of this cells is the Planck lenght (lp) of 10E-35 meter, which is the distance at wich both quantum fluctuations and gravitational effects are important. If so, the foamy nature of spacetime will always be too minisucle to observe.

    Seth Lloy and Y.Jack NG
    excerpt taken from Scientific Amercian Nov 2004
    Black Hole Computers.

    --
    - these are not the droids you are looking for -
  157. Re:Asymptotic (OT) by gentgeen · · Score: 1
    Linux is like a teepee. It has no windows, no gates, and there's an Apache inside.

    Cute signature, but incorrect. Apache Indians are a member of the "Southwestern Tribes" (A term applied by white scholars, not the tribes themselves), and the Southwestern tribes did not have enough skins to create TeePees (TeePees have a lot of wasted space, as far as construction material are concerned). The Apache lived in homes called WikiUps. They were dome shaped (like an igloo) and usually covered with bark, sicks, mud, and sometimes hides.

    It just drives me nuts when people (not nec. parent poster) have this Indian/TeePee connection. The Native American cultures are just like the "Native European" cultures. Yes the are all "white", but you have german, english, russian, etc. Not all "red" indian cultures are the same.

    Sorry, I'll step off my soap box now :-)

  158. Screw GHz by Anonymous Coward · · Score: 0

    I'm still running a P3@500Mhz (with Suse Linux) and it works great. Sure it's not my everyday production machine, but for most things 'normal' users do, it would do just fine.

  159. Plank Limit by Saint+Stephen · · Score: 1

    I once did a calculation of how quickly my PC could add up floating point 1.1 a billion times, and using Moore's Law realized that we'd hit Plank Time for the communication of information in about 150 years.

  160. Sorry... by Junior+J.+Junior+III · · Score: 1

    I accidentally ran over your 10GHz PC with my flying car.

    --
    You see? You see? Your stupid minds! Stupid! Stupid!
  161. Re:Asymptotic (OT) (Way out there in Left field) by Anonymous Coward · · Score: 0

    All you pale faces look the same to me so you all must be the same.

  162. Where did all the cycles go? by Anonymous Coward · · Score: 0

    20 years ago my 1MHz C64 could do some pretty neat things and was adequate for most tasks. Now machines are more than 3000X faster, have more than 1000x memory, and something like 1000000x storage. Have we really gained much?

    1. Re:Where did all the cycles go? by tarpitcod · · Score: 1

      One word - Abstraction.
      A modern machine does much more than the old C64 (I'm an Atari 8 bit and Ohio Scientific Challenger owner myself)..
      Those early machines weren't doing nearly as much as a modern PC is. It's still a valid point however. We have decided we would rather live in a world of abstracted API layer after layer, and we pay for it dearly. The flip side of the coin is that a good API allows us to run our software on many different machines. When the API is poor then you end up with a software mono-culture.

      The AMIGA is an excellent example of a machine that had tight hardware/software synergy. Similar time frame PC's were laughable compared to the AMIGA, but who won? It's because eventually you could upgrade them, you could change them. Mediocrity with expandability works.

  163. They're coming by GrinFranklin · · Score: 1

    I cut a picture out of one of the industry magazines a year or two ago. It showed the prototype of the machines they are building that will allow building the next generation chips...and yes...it mentioned speeds over 10ghz.
    If the machines to build the chips aren't even built yet, we'll have to wait a while for the next step.

  164. Concurent Programming by Detritus · · Score: 1
    I read Per Brinch Hansen's excellent book on Concurrent Pascal about 25 years ago. Where are the software tools for concurrent programming? (Insert sound of crickets chirping)

    I've done a lot of real-time embedded system programming with multiple tasks, interrupt service routines, etc. I've yet to use a compiler/language that made any attempt at making concurrent programming easier for the programmer. If I need something, I have to do it myself. It's sort of like doing OOP in C.

    --
    Mea navis aericumbens anguillis abundat
    1. Re:Concurent Programming by tarpitcod · · Score: 1

      Very true, Anybody remember Algol 68. It had the idea of coroutines in there too.

    2. Re:Concurent Programming by Anonymous Coward · · Score: 0
      erlang

      Erlang is characterized by the following features:
      • Concurrency
      • Distribution
      • Robustness
      • Soft real-time
      • Hot code upgrade
      • Incremental code loading
      • External interfaces
      People are working on some cool projects, web servers, SMPP, XMPP, Python bindings, spread bindings, SIP and VoIP stuff, etc.
  165. Light speed by SilverspurG · · Score: 1

    After all, Moore's Law predicts exponential growth, and clearly exponential growth can't continue forever before we reach hard physical limits; light isn't getting any faster. The growth must eventually slow down and even end

    If we measure the speed of light in terms of feet per second as opposed to the more commonly known kilometers per second, the multiplier will yield a number which is greater (ignoring units). This will be good enough for the people in marketing and the salesmen at the major electronics outlets.

    Similarly the onus will no longer be on the programmers or engineers to produce faster, more efficient, or more capable products. Businessmen, investors, and executives being what they are they will simply pressure the marketing department to produce more glitz and glam. Was the onus ever really on them? That's arguable. The size of programs has increased to the point where even a simple word processor wouldn't fit on a hard drive of 10 years ago, yet are the word processors of today helping us to write better letters? For all the extra horsepower and storage space we still do (mainly): e-mail, surf web, print pictures, play games. The only people who have a significantly improved computing experience are those who no longer have to wait 18 hours for the graphical rendering, mathematical modeling, or compilation to finish.

    Intel has already shown us the way of advertising. Those three blue guys who are always doing some really neat stuff like taking off with rocket jetpacks or surfing around on anti-gravity boards. What does that have to do with processor capability, quality, or reliability? Nothing. At least automakers genuinely show a car in use doing something that a car does. When's the last time your processor caused you to physically fly to work?

    --
    fast as fast can be. you'll never catch me.
  166. Concurrent Desktop Software by MasterVidBoi · · Score: 1

    If desktop machines move towards concurrency, it could really give Apple a significant performance advantage.

    Apple's performance problems truly began when Motorola proved incapable of getting the G4's clockspeeds to scale. They compensated by making the Powermac a largely dual processor line. This move was, of course, laughed at because of the absolutely terrible software support. At the time, Photoshop was really the only app that could use that processor, not even OS 9 really worked with it. This was the classic desktop dual-processor chicken-and-egg problem. No one wrote software, because no one had the hardware. Apple hinged the product's success on people being willing to buy the machine knowing that the second processor wouldn't do much until OS X finally shipped.

    So now we find ourselves 5-6 years later.

    The chicken-and-egg problem has largely solved itself. One part magically appeared, and given enough time, the other followed. An incredible amount of desktop software on OS X is multi-threaded (from OSS to shareware to commerical offerings), and demonstrates significant performance improvements when that other core is available. Most desktop software on other platforms (X11 and Windows apps), are still largely sequential, and it's going to take years for that to change. Apple's consumers are going to see a much larger, and more immediate, benefit as it becomes economical to grant the Powermac a couple more cores, and move dual core down to the consumer lines. The software is already there.

  167. Changing focus... by Izago909 · · Score: 1

    Both major CPU makers have stopped using the clock spped as the selling point of their products for a very good reason. Raw clock speed is the lest effective way to judge preformance. A system is only as fast as its slowest part. With Athlon FX systems getting close to 2GHz FSB speeds, on chip memory controllers, and beefy L2 caches, it's easy to see just how much preformance you can get out a of a chip if you give it what it wants: low latency, high bandwith, and memory to spare.

  168. Dynamically-reprogrammable Processor HARDWARE? by Dogtanian · · Score: 1

    How about CPUs that can modify their own hardware-functionality on the fly, and very fast?

    I know that programmable-hardware devices are already well-established, but what I am considering is something that can do this on the fly, and repeatedly.

    Question is, how much performance improvement would this give?

    --
    "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
  169. in the old days, great programmers used to say... by museumpeace · · Score: 1
    "We should forget about small efficiencies, say about 97% of the time:
    premature optimization is the root of all evil." - Donald Knuth
    "Programming can be fun, so can cryptography; however
    they should not be combined." - Kreitzberg and Shneiderman
    "More computing sins are committed in the name
    of efficiency (without necessarily achieving it)
    than for any other single reason - including
    blind stupidity." - W.A. Wulf
    I loved and still get a kick out of squeezing a function into the fewest bytes or cpu cycles possible...I also like math puzzles. But it would be a mistake to romanticize the "good old days" when memory was expensive and cpu's were both slow and costly. Tweaking and whittling code at the instruction level would take you forever to write systems as complex as sit on the average user's desk these days.
    The real lessons of computer era are not Moores' law of transistor density but Gate's law of cyber-guzzling by dense users which I now coin:
    "processors are never so fast or memory so big that the next generation of customers can't be convinced to buy software that strains the system"
    In the long run, marketing pull always gets ahead of engineering push...just look at DEC. When I joined DEC in 77, those old programming proverbs were taped like gospel to the cubicles where the compiler writers worked. They seem forgotten but I found them here and here. In that year, nearly any system or periperal DEC dreamed up found willing scientific and engineering customers in labs. By '84, the earliest PC's were all the buzz but DEC's offerings in that area were ignored by the market. The imagination and genius of engineers and scientists is generally sufficient to awe the public initially. But if the technology has gratifying uses and economic benefits, markets absorb magic and make it an ordinary commodity and finally a staple for which improvement is always wanted.
    And by the way, since when is this topic news? I hope it isn't just because DDJ mentioned it. I don't feel like dredging up pointers to the bezillion pages on the matter but there has been academic and industry handwringing about the inevitable limitations of transistor size and speed for a decade. OK, one URL, thats all you get! read pg 62 for consice four year old description of the issue [and how carbon nanotubes are going to save us]. The predictions of the exact day when progress stops were always a bit vague and hedged with hopeful notes about gallinium and going to 3-d circuits...all that is really happening is that, having seen the wall a long ways off, chip makers aren't going to smack into it head on with an abrupt cesation of speed increases but veer off in new directions and so only slow down the increases.
    --
    SLASHDOT: news for people who can't concentrate on work or have no life at all and got tired of yelling back at the TV.
  170. Lying??? by megalomang · · Score: 0

    Lying? How so? This is a prediction. How many of us know exactly what will happen in the future? You didn't *really* think they knew the future did you? They just had a roadmap based on their expectations of the process technology. It didn't pan out, so they changed the roadmap. Everyone else did too. AMD has delayed the hell out of their technology scaling, higher frequency and dual core procs to the point where Intel will beat them to a dual-core release, but I don't see you complaining about that, do I? Transmeta is pulling out of the IA-compatible CPU business, but you aren't crying foul there either.

    The quote from the marketing rep you included does not have a date on it, and I'm sure the roadmap you remember seeing had an appropriate disclaimer on it, if it were even published by Intel (Intel doesn't generally publish these officially).

    Furthermore, you can rest assured that some day there will still be 10GHz chips sold.

    Haven't you ever noticed this clause at the bottom of similar PR? It's a shame that people actually need to cover their ass with legalese like this, really.

    This Business Outlook contains certain forward-looking statements that are subject to known and unknown risks and uncertainties that could cause actual results to differ materially from those expressed or implied by such statements. Such risks and uncertainties include, but are not limited to, the Risk Factors noted in the Business Outlook as well as in the Earnings Releases, Business Update press releases and Intel's filings with the Securities and Exchange Commission on, e.g., Form 10-K and Form 10-Q.

    1. Re:Lying??? by bigtrouble77 · · Score: 3, Insightful

      There's a big difference between a reasonable prediction and saying ridiculous things to inflate your stock price. I don't think it was reasonable for Intel to say, in 2002, that we will have a 10ghz part in the near future. Perhaps saying, 'Our goal is to reach 10Ghz by 2006', is a little more reasonable. But Craig Barrett and Co. don't talk that way (neither did Jerry Sanders of AMD). These statements could be looked at as devices to drive up stock prices. Finally, Intel said that the PIV's would hit 10Ghz. You can rest assured that's never going to happen.

    2. Re:Lying??? by megalomang · · Score: 2, Interesting

      I fully agree that bullish statements by both companies were all over the place, especially stepping up after AMD beat Intel to the 1GHz punch, which also coincided relatively well with the added desparation created by the dot-bomb. The result is that as you pointed out, unofficial technology roadmaps to 4 years down the line were being quoted, compounding the possibility for gross inaccuracies.

      But, I can assure you (I am part of the industry) that back then, the technology roadmap outlook was drastically different than today. It was impossible back then to understand the massive leakage issues at those speeds in 65nm and beyond since at the time, the warning signs were not unusual (i.e. they were overcome many times before on larger geometries). And believe me, the entire industry was practically blindsided by this. I think Intel was hit hardest simply because they were among the first to get there and were therefore aggressive on its adoption.

      To say they were lying, and hold them accountable some kind of liability due to their confidence in 65nm would stifle future growth of the entire technology industry.

      To single them out among all others who did the same would be unfair.

      To even try to assign a dollar amount to this would be absurd. The entire industry took a beating at the same time. How much of Intel's stock plunge can be attributed to the failure of 65nm and frequency scaling promises? Is Intel not free to achieve these performance gains through other means such as core parallelism, memory architecture, higher levels of integration, and i/o architecture? Does this mitigate these dollar amounts?

    3. Re:Lying??? by SQL+Error · · Score: 1

      To say they were lying, and hold them accountable some kind of liability due to their confidence in 65nm would stifle future growth of the entire technology industry.

      65nm hasn't failed yet. It's 90nm that's failed. (And 130nm was a bit of a cow too.)

  171. I knew it! by Chemisor · · Score: 1

    > Ball Semiconductor

    Hah! I knew it! :) /me does the happy dance.

    That company also have discovered some even more interesting advantages of doing spherical circuits. It turns out that the balls can be made without a cleanroom, which is obviously an enormous expenditure. They also cite lower environmental cost, due to less silicon going to waste. And making an inductor coil on the surface for communication is way cool!

  172. Processor size in units of time by iabervon · · Score: 1

    At 3 GHz, light travels 4 inches in a clock cycle. If you have a 2 inch processor, including the delay due to not using light in a vacuum, you simply can't have clock synchronization throughout the chip. That doesn't mean that processors can't go faster, but, when they do go faster, there won't be a single clock whose speed you can report.

  173. Impact on Loghorn? by PolR · · Score: 1

    What are the consequences on Longhorn release? IIRC Microsoft planned their capacity requirements according to the projected capacity of hardware at the time Longhorn will be released (2006), not what makes sense with current hardware. IIRC Longhorn specs are for something like 4-6 Ghz CPU. If the hardware is not there, will there be a wrench thrown into Microsoft plans?

  174. Goodbye to OO Programming by sanferrera · · Score: 1

    Object Oriented Programming worked because we had speed to spare, but thats over. Of course concurrency will be more important now, but the code will also have to be optimized. Goodbye C++, java, welcome back C.

  175. 10 MHz? by krunchyfrog · · Score: 0

    I misread the title of the article. I was wondering if the poster was having some huge nostalgic crisis because he lost some old 286/386 or was stolen.

    --
    printf($randomline(sigs.txt) \n "-- "$randomline(authors.txt));
    -- myself
  176. Re:Moore's Law isn't Speed Doubling, it's Transist by swordgeek · · Score: 1

    "Unless you've got a REALLY fat pipe, there's a limit on how much pr0n you can process"

    Amateur!!!

    --

    "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
  177. Re:Moore's Law isn't Speed Doubling, it's Transist by swordgeek · · Score: 1

    Hmm. Makes me think you should be running stuff like this on a different platform entirely. A Sun V490 would probably rip through that in seconds.

    --

    "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
  178. could not be said better by ndunn · · Score: 1

    Hogwash! Write first, optimize later . . . what are the chances that I can write a better sorting algorithm than one included in a standard library that was written by some who studied sorting algorithms [and thoroughly tested the code].

    Or more conretely:

    "We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." - Donald Knuth

    I would argue that its still important to know HOW to write these algorithms, so you know what the cost/benefits of different types of sorts are, but there is no virtue in reinventing a working wheel.

  179. I call FUD... by Anonymous Coward · · Score: 0

    I can't believe this got posted as a story...seems like trolling to me.

  180. so, learn ada by Anonymous Coward · · Score: 0
  181. Re:Asymptotic (OT) by Anonymous Coward · · Score: 0

    cool. interesting to know.

    question - does this mean you're indian/native-american ?

  182. But then... by sczimme · · Score: 3, Funny


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

    But then how are we supposed to leverage our synergies going forward to create a win-win situation? You are generating negative ROI in this incumbent conversation, and have become a cromulent addition to the team. You will be capsized^W rightsized immediately.

    --
    I want to drag this out as long as possible. Bring me my protractor.
    1. Re:But then... by danrees · · Score: 1

      Isn't ROI that thing in SimCity?

    2. Re:But then... by plexitox · · Score: 1

      you mean RCI ? the Residential Commercial Industrial balance meter?

    3. Re:But then... by spudchucker · · Score: 1

      Apparently that poster does not know how to become a critical participant exploiting synergistic methodologies contributing to a cohesive informational social transaction.

    4. Re:But then... by kurzweilfreak · · Score: 0

      All this drone-speak is wearing me out, can we all touch base on this next week?

      --

      kurzweil_freak

      5th Kyu Genbukan Ninpo/KJJR student

      Be the darkness that allows the light to shine.

  183. We are all too scared to switch to F.P. or PROLOG by tarpitcod · · Score: 1

    Many good points by other posters, but the core reason is simple. We are too scared to do it.

    Great ideas have been around for a fair while how to speed things up by orders of magnitude. Examples? Anybody remember John Backus and F.P.??? Remember Prolog?

    The truth of the matter is that great ideas for ways around the performance limitations we are experiencing have existed for decades, and we just haven't got the GUTS to make the jump.

    I dream sometimes of having the courage to throw away my imperative mind, and program in a world of logic (PROLOG) or make parallelism my mantra (F.P). I haven't had the guts yet, I always fall back to LDA #$0F, STA $D20F. have you had the guts to do it? If you have then please followup.

    We need to hear from people who made the leap from the imperative world of constructs we are all so familiar with and immersed themselves in those other worlds.

    --tarp

  184. You can find it... by Dave21212 · · Score: 1


    You can find it in the trunk of your flying car, right next to your alcohol-powered laptop.

    --
    "Whoever would overthrow the liberty of a nation must begin by subduing the freeness of speech."--Benjamin Franklin
  185. There reason we don't use GaAs by Theovon · · Score: 1

    Ok, I'm sure I'm missing lots here, but one of the reasons we like silicon is because SiO2 is an insulator, it's a solid, and it's insoluable. We use SiO2 very heavily in CMOS electronics, upon which all of our "fast CPUs".

    Well, I may be remembering this incorrectly, but I think one of the barriers for GaAs, besides being a more expensive material, is that when you oxidize GaAs, you get something which is water-soluable.

    Kinda kills the idea of doing CMOS in GaAs which throws us back into the 70's when people still used TTL for VLSI.

    1. Re:There reason we don't use GaAs by gus2000 · · Score: 1

      Well, I may be remembering this incorrectly, but I think one of the barriers for GaAs, besides being a more expensive material, is that when you oxidize GaAs, you get something which is water-soluable.

      No, you are thinking of Ge. The problem with GaAs is that the native oxide interface is full of surface states which gives you a transistor that is normally on rather than one which is normally off (which is what you want for CMOS). The transistors (MESFETS or HBTs) that you fab on GaAs are fine for analog applications, but have a static power dissipation problem that makes them bad for logic.

  186. Re:I think you are getting a few things mixed up h by WaZiX · · Score: 1

    i was merelay talking about bandwidth...

    and btw i guess you know better then:

    Physicist Anthony F.J. Levi of University of Southern California

    Michael Morse, Photonic Researcher at Intel

    Mark T. Bohr Director of process Architecture at Intel

    and W. Watt Gibbs, author of the very interesting article i got my information from in the November Issue of Scientific American.

    And btw those are just a couple of names taken in the two first paragraphs or so from the article.

  187. disposable symptoms by spoonyfork · · Score: 1

    Don't sell me faster hardware... sell me more efficient software and peripherals.

    --
    Speak truth to power.
  188. That humor isn't so far off by GoClick · · Score: 2, Insightful

    Actually they have proactivly developed new thingys ;)

    I'd like to note that the average 3Ghz PC can do MORE than the eqivalant of a 10Ghz 5Mhz 8086. Don't forget that it's not just your CPU doing math now days, it's that fancy $400 super-computer rivaling video card you've got too.

    1. Re:That humor isn't so far off by darkwhite · · Score: 1

      Not entirely correct. The CPU is a general-purpose processor. The GPU is not.

      --

      [an error occurred while processing this directive]
    2. Re:That humor isn't so far off by Jace+of+Fuse! · · Score: 1

      Actually, what I think he meant was that his Processor doesn't have to be 10 ghz to do what it is doing now BECAUSE it has that $400 video card with it's own included T&L processing capabilities.

      In fact, some of the things modern video cards are doing today are done as well as they are BECAUSE CPUs aren't general purpose processors. They may have specific purposes, but they're much better at doing those things than general purpose processors ever could be.

      --

      "Everything you know is wrong. (And stupid.)"

      Moderation Totals: Wrong=2, Stupid=3, Total=5.
    3. Re:That humor isn't so far off by darkwhite · · Score: 1

      Actually what I think I meant was that if you are running something that needs to crunch numbers to do what it's doing but doesn't need to show pretty pictures with that, the GPU is not going to speed it up whatsoever. In which case the GPU doesn't matter, if the CPU isn't fast enough it's still not fast enough. Particularly if the app is not parallelizable.

      --

      [an error occurred while processing this directive]
    4. Re:That humor isn't so far off by Jace+of+Fuse! · · Score: 1

      Well, I could hardly argue with THAT. I was simply pointing out that at least as far as video applications are concerned (games esspecially) we're much farther because of GPUs than we would be if we were relying on processing power alone, even if CPUs had managed to make it to the 10 ghz mark. Besides, Mhz never really was a very precise indicator of processing power anyway.

      --

      "Everything you know is wrong. (And stupid.)"

      Moderation Totals: Wrong=2, Stupid=3, Total=5.
  189. Re:Asymptotic (OT) by Some_Llama · · Score: 1

    TeePees Wikiups, TeePees Wikiups, sounds to me like you are two tents.

  190. 10Ghz AND to be used as Central Heating system by Anonymous Coward · · Score: 0

    Sounds great. Use your CPU and recycle the heat as a major power source for a household. Large offices may sell their surplus. A Brave New World is waiting!
    daim

  191. Software in the SoftwareThread Level Parallelism by iirving · · Score: 1



    Thread Level Parallelism

  192. Software in the Thread Level Parallelism Era by iirving · · Score: 1

    Tim Bray concurrently covered a simmlar topic in Software in the TLP Era and offers some strategies to deal with the coming MultiCore chips.

  193. Key Quote by lupine · · Score: 1

    "I will speculate that today's single-threaded applications as actually used in the field could actually see a performance boost for most users by going to a dual-core chip, not because the extra core is actually doing anything useful, but because it is running the adware and spyware that infest many users' systems and are otherwise slowing down the single CPU that user has today. I leave it up to you to decide whether adding a CPU to run your spyware is the best solution to that problem."

    Sounds like users dont really need faster processors, just adequete spyware protection & removal. But I cant wait for a dual core AMD-64 system.

  194. Re:Software in the Thread Level Parallelism Era by tarpitcod · · Score: 1

    How does this stuff compare to Burton Smiths MTA/Tera stuff?

  195. Heat management by Chemisor · · Score: 1

    > If you were to surround them with a hot spherical
    > shell, then they would become HOTTER than the average temperature of that shell

    Right, but if you can keep the shell temperature low, you would then also set a limit on the core temperature. If liquid cooling can keep a flat chip at 30C, the center of a likewise cooled sphere should be well within its normal operating temperature range.

    1. Re:Heat management by HiThere · · Score: 1

      True, but you are now specifying a cooling system. That means that the heat IS being removed. (Perhaps a sealed liquid coolant would be better than a silver heat pipe, I wouldn't know. You must have SOMETHING.)

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    2. Re:Heat management by Chemisor · · Score: 1

      > True, but you are now specifying a cooling system.

      You can't design a circuit without also designing a cooling system for it. There isn't a single desktop CPU that can run without one, and while monster fans are ubiqutous, liquid cooling is becoming popular. Of course, back in the mainframe days, plumbing was the computer :)

  196. Larger Data Inputs and Outputs by Josh · · Score: 1

    Even more important than bad (or less optimized = more cost effective) programming is the fact that the size of the data we want to process keeps getting bigger. Examples where this is obvious include things like computer games, meteorology, data mining, physical simulation, etc. There is still plenty of need for CPU power because each advance can be met by a desire to work on bigger/harder problems. But these bigger problems don't occur anymore in word processing, web browsing, or doing business forms, so computer gaming is the most activity where more processor can be useful.

  197. RTFA!! by fupeg · · Score: 1

    One the main points of TFA is that Moore's Law has continued to be true while clock speed has stalled. Actually you don't even have to RTFA, you can just look at the pretty graph on there.

  198. GaAs has made me some money by museumpeace · · Score: 1

    Back when Vitesse finally started getting decent yields on its communication components I bought shares that eventually doubled several times. I admit that a lot of less substantial technical achievments have made equally substantial profits in the market of the mid 90's. I don't know squat about stock markets and the only thing that kept VTSS from skining me alive later was my wife's advice to sell half the shares any time it split or duoubled. In 96, the typical stock analyst didn't know squat about GaAs so I had a temporary advantage.
    Just wanted to note that a few GaAs promises have been kept. [looks like I should invest in companies that make good heat sinks and fans?]

    --
    SLASHDOT: news for people who can't concentrate on work or have no life at all and got tired of yelling back at the TV.
  199. Speed scales with geometry by Baldrson · · Score: 1

    What you're missing is that the main source of increased speed for silicon was decreased feature size. This geometric scaling of speed is pretty independent of the material. What is not independent of the material is the electron mobility and capacitance.

  200. End of Cold War Changed Procurement by Baldrson · · Score: 1
    When the cold war was going hot and heavy the national labs needed computing power and they didn't care how they got it. They put out benchmarks/code and people designed computers to run the code or they didn't. If they did a good job they got PURCHASES.

    As the cold war ended there was a shift away from such performance-based purchases to idiotic programs where really really "smart" guys would divine the next wave in wonderfulness and have people with Ivy League and press connections hang around the halls of power schmoozing it up a real whole lot so they could get funding in advance of technical accomplishment.

  201. My 450Mhz P3 still works !! by fani · · Score: 0

    It may be 2005 but my P3-450Mhz still packs a punch for my wife.
    She's blissfully unaware that she's now using the 450Mhz instead of the super duper AMD 3500+.

    From browsing the internet, to playing Solitaire, to reading email, even this 450Mhz from 1999 works like a charm.

    Forget the processor, today the bus speeds are like 3 times faster.

    This makes us wonder why do you really need a 10GHz PC ? Perhaps you can lower your heating bill using this as a heater :)

  202. Re:Asymptotic (OT) by gentgeen · · Score: 1

    Not enough to count for anything. But Native American history is a hobby, and I am a Indian Hobbiest (check out www.powwows.com) it is heavy with the java/multimedia/etc but if you can get past that a lot of good info on pow wows and both Native and hobbiest.

  203. Since when is this topic news? by museumpeace · · Score: 1

    Since when is this topic news? I hope it isn't just because DDJ mentioned it. I don't feel like dredging up pointers to the bezillion pages on the matter but there has been academic and industry handwringing about the inevitable limitations of transistor size and speed for a decade. OK, one URL, thats all you get! [rice.edu] read pg 62 for consice four year old description of the issue [and how carbon nanotubes are going to save us]. The predictions of the exact day when progress stops were always a bit vague and hedged with hopeful notes about gallinium and going to 3-d circuits...all that is really happening is that, having seen the wall a long ways off, chip makers aren't going to smack into it head on with an abrupt cesation of speed increases but veer off in new directions and so only slow down the increases.

    at 500 comments in 2 hours, there is clearly healthy /. interest...but you could have had this conversation anytime in the last 5 years!

    --
    SLASHDOT: news for people who can't concentrate on work or have no life at all and got tired of yelling back at the TV.
  204. technology surpression by LabRat404 · · Score: 0

    there will always be money to be made in the market of technology surpression. its why we still run our cars on gas.

    --
    1001100 1100101 1100001 1110110 1100101 1001101 1111001 1000010 1101001 1110100 1110011 1000001 1101100 1101111 110111
  205. Who said professional..... by way2trivial · · Score: 1
    I am a prosumer.. my eldest is 20 months old, I've made now 4 different dvd's to distribute to family on both sides of the pond, and my abilities with video editing tools grows each time, but it still takes 6-8 hours (p4 2.53) from finished AVI to first DVD burned

    I find that excessive.

    CGI is something I'd like to dabble in for future projects, I know it's a resource hog.

    --
    every day http://en.wikipedia.org/wiki/Special:Random
  206. Re:Moore's Law isn't Speed Doubling, it's Transist by Peldor · · Score: 1
    Meanwhile, cache sizes are up, instruction pipes are up, hyperthreading has been here a while, multi-core chips are coming down the pike... we're still getting speed gains, just not in raw clocks.

    And "just" not in the same magnitudes (over time) as we saw from those previous clock speed gains. Which is the point of the article. Doubling cache or going multi-core has much smaller returns than doubling the clock speed for most apps.

    I hate to say it, but what do you think you need 10GHz for anyway? Unless you've got a REALLY fat pipe, there's a limit on how much pr0n you can process ;^)

    The same thing you needed 1 GHz for when 300 MHz was state-of-the-art. And don't ever ask that again or you'll have to turn in your geek card.

  207. Re:Software in the Thread Level Parallelism Era by iirving · · Score: 1
    I don't know a lot about the MTA/Trea stuff, save they have been doing highly parallel and shared shared memory system for a long time, and indeed I belive they have pioneered a lot in this space. (see From Here to Petraflops)

    The differance is that MultiCore is going mainstream. Intel, ADM, IBM, Sun all have chips we can buy in the next year. Not as powerfully as Trea, but a lot cheaper.

    My point would be that - regardless of why its happening - there is a major change it hardware happening, Like the change from Intel 16 bit to 32 bit, which took several years, but much more difficult. (we are also going 64 bit is servers and desktops to address all that chaep ram, but that is also most a non-story.)

    The industry has been talking about Parallelism for a long, long, time. Looks like we a now starting down that path. Its going to be hard, but it is rewarding. Which is part of Herb Sutter's and Tim Bray's message. The OS's, tools, and applications that do this right are going have a big advantage in the server and desk/laptop market with all that highly scablible hardware.

  208. The only stupid question by starglider29a · · Score: 2, Interesting
    The one unasked:

    Could we do a multi-processor system that splits the tasks according to their horsepower needs? The OS splits the tasks the processor that can handle it, an no more. Multilevel, Trickle UP CPU power. Say, for sake of argument, set up arbitrary CPU usage levels
    1. A Pentium nothin' (or equivalent)
      relegate the slow, stupid stuff to a lesser processor, like Notepad, some sniffers... look at your Task Manager processes (or equivalents) for stuff you could be running on a 80286 and shove them to the CPU slums. This level keeps the lights on, controls the heat. It's the oil and the water pump on your Ferrari.
    2. A Pentium ][ (or equivalent)
      Runs the OS functions themselves, if they can. File transfer, TCP/IP, simple Multimedia like MP3 & CD, Virus, Spyware detection... This level replaces the Pentium ][ in your kid's room running Limewire. It's the Stereo on your Ferrari
    3. A Pentium ]|[ (or equivalent)
      The GUI, the heavy multimedia, like video, CD burning, the bloated web rendering... this level makes the UI responsive. It's the suspension on the Ferrari
    4. A Pentium IV (or equivalent)
      The Engine of your Ferrari! The monster throughput... The Doom VII, the Celestia: Andromeda, SETI:Alpha 6, Climate Prediction, and of course the rendering of the perfect sig-other on Maya. When yer not using this part, shut it down, despin the fan and listen to the sound of silence.

    The offshoot of this is that there can be a Level 5, if one were to plug into a cluster. From there, you can plug into BIGGER clusters until you either reach Blue Gene/X or you ARE part of the cluster.

    Why not?
  209. Re:Moore's Law isn't Speed Doubling, it's Transist by Trailer+Trash · · Score: 1

    I hate to say it, but what do you think you need 10GHz for anyway?

    When I bought a 160GB drive a couple of years ago, my linux kernel only saw 130GB of it. I laughed, since it didn't matter. I wasn't going to use 130GB, either.

    Right? Right?

    Well, wrong.

    I bought a DV camcorder, and started pulling in all of our old tapes, even my wedding tape. Now I have 250GB or so of video on the LAN and I'm adding more HD space.

    What will I use a 10GHz processor for? I'll find out when I get one. Probably something with video...

  210. What realtime interactive full-motion video? by argent · · Score: 1

    "A machine that can do realtime interactive full motion video".

    Only in a very limited way. The absolutely latest "realtime interactive full-motion video" - Halflife 2 - is just beginning to do optical transparency and realistic physics in a reasonable way. It's only good enough to fool the eye for a few seconds, if you pay attention to shadows and reflections, but it's the first system that's managed to provide anything like photorealistic rendering.

    Luckily raytracing is very parallelisable through brute-force techniques (give each GPU a full copy of the polygon database and a segment of the screen to render, and Nx as many processors will be able to give you Nx the framerate... up until pushing out the polygons starts taking a significant part of the CPU), and luminosity (shadowcasting is a really crude kind of luminosity calculation) and the physics engine can be run separately from the final engine...

    So "realtime interactive full-motion video" is potentially possible, but we're not there yet.

    1. Re:What realtime interactive full-motion video? by Chandon+Seldon · · Score: 1

      I didn't coment on photorealism, but I'd say that any of the 3D games qualify as "realtime interactive full motion video".

      Let's take Quake I for a second:

      Realtime - Yes, the scenes are not pre-rendered.
      Interactive - You can move around.
      Full Motion - There are 30+ frames per second.
      Video - It isn't anything else...

      My biggest question there is Interactive, and even half-life 2 doesn't have full environment interaction (the inconsistancy on moving cars with the gravity gun annoyed me to no end), but there was *some* interaction even in Quake I, so the game was interactive.

      We continue to approach "Photorealistic Realtime Full Motion Video" and I think it's a long way off. Look at some of the CGI scenes in current action movies - it's getting better but we're not to phtorealistic yet - if we can't do it with a renderfarm I don't think we'll get it in realtime any time soon.

      But that leaves an obvious domain where an increase in processing power continues to be useful, and another reason why the "The computer I have is fine for the applications I currently run, so technology can just stagnate here - in fact I'd prefer it so I never need to spend money upgrading" crowd won't get their wish.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    2. Re:What realtime interactive full-motion video? by argent · · Score: 1

      I'd say that any of the 3D games qualify as "realtime interactive full motion video".

      Ironically, gamers use "FMV" - "full motion video" - to describe the cut-scenes in the more movie-like video-games like Final Fantasy, and the distinguishing factor between these cut-scenes and the everyday "running around in a realtime-interactive 3d-environment" that most of the game-play consists of is the level of realism in the cut-scenes.

      It's only the very latest games that seem to use use the regular 3d engine to render the cut-scenes, at least with any great effectiveness. And these still look better than the realtime-interactive part of the game... generally because the animation and physics is fully scripted instead of depending on what a friend of mine used to call "meatball AI" when we were doing video-games - back in the '80s when good realtime interactive 2d was a challenge and the Amiga's blitter was a breakthrough.

      20 years later we have better graphics... ALMOST good enough to handle cartoon photorealism (Legend of Zelda - Windwalker is an amazing approach to that, but the physics of sailing and wave motion is all wrong even for a cartoon world), but the AI is still crude as hell.

  211. Exposé and its children... by argent · · Score: 1

    GPUs are good enough that a realtime 3d window manager is possible. It's a much simpler problem than FMV, and Apple's beginning to play with some of the features in Quartz Extreme and Exposé, but until someone actually produces something like my fantasy 3dWM we won't see much demand for it.

    1. Re:Exposé and its children... by Erik+Hollensbe · · Score: 1

      Bring me holographic monitors, and I'll bring you a person interested in 3d UI's.

      Until then, uh, I'll stick to counter-strike. I'm not trying to get any real work done there.

    2. Re:Exposé and its children... by argent · · Score: 1

      You're already using a 3D UI, unless you're using RatPoison or some similar tiled or full-screen-only window manager.

      There's a Winston Churchill quote that seems approprieate here.

  212. 2D room-temp superconductors by gnuman99 · · Score: 1
    I'd think the more likely reasons would have to do, for starters, with consumers not wanting or being able to afford a computer that requires constant cooling with liquid nitrogen (or even worse, liquid helium) to work.

    You can now have even room temperature super-conductors, but these are (I think) not 3D superconductors, but 2D supercuducors (surface superconducing). They do not work for any application with any power demands (eg. magnets or power distribution), but then the purpose of a CPU is not to trasfer or translate power.

  213. there are other materials by uglomera · · Score: 1

    They are called compound semiconductors. Intel is already funding research in III-V devices.

    Yes, I know this was lame on the font of all the business speak :D

  214. That article seems kind of pointless. by XxXoldsaltXxX · · Score: 0

    Why wouldnt programmers add more to their software? Its kind of like developing and using a 10,000 horsepower engine, but never pushing the throttle above 10%.

  215. Luckily we have lots of concurrency to chew on... by argent · · Score: 1

    The performance gains should initially be about the same as having a true dual-CPU system (only the system will be cheaper because the motherboard doesn't have to have two sockets and associated "glue" chippery), which means something less than double the speed even in the ideal case, and just like today it will boost reasonably well-written multi-threaded applications. Not single-threaded ones.

    That's OK, for most people dropping back to 1 GHz and getting half a dozen cores would give them a lot nicer computer than pushing the CPU speed to 4 GHz on a single chip. Why? because there's gobs of concurrency on your desktop already no matter what your processor... no mater what your OS, there's half a dozen processes (tasks, whatever) that each take turns using a lot of the CPU and occasionally stepping on each others toes and making your computer feel slow.

    For games, increasingly, the bottleneck is the video card. There's still a lot of straight-line code in most games, but things like the physics engine, the rendering engine, and the user interface... these parts of the system can be made to have relatively narrow communication channels between each other. Each can then become a separate thread, or even a separate program, running on a separate processor. Overall a 6x1GHz system would still be able to provide a better experience than a 1x4GHz one, even for games.

    This won't make the benchmark boys happy, but who cares? They haven't been happy in a long time anyway.

  216. O.K., let's try this again... by CPNABEND · · Score: 1

    In my office at home, I am running AMD 3000+ for my XP box and AMD 2200+ for my SuSe 9.1 box. If you look at the S.M.A.R.T. number off of the MOBO sensors, the temps are scary. Running one "in" fan and one "out" fan on each box, in addition to multi-speed power supply fans, the 8' * 10' room gets rather warm, too. As the density of chips increases, and the clock frequency increases, we are getting to the point where liquid-based cooling is necessary on gamer machines. Is this where we all want to go? The short-term answer is dual-core at lower clock speeds. Assuming, with MP factors that 1+1 = 1.9 or so, a multi-tasking system can give a pretty good illusion of being a honkin' single image. The other short-term answer is multiple, slower CPUs for the same reason; spread the heat dissipation across more real estate on the MOBO to keep from frying things. Remember - in the world of electronics - Heat IS NOT your freind :^)

    --
    My wife doesn't listen to me either...
  217. BeOS by Anonymous Coward · · Score: 0

    This is exactly the premise that BeOS tried to sell a few years ago.

    Maybe they were just a little bit ahead of their time.

  218. What we need is a war by [000000] · · Score: 1

    war is the best time for technology, however it has its draw backs, like death.....

  219. Are you trying to suggest... by hajihill · · Score: 1

    That my NES emulators aren't challenging my brand new P4, or utilizing my gig of ram to peak performance??

    --
    Of blankness, I know nothing.
  220. Moore's Law by Fringex · · Score: 1

    Well I guess you can't call it a Law anymore if we are hitting this road block.

    Moore's Idea? Moore's Philosophy?

  221. maybe, a physics card? by Khashishi · · Score: 1

    Perhaps some day, we'll have processors dedicated to physics-- a PPU? Perhaps it would model a simple subset of physics: rigid body collisions or rigid jointed bodies.

    1. Re:maybe, a physics card? by grumbel · · Score: 1

      Unlikly, I am not so sure how good physic calculation can be done in parallel, but if they could you could just abuse the graphics cards, which today is not only good for graphics, but a rather generic vector processing unit which can be used for anything that needs calculation of huge vectors of numbers.

  222. Bus, Mghz... whatever.... by Anonymous Coward · · Score: 0

    If you've read this far you'll realize what a tweerp you are & all others when you realize the counter to this agr.. is on the same slash page as the initial listing...
    http://www.boston.com/business/technol ogy/articles /2005/01/05/intel_researchers_build_laser_on_chip? mode=PF

  223. Innovation? by juanbobo · · Score: 1

    Maybe we finally have a concrete wake-up call for America to stop relying on the fact that it is America and embrace innovation. Innovation creates jobs, innovation builds an economy, and innovation ultimately saves lives.

  224. Re:Moore's Law isn't Speed Doubling, it's Transist by Anonymous Coward · · Score: 0

    Actuallly, I generally find that the more pr0n I process, the fatter my pipe gets.

  225. Re:Moore's Law isn't Speed Doubling, it's Transist by krumms · · Score: 1

    I hate to say it, but what do you think you need 10GHz for anyway? Unless you've got a REALLY fat pipe, there's a limit on how much pr0n you can process

    Oh yes, how we all love to "process pr0n" with our "REALLY fat pipe".

  226. Re:water cooling by sarahtim · · Score: 1

    So it has water cooling... so what? .. and "lying out his ass" is a bit strong. Jobs will have said that because IBM told him that they hoped to get there. They, and Intel, found the next step in development of their cpu's harder than they anticipated.

  227. PC Speed doubles every 18 months, while slashdot.. by MrArmyAnt · · Score: 1

    Isn't the speed of PC's supposed to double every 18 months? Someone needs to get out a periodic table and find something better than silicon. Slashdot comments, however, seem to double every 30 seconds. ~T http://www.ModLife.Net

  228. Re:water cooling by Anonymous Coward · · Score: 0
    If Jobs promises something, it's his responsibility to deliver. This wouldn't be an issue if he had said "IBM promises to deliver 3 GHz within a year" or something along those lines.

    As for the water cooling part, you clearly didn't read the message. Water cooling on the G5 is obviously a stopgap measure because of the insane heat levels. They wouldn't voluntarily start using water cooling. Nobody would.

    I suspect Apple will demonstrate a 3.0 GHz G5 within a month or two, but it'll also be water cooled and won't find its way to consumer products until the end of this year, volume shipments much later.

    I'm sorry, the G5 isn't a miracle you'd have hoped for. My money is on the Athlon 64, which can be clocked well past 3.0 GHz (maybe 3.5) on air at 90 nm process technology and dual stress liner strained silicon. These chips are due to be shipped in the first quarter of 2005, though AMD will probably play it safe and not release insanely fast chips even though they have the chance to beat Intel repeatedly with a large stick.

  229. 10 Gigahazard PC? by Anonymous Coward · · Score: 0

    You typed 10Ghz right? I look up 10 and it means 10. The capital G is a metric prefix for one billion "Giga", and the abbreviation for hazard is hz. That's what you meant isn't it? Surely you didn't trip over one of my pet peeves, ignorant of the work of German Scientist Heinrich Hertz (who spelled his last name with a capital H) and accidently (or foolishly) droped the capitalization!!! Next thing, you would replace the metric prefix M (for mega, representative of million), with m (for milli, representative of 1/1000). I saw a lot of computers for sale in stores advertised as 900mHz. 900 millihertz, or worse 900mhz --900 millihazard, whatever that is. When I was studying engineering, people would occasionally get this wrong (and thus the whole answer was wrong). I was told that even if you didn't give a sniff about the engineering "I only do business, not of that yukky engineering stuff", that legal business contracts with incorrect metric prefixes are legally binding as stated. If you order 200 1800 mHz computers for $400,000, they can sell you 200 old IBM XT's, since they excede the contract by running at 2.77 MHz, and all you should have expected was 1.8 Hz --1.8 cycles each and every second. It's wouldn't be their fault that you couldn't tell the thickness of a dime -1mm- from 621 miles -1Mm - either.

  230. OOP braggin's by Tablizer · · Score: 1

    All that talk about how great OOP is and nobody challenges it? I have not seen any good evidence that OOP improves the maintanence of complex software. Surveys don't show any lower failure rate for OOP software. Ed Yourdon did a survey of such in the 90's.

    1. Re:OOP braggin's by Tablizer · · Score: 1

      Another thing, the article claimed that very few developers know how to do concurrency correctly. The fact is that anybody who uses and understands basic database transactions and client/server techniques has been doing concurrency and often do it well. The database abstracts away many of those details. I see no reason to limit the discussion to just "RAM-based" solutions. Database concepts can and do extend to RAM.

  231. wish author could get his facts straight... by iamhassi · · Score: 1
    "We're at 3.4GHz already--surely 4GHz can't be far away? .... As of this writing, Intel is planning to ramp up a little further to 3.73GHz in early 2005..."

    Article doesn't say when this was written, but we're already beyond 3.4 ghz. You can but a 3.6ghz on Pricewatch right now and Tom's Hardware announced a 3.8 ghz being released way back in November 2004, so I don't know why the author is saying 3.4ghz is the top of the line currently and Intel will release a 3.73 ghz in 2005.

    When was this written, early 2004?

    I do have to laugh a little at it: "This article will appear in Dr. Dobb's Journal, 30(3), March 2005. A much briefer version under the title "The Concurrency Revolution" will appear in C/C++ Users Journal, 23(2), February 2005."

    With the author saying "3.4 is out now and 3.73ghz early 2005" while everyone's upgrading to a 3.8 that's been out since 2004 it's gonna make that article look very old and inaccurate.

    --
    my karma will be here long after I'm gone
  232. 2004: Rest of desktop computer gets faster. by MtViewGuy · · Score: 1

    I think what has started to happen is that because CPU's are running pretty fast nowadays, they are now starting to upgrade the rest of the computer to keep up with the CPU.

    As I said in another post here, I wrote these things are now happening to desktop computers:

    1. The development of faster motherboard interconnects with improved chipsets and things like HyperTransport and its competitors.

    2. The wide availability of PC3200 (DDR-400) DDR-SDRAM system RAM, with even faster RAM coming over the next 18-24 months.

    3. The development of AGP 8x and new PCI Express connections for graphics cards with 3-D processing ability that would be the domain of ultra-expensive workstations only a few years ago.

    4. The development of ATA-100/133 IDE, Serial ATA and soon Serial ATA-II IDE, and UltraSCSI 160/320 interfaces and 10,000+ RPM drives with 8 to 16 MB on-drive memory caches for very fast hard disk access. Even optical disk drives are benefiting from these faster interfaces.

    5. The very wide availability of 100Base-T Ethernet connections on most motherboards, plus some motherboards now sport 1000Base-T Gigabit Ethernet connections.

    6. The near-universal availability of USB 2.0 connections and increasing use of IEEE-1394 connections to external devices, which makes the use of external disk drives to back up data and connect to digital camcorders possible.


    These improvements in the rest of the computer means you don't need the fastest CPU to get much-improved performance over desktop machines of a few years ago.

  233. working while it waits... by mangee · · Score: 1
    How much computing did the machine do while you read this paragraph of text?

    mmm. Warmed my lap.. and did a little bit. 0% idle.

  234. This will not be accepet by keyboardsamurai · · Score: 1

    Yes, maybe we have reached this limit for the moment, but I don't think the decision to just put more cores on a chip will fit well with customers. I wrote a small article about this a while back on this page Basically concurrency is too hard for the average developer to use in any single project. It opens the floodgates to a mighty source of errors. No customer will want that. The Industry obviously has got to invest in R&D for a more acceptable solution.

  235. best line of fit by areve · · Score: 1

    I'm posting really late on this article so no one will read this but the line of best fit for those points is shockingly out! If i was to draw it then the 10000ghz would surface in 2008

  236. My debasement of moores law by tod_miller · · Score: 1

    My journal entry here contains a nice little article on why Moore can show his law into his pipe and smoke it.

    Also, Smoking Gnu in Going Postal... is this GNU?? :-) I like to think so.

    --
    #hostfile 0.0.0.0 primidi.com 0.0.0.0 www.primidi.com 0.0.0.0 radio.weblogs.com
  237. Broken promises.. by TibbonZero · · Score: 1

    Flying cars
    Duke Nukem Forever
    Windows now crashing...

    --
    Tibbon
    tibbon.com