Slashdot Mirror


45 Years Later, Does Moore's Law Still Hold True?

Velcroman1 writes "Intel has packed just shy of a billion transistors into the 216 square millimeters of silicon that compose its latest chip, each one far, far thinner than a sliver of human hair. But this mind-blowing feat of engineering doesn't really surprise us, right? After all, that's just Moore's Law in action isn't it? In 1965, an article in "Electronics" magazine by Gordon Moore, the future founder of chip juggernaut Intel, predicted that computer processing power would double roughly every 18 months. Or maybe he said 12 months. Or was it 24 months? Actually, nowhere in the article did Moore actually spell out that famous declaration, nor does the word 'law' even appear in the article at all. Yet the idea has proved remarkably resilient over time, entering the zeitgeist and lodging like a stubborn computer virus you just can't eradicate. But does it hold true? Strangely, that seems to depend more than anything on whom you ask. 'Yes, it still matters, and yes we're still tracking it,' said Mark Bohr, Intel senior fellow and director of process architecture and integration. 'Semiconductor chips haven't actually tracked the progress predicted by Moore's law for many years,' said Tom Halfhill, the well respected chip analyst with industry bible the Microprocessor Report."

214 comments

  1. Number of components, not computing power by Daengbo · · Score: 2

    Number of components, not computing power, and the time-frame should be easy to figure out given the difference between 1965's number and the 65,000 predicted in 1975.

    1. Re:Number of components, not computing power by MrEricSir · · Score: 3, Insightful

      Adding components is easy. Making faster computers is not.

      --
      There's no -1 for "I don't get it."
    2. Re:Number of components, not computing power by Monkeedude1212 · · Score: 1

      I thought it was the number of transistors in a chip will double (or more, due to major breakthroughs) every 2 years, which means whatever they had 2 years ago would need to have been doubled. Which, when people asked if Intel would have 1 billion transistors on a 1 inch chip by 2010 - they said "Already done it!"

    3. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      Especially when the software retards are jut eager to pile on bloat, abstraction and whatever tickles their fancy this week. After all, they're not engineers, and they're not doing the heavy lifting.

    4. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      The exact law is that after a certain time period you get twice the number of components on the same piece of silicon FOR THE SAME PRICE. IC node scaling still follows this. Once about every 18 months we move to a smaller process.

    5. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      Yeah, god forbid the software actually uses the chip. It should sit there idle, like RAM.

      Resources are for stockpiling.

    6. Re:Number of components, not computing power by NewWorldDan · · Score: 2

      Conveniantly, the actual 1965 article is linked in the summary above. Specifically, it was about the cost-effectiveness of adding components to in integrated circuit. Circuits with few components aren't cost effective to build, and cuircits with more components have lower yields, making them not ideal either. At the time, the component count was doubling on a yearly basis, and Moore predicted that this would continue for the near term (5-10 years), but that the longer term trend was unlikely. And so it was with time between component count doubling increasing from 12 moths to 18 to 24 to whatever it is today. I remember in the early 90s, processor performance was easily doubling every 2 years, and it certainly hasn't been that way the last 4-5 years.

    7. Re:Number of components, not computing power by __aatirs3925 · · Score: 5, Funny

      We call those Java developers.

    8. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      No, it's the truth.

    9. Re:Number of components, not computing power by Yvan256 · · Score: 5, Insightful

      You're either trolling or looking at it the wrong way.

      More efficient software means we could probably run tomorrow's software with yesterday's hardware.

      Instead, because of bloat, we're stuck running yesterday's software with tomorrow's hardware.

      When put in the mobile context, it also means shorter battery life.

    10. Re:Number of components, not computing power by bluefoxlucid · · Score: 1

      You mean like how back in the day you had 32 megs of RAM using Windows, with a 100MHz processor, and you could pile on a new program and the computer would swap 50 megs to disk, and tick along just fine mostly?

      And nowadays we have 4 gigs of RAM, and the computer uses 500 megs of swap and every time you alt-tab you have to wait 4-5 seconds for everything to load back into RAM as windows slowly get redrawn, and everything runs slow... but wait! Developers are piling more and more on, since there's 4 gigs of RAM then EVERY program can use 2-3 gigs of RAM, and now... yes! 6 gigs of swap, and a computer that barely runs at all with 6 8 core processors!

    11. Re:Number of components, not computing power by BlueWaterBaboonFarm · · Score: 3, Insightful

      Since when can't you call someone a troll for telling you the truth? ~

    12. Re:Number of components, not computing power by mangu · · Score: 5, Insightful

      I remember in the early 90s, processor performance was easily doubling every 2 years, and it certainly hasn't been that way the last 4-5 years.

      It was easier to measure then, because performance was directly related to clock rate. Now that clock has stopped going up, performance depends on parallel processing.

      Then there's a catch, parallel processing depends on the software. Doubling clock rate will probably double the performance of almost any software that runs in the computer, doubling the number of cores not necessarily. Luckily, the most demanding tasks in computing are those that can be parallelized.

      With the advent of the GPGPU the future looks bright for Moore's Law. I've recently run some benchmarks using Cuda to perform FFTs and compared it to the data I have from my old computers. In my case, at least, my current computer is above the curve predicted by applying Moore's Law to the computers I've had in the last 25 years.

    13. Re:Number of components, not computing power by rubycodez · · Score: 1

      some of us might want to run more than one major application at once, our maybe use our RAM for our own data instead of hundreds of megabytes of bloatware.

    14. Re:Number of components, not computing power by MrEricSir · · Score: 1

      That's called "enterprise software."

      --
      There's no -1 for "I don't get it."
    15. Re:Number of components, not computing power by Joce640k · · Score: 3, Insightful

      I remember worrying when they started making 16 and 20Mhz CPUs, I thought digital electronics wouldn't be very stable at those sort of clock speeds.

      --
      No sig today...
    16. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      We call those Java developers.

      Or Bjarne Stroustrup & C++0x.

      Today's C++ ain't your Dad's C++!

    17. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      Adding components is easy. Making faster computers is not.

      exactly. quantum mechanics sets a pretty hard and fast limit of just how fast computers can actually get.

    18. Re:Number of components, not computing power by vux984 · · Score: 5, Interesting

      It was easier to measure then, because performance was directly related to clock rate.

      It was easier to measure then because real world performance was actually doubling and was apparent in most benchmarks.

      Now that clock has stopped going up, performance depends on parallel processing.

      Performance isn't doubling anymore. Cores are increasing, and the pipelines are being reworked, cache is increasing, but PERFORMANCE isn't doubling.

      Then there's a catch, parallel processing depends on the software.

      It depends on the task itself being parallelizable in the first place, and many many tasks aren't.

      Luckily, the most demanding tasks in computing are those that can be parallelized.

      Unfortunately its the aggregate of a pile of small independent undemanding tasks that drags modern PCs to a crawl. And these aren't even bottlenecking the CPU itself... to be honest I don't know what the bottleneck is right now in some items... I'll open up the task manager... cpu utilization will be comfortably low on all cores, hard drive lights are idle so it shouldn't be waiting on IO... and the progress bar is just sitting there... literally 20-30 seconds later things start happening again... WHAT THE HELL? What are the possible bottlenecks that cause this?

    19. Re:Number of components, not computing power by icebike · · Score: 5, Insightful

      Well said.

      I'm often modded troll when I claim that every advancement in computer processing power has been absorbed by look and feel of the OS interface.

      Recalculating the spreadsheet (or just about any other real work) seemingly takes just as long (short?) as ever.

      I know its not provably true, but it sure seems that way.

      --
      Sig Battery depleted. Reverting to safe mode.
    20. Re:Number of components, not computing power by Jonner · · Score: 1

      It depends what you mean by "faster computer." Nobody expects clock speeds to advance much beyond the several GHz possible today. Therefore, more and more components are being devoted to parallel processing, such as multiple cores, pipelines, and processor threads.

      It seems to me that chip designers like Intel, AMD and others are doing pretty well at getting more and more processing power out of each clock cycle, though I'd hesitate to call anything about chip design "easy." Writing software to take advantage of the increasing parallelism seems harder.

    21. Re:Number of components, not computing power by increment1 · · Score: 2

      // TODO remove this
      sleep(30);

    22. Re:Number of components, not computing power by Anonymous Coward · · Score: 1

      This depends on your definition of performance.

      If you define it as "How fast does program X run" then no, it's not increasing.

      If you define it as "How much work can the computer do in one second" then yes, it increases.

      Also, you don't necessarily need a highly parallelizable task, you simply need a lot of tasks.

      To your last question, a some operating systems these days (I'm looking at you, Vista) try to make certain things "faster" by indexing. That means, every time you copy/move/unzip files, it has to update the index. That also means that working with a lot of small files is much worse than one large one. This is basically why Vista's copies are so slow. The benefit of this (the usefulness of which is debatable) is that searching for files is much faster.

      For me, I don't often even *do* file searches, so it's mainly a feature that slows things down and does nothing for me.

    23. Re:Number of components, not computing power by MaskedSlacker · · Score: 1

      There is no exact law.

    24. Re:Number of components, not computing power by TheCarp · · Score: 1

      > It was easier to measure then, because performance was directly related to clock rate. Now that clock
      > has stopped going up, performance depends on parallel processing.

      Very true, but, is it still "Moore's Law" if you reformulate it to take new paradigms into account? When Einstein adopted the Lorentz Transformations to describe relative motion, nobody referred to those equations as "Newton's Laws".

      Its splitting hairs but, I don't think its all that useful to call a "law" anyway. I always thought of it more of a "rule of thumb". As such, it is still useful. If I have a workload that runs slow today, I know that that isn't a total killer, because, 2 years or so down the line, I can expect to have machines that can do the same workload faster (or take on a bigger one).

      In those terms, "Moore's Law", as long as you don't try to get too specific with it, works ok. Its also good for explaining things to non-technical people when they want an idea of a comparison between their old machine and a brand new one.... again... accuracy and precision are not important here, just, a general ballpark.

      For that, I think its great, and I use it that way. However that said... there is no reason to expect it wont change. Like, I fully expect that if some major national government decided to utterly pour resources into the problem we would start seeing that doubling time climbing to 4 or 6 or even 8 years! :)

      -Steve

      --
      "I opened my eyes, and everything went dark again"
    25. Re:Number of components, not computing power by Cid+Highwind · · Score: 4, Insightful

      The problem with that is there is no objective definition of software bloat. It's just slashdot shorthand for "spending time on stuff I personally don't find important".

      Your "bloat" is another user's "better interface" or "better security" or "maintainable code".

      --
      0 1 - just my two bits
    26. Re:Number of components, not computing power by Confusador · · Score: 2

      I know you said that it shouldn't be I/O, but I would still bet money that if you put an SSD in there you'd notice a dramatic improvement. (Although, you didn't mention RAM usage, but even then the SSD would help since it would speed up swap.)

    27. Re:Number of components, not computing power by nabsltd · · Score: 1

      Nobody expects clock speeds to advance much beyond the several GHz possible today.

      With the Sandy Bridge chips overclocking about 20% faster at the same temperature, it will only take about 3 more iterations before we are nearing 10GHz.

    28. Re:Number of components, not computing power by nabsltd · · Score: 1

      Performance isn't doubling anymore. Cores are increasing, and the pipelines are being reworked, cache is increasing, but PERFORMANCE isn't doubling.

      It really is, if you have software that takes advantage of all those core. If you have a single-threaded task, then you probably aren't seeing an increase in performance of that task, but you can now run that task plus something else at the same time.

      I have been encoding audio to Dolby Digital recently, and the single-threaded compressor finished the job in about 1-2% of the length of the audio, so, 1 hour of audio took about a minute to encode. Although it has been available for a long time, I had not tried the Aften AC-3 encoder before, but after discovering that it is multithreaded and can encode that same hour of audio in less than 5 seconds on an 8-core machine, I'm never using anything else.

      There are many other examples like mine that show overall performance is increasing. Even games now benefit from more cores, although 4 is about the limit of increasing performance for most current titles.

    29. Re:Number of components, not computing power by rawler · · Score: 1

      When put in the mobile context, it also means shorter battery life.

      It also provides incentive for hardware makers to keep focusing on performance rather than other qualities. It's to the point of the hardware literally catching on fire, killing people.

      Sure, if you sit with your laptop in your lap, it's smart to make sure it gets properly ventilated, but WHY SHOULD THE USER HAVE TO CARE? Had software systems remained efficient, hardware manufacturers would soon had to differentiate themselves on other qualities such as cool and quiet, case-design or other things users actually value.

    30. Re:Number of components, not computing power by Anonymous Coward · · Score: 1

      Presumably you weren't familiar with Emitter Coupled Logic (ECL, pronounced "Ek-el") during the same era. I remember looking at ECL signals on an oscilloscope and observing how "beautifully" (or "cleanly") they transitioned their logic states--fascinating, and it also inspired confidence that reliability could be achieved at very high speed switching speeds.

    31. Re:Number of components, not computing power by vux984 · · Score: 2

      I know you said that it shouldn't be I/O, but I would still bet money that if you put an SSD in there you'd notice a dramatic improvement. (Although, you didn't mention RAM usage, but even then the SSD would help since it would speed up swap.)

      However, when I observe PCs stall with no significant cpu activity and no disk activity... if it were thrashing ram there should be disk activity. No, those stalls have got to be something else.

      Personally, though, yes, an SSD is my next upgrade, and I agree with you that I hope and expect to see a dramatic difference in load times, boot times and other io intensive stuff, but I don't think the stalls I'm complaining here about are related.

      One source of stalls that I am aware of are networking related. I've seen lots of stuff choke badly trying to reach servers that aren't reachable, where it just stalls the entire UI of an app while it waits for some network query to timeout. That accounts for some of them, but I'm still head scratching why it stalls in a number of other cases where there shouldn't be any networking dependency/functionality.

    32. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      Since when can't you call someone a troll for telling you the truth? ~

      mod parent troll... he speaks the truth

    33. Re:Number of components, not computing power by bertok · · Score: 1

      Instead, because of bloat, we're stuck running yesterday's software with tomorrow's hardware.

      Bullshit!

      You're still using a mechanical hard-disk, right? That's the component that's bottle-necking your PC, not programmers!

      Get an SSD to find out what your CPU and your "bloated" software is capable of.

      On my old laptop, with an old 2.6 GHz Core 2 Duo CPU, which is several generations older than the CPU in the article, if I double-click the Word 2010 icon, it launches instantly. Not after a second or two, instantly. It's like notepad. I get the pretty transparent window borders, the ribbon, font-smoothing, everything. How is that "bloated"?

      I checked it too: Starting up Word 2010 takes ~400ms of processor time, total. It doesn't even show up in the Task Manager, I had to use SysInternals Process Explorer!

      Acrobat Reader, the "horribly bloated" application that most people hate for being slow? It also launches instantly, and uses a massive 180ms of processor time. It's eating up my CPU! Oh wait... it's not.

    34. Re:Number of components, not computing power by rwa2 · · Score: 1

      Moore's law is dead in everything except transistor count.

      Here's the picture I was looking for, smack in the middle of:
      http://www.gotw.ca/publications/concurrency-ddj.htm

      Above 4Ghz, the power loss due to transistor current leakage suddenly starts going way up and becomes the most significant term.

      It will take a fundamental change in the way we build transistors to get any kind of efficiency above 4Ghz... maybe photonic or micromechanical gates.

    35. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      You are comparing software start-up time to code efficiency.

      Efficient code would allow you to run the exact same software (from your point of view) on a 1GHz single-core CPU.

    36. Re:Number of components, not computing power by peragrin · · Score: 2

      On my work computer adobe acrobat takes 10-25 seconds to load. yesterday i tried to print a single page from the middle of a PDF and it took a good 10 minutes to process it., but only 5 seconds to actually print it when windows finally had control of the file. The processor wasn't loaded it is just that adobe acrobat is a piece of shit software.

      Hard drives are one of two bottlenecks in current computers the other is RAM. RAM tends to be several clock cycles behind the processor. This is why I have high hopes for memresistors, if you can move the HD into RAM you can have a massive speed increase. of course all software will have to be rewritten, but that is besides the point.

      --
      i thought once I was found, but it was only a dream.
    37. Re:Number of components, not computing power by vux984 · · Score: 1

      It really is, if you have software that takes advantage of all those core.

      And if that is the only software you use. Otherwise you get a performance increase in one or two activities, for a net increase in total performance, that is distinctly less than DOUBLE.

      There are many other examples like mine that show overall performance is increasing. Even games now benefit from more cores, although 4 is about the limit of increasing performance for most current titles.

      Yes, overall performance is definitely increasing. No argument. But its not doubling anymore. Its doubling when you do X task, with Y software. But u,v, and w are only 18% faster, so if you spend your time split evenly between u,v,w,x you are seeing 38% increase overall... or however it works out for you.

      It used to be you bought a new PC and it was twice as fast as your old one. 100% faster accross the board, and the new [hardware feature like MMX] made task X with Y software 150% faster than your old PC.

      Besides my current PC is an i7 920, launched in Q4'08. Its 2 years later now. What can I buy that's twice as fast for the same price I paid 2 years ago? (~$350 iirc)?

      Even spending 3x as much, and getting a top of line 6 core, I'm still not seeing 100% performance increase at anything, let alone accross the board. At best I'll see a 50-70% increase a couple specific applications? That's at BEST, and at triple the price point.

    38. Re:Number of components, not computing power by mikael_j · · Score: 1

      You're still using a mechanical hard-disk, right? That's the component that's bottle-necking your PC, not programmers!

      Actually, if you're having performance issues on a modern computer that are solved by swapping out your system/application disk with an SSD chances are your real problem is that you're low on RAM.

      The issue most people have is that they're using all of their RAM or close to all of it with just their active applications (active here meaning "the window at the top, those other apps that are running are all swapped out") so every time they hit alt-tab/cmd-tab or start another app the disk starts churning like crazy. Or maybe they just entered a menu that belongs to a part of the app that's been swapped out because the OS decided that it hadn't been used for 30 seconds (one of my main issues with Windows btw, it will do this even when there should be plenty of available RAM because apparently disk caching of apps that haven't been started in days or weeks is clearly more important than the currently active app not grinding to a halt).

      --
      Greylisting is to SMTP as NAT is to IPv4
    39. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      Doubling clock rate will probably double the performance of almost any software that runs in the computer

      I/O Bound, Interactive and other software depending on any sort of hardware will disagree. What I mean is, your hard-drive wont speed up, your typing speed wont double, your internet connection wont double, your printer/scanner/other wont double.

      In the end most single-threaded programs will have to wait for I/O and wont benefit as much from a faster CPU as you might think. Only computation intensive programs would.

    40. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      Have you tried Ubuntu Linux?
      I bought eight gigs of ram and noticed I rarely use over 700mb even with no swap file as I don't want my solid state hard drive to wear out.

    41. Re:Number of components, not computing power by bertok · · Score: 1

      On my work computer...

      I'll stop you right there. It has a mechanical drive, right?

      Think about that for a second. You've got a solid state processor with hundreds of millions of parts switching billions of times per second waiting on... a single, moving, mechanical part that can't exceed about a hundred movements per second.

      Your computer's mechanical hard disk has a latency about a million times higher than your computer's processor or memory!

      Mechanical disk performance has not improved in over a decade! Ignore the benchmarks about streaming throughput, that's irrelevant to real-world performance. What hasn't changed is the latency and the random IOPS.

      The SSD I have in my laptop now can do 60,000 random 4KB reads per second, with a latency under 100ms. If you think about it, that's still glacially slow compared to the processor. Ideally, the latency should be a few microseconds, which is what you'd expect for a 4KB transfer on a high-bandwidth link, so there's still a long way to go before disks have "caught up" to the rest of the PC.

      You may as well be running software off floppies or tape, and whine about how it takes forever to spool back and forth when you use your software.

      On my computer, practically nothing makes me wait, or if I have to wait, it's because real heavy-weight computation is taking place. Even then, if I switch to another program, the alt-tab transition is instant, and all the other software remains perfectly responsive while I wait.

    42. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      When is slashdot going to quit talking about Moore's law every two months?

    43. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      I am sure a certified and civil engineer like yourself can provide all the lift and support I need in my endeavors.

    44. Re:Number of components, not computing power by bertok · · Score: 1

      You are comparing software start-up time to code efficiency.

      Efficient code would allow you to run the exact same software (from your point of view) on a 1GHz single-core CPU.

      It's a valid comparison. The startup of Word is mostly single-threaded, and my CPU is 2.6 GHz, so on a 1 Ghz processor that measurement of 0.4 seconds would be... about 1 second. Oh no.. the horror! I'd have to wait an entire second to launch one of the most complex pieces of software on my computer.

      Processors have been getting steadily faster, but most people's perception of their computer's speed has been completely dominated by the disk speed, so they haven't noticed.

      When my customers complain about how "computers are so slow" I like to do a little demo for them using Mathematica, which is something I used to use at Uni, and still have installed in case I need it. I usually demonstrate it computing Pi to 1 million places in about a second, or symbolically integrating some complex equation instantly where the output is five screenfuls of hideously complex looking maths. Puts things in perspective for them.

    45. Re:Number of components, not computing power by Kevin+Stevens · · Score: 1

      Probably because your spreadsheet has updated at the same rate for the past 15 years- instantaneously.

      I can tell you that my number one cycle killer that I actually wait on has reduced tremendously over time- compiling. There was an XKCD on this, but back in the day, even for smallish projects, for a full build you would go and get coffee, probably even lunch, and possibly just went home for the day or bothered your coworkers (how far we have come from the days of P4 when a process could peg your computer!). A good deal of those reduced times come from better compiler technology, better code practices, and even better languages (IE C++-> Java/C#), but I am still doing C++, and doing full builds on the same size large systems I was working on 10 years ago now only call for a trip to the bathroom, and maybe a cup of coffee, though due to the wonders of multi-core machines, it is not a problem to surf /. and compile.

    46. Re:Number of components, not computing power by icebike · · Score: 1

      Kernel compiles were my benchmark. Yes, they seem faster now, but not relative to the increase in processing speed claimed by the newer machines.

      But I suspect almost all of the improvements in that arena came from faster IO, faster disks, bigger memory for file buffers, etc.

      --
      Sig Battery depleted. Reverting to safe mode.
    47. Re:Number of components, not computing power by TooMuchToDo · · Score: 1

      I think you'll see the move to photonics, with in silica light generation/detection used to push bits around. No voltage leakage, no heat issues (ergo, more reliable/longer lasting equipment). Intel is well on it's way with Light Peak.

    48. Re:Number of components, not computing power by SecurityGuy · · Score: 3, Insightful

      I'd have to wait an entire second to launch one of the most complex pieces of software on my computer.

      I think you just refuted your own point. The most complex piece of software on your computer is a word processor. That's the problem. Things which are conceptually simple have become so monstrously bloated that they're now "complex software".

    49. Re:Number of components, not computing power by Jeff+DeMaagd · · Score: 3, Insightful

      That's sometimes true, the trouble is that I'm finding software is often less reliable and slower than the same kind of software a decade ago. More maintainable code should mean that the product is more reliable. I don't see where security necessarily yields terribly slower software and much larger file sizes, unless you mean constant malware scanning. Software available today isn't necessarily more usable to novices or the experienced, so the suggestion of a better interface doesn't necessarily hold true.

    50. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      Um, you need to lurk moar. Last discussion of Moore's Law was 2 months ago, next one is scheduled for February 2. By Easter it'll be every single post.

    51. Re:Number of components, not computing power by samkass · · Score: 1

      I'm often modded troll when I claim that every advancement in computer processing power has been absorbed by look and feel of the OS interface.

      To put it another way, all the processing power recently has been put toward making computers more accessible and engaging to people and feel like actual appliances instead of obscure gadgets. Sign me up!

      However, I don't think you're looking at the whole picture. A typical data center's 32-core powerhouses aren't rendering GUIs. The client machines spend their additional cycles making things look better while the servers spend their additional cycles crunching additional data. Again, I don't seem to have the same problem with this that you do.

      --
      E pluribus unum
    52. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      Adding components is easy. Making faster computers is not.

      Anyone can build a fast CPU. The trick is to build a fast system.
                      -- Seymour Cray

    53. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      Recalculating the spreadsheet (or just about any other real work) seemingly takes just as long (short?) as ever.

      I know its not provably true, but it sure seems that way.

      Certain specialized tasks which avoid OS and user interface bloat are noticeably faster now. As a grad student in the early 90's I would setup some computationally intensive processing before going home each night. They would take 8-10 hours to run. Now doing bigger jobs of the same type takes seconds. Some of it is having much more RAM, but that is one area where the additional computing power is very visible.

    54. Re:Number of components, not computing power by bertok · · Score: 1

      I'd have to wait an entire second to launch one of the most complex pieces of software on my computer.

      I think you just refuted your own point. The most complex piece of software on your computer is a word processor. That's the problem. Things which are conceptually simple have become so monstrously bloated that they're now "complex software".

      How is it "conceptually simple"?

      Just because it's a common task that a lay person can understand doesn't make any of the required software complexity magically go away.

      Consider just the capability of handling multiple languages. That is practically mandatory for 50% of the world population (maybe not you, but not the entire world is the United States). To handle Unicode alone, ignoring all the other legacy encodings, requires that the software do all of the following, in real-time:

      - Handle 60,000+ code points
      - Load multiple fonts and map code points to glyphs. The mapping tables alone required several megabytes of memory.
      - Display text left-to-right and right-to-left, including mixed directions with justification, etc...
      - Load and handle the kerning information for all of those characters, and all their combinations.
      - Handle advanced typography features required by some languages like ligatures and context-sensitive glyph selection.
      - Handle input method editors to allow users to enter text where there are more characters than keys, like Chinese and Japanese.
      - Display all of that even with per-character styling, like colours and sizes.

      Just think for a moment how insanely complex something as trivial as the "selection highlight" is when it has to handle anti-aliased formatted text that's a mix of left-to-right and right-to-left text using ligatures. Arabic text embedded in English text is a good example.

      That's just text entry. Then there's spelling and grammar checking, localisation issues like date and number formatting, lexicographical sorting, and the list goes on.

      A word processor is just about the most complex piece of software most normal users ever run. Practically everything else on an ordinary office PC is simpler.

      As a comparison, most developer IDEs use fixed point text, and many do not support Unicode, none support justification, multiple columns, tables, or any advanced layout at all. You "think" of it as more complex because you use it for more complex tasks, but the software is much simpler internally. It's possible to write a simple compiler from scratch in a day, and I've written a simple real-time syntax highlighting code editor in under a week.

      I bet you would struggle to write a text box control (let alone a word processor) with full internationalisation support, from scratch, in under a year. There's no practical way to do so with less than 5 MB of code & data, because the font and Unicode tables are that big alone. The input method editor lookup tables are also quite large, and the code behind them is very complex.

    55. Re:Number of components, not computing power by eggnoglatte · · Score: 1

      Moore's law never was about performance. He predicted the doubling of transistors per unit area over a give time period. In the past a side effect has been that the smaller transistors could also be clocked faster. That is no longer the case, but the original Moore's law still holds.

    56. Re:Number of components, not computing power by drsmithy · · Score: 1

      The most complex piece of software on your computer is a word processor. That's the problem. Things which are conceptually simple have become so monstrously bloated that they're now "complex software".

      A word processor - particularly a WYSIWYG word processor - is a complex piece of software, and always has been.

      Even something ancient like WordPerfect 5.1, is far from "conceptually simple".

    57. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      I think the number of times Moore's Law gets mentioned on Slashdot doubles every 18 months.

    58. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      and the progress bar is just sitting there... literally 20-30 seconds later things start happening again... WHAT THE HELL? What are the possible bottlenecks that cause this?

      The obvious suspect would be network...sometimes stuff phones home/checks for an update. Networking often has timeouts measured in seconds which would explain the apparent lack of activity and then the sudden return to life.

      Poorly-written multithreaded coded could also exhibit that behavior (i.e. crap we're getting a deadlock...adding a sleep for 30 seconds to allow the other thread(s) to finish is easier than communicating correctly between the two threads.)

    59. Re:Number of components, not computing power by guruevi · · Score: 2

      Deadlocks, badly implemented (blocking) loops, blocking or slow IPC, blocking file io (where it has to wait for the hard drive to return confirmation of the write), waiting on interrupts from various sources, exhausted entropy etc. etc.

      There are a lot of things that programmers and compilers do wrong. There are a lot of things that can't be parallelized yet and there is a lot of contention over a few limited resources (RAM, hard drive, external IO) which makes a computer slow.

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    60. Re:Number of components, not computing power by CapOblivious2010 · · Score: 1

      Does word still install the "quick-start" option? And didn't acrobat do something similar at one point?

      It's the oldest trick in the book: make users pay at OS startup time, instead of app startup time, and they'll think the app is fast and the OS is slow... when what's really happening is they're paying for the startup at every boot, regardless of whether they ever actually use the app, and it's soaking up RAM the whole time. Win/win for everyone! (well, except the user)

    61. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      You mean like how back in the day you had 32 megs of RAM using Windows, with a 100MHz processor, and you could pile on a new program and the computer would swap 50 megs to disk, and tick along just fine mostly?

      I remember Netscape Navigator 2.x taking several minutes to start on a 100 MHz processor with 24 MB of RAM. (Not sure how much faster it would have been with 32 MB. I think the HDD must have been the bottleneck anyway. It took less than a minute to restart Netscape when it crashed.) Anyway, it was long enough to go to the kitchen and boil some water and make a cup of tea.

      Firefox 3.6 starts in less than five seconds on my 2.1 GHz dual core CPU and 4 GB of RAM.

    62. Re:Number of components, not computing power by TheLink · · Score: 1

      However, when I observe PCs stall with no significant cpu activity and no disk activity... if it were thrashing ram there should be disk activity. No, those stalls have got to be something else.

      Checking for online updates? Or commands from the bot master? :p

      Another thing is most timeouts are set on a human scale: e.g. seconds or even minutes.

      Sometimes there are good reasons for this. Whatever they are, in many cases it means that if there is an exception you have to wait for a human scale interval, in some cases you have to wait even if there are no exceptions ( pauses just in case a human wants to override something, or to show stuff to the human - splashpage or eyecandy UI animation).

      --
    63. Re:Number of components, not computing power by Dutch+Gun · · Score: 1

      Programming tasks often seem trivial to those who don't actually have to do them.

      A programmer I once worked with drove me nuts when any task he didn't have to do should "only take a few minutes". At one point, being unfamiliar with the system he set up, I got his help on the problem, and lo-and-behold, a few minutes turned into half a day of work...

      --
      Irony: Agile development has too much intertia to be abandoned now.
    64. Re:Number of components, not computing power by Omestes · · Score: 1

      And nowadays we have 4 gigs of RAM, and the computer uses 500 megs of swap and every time you alt-tab you have to wait 4-5 seconds for everything to load back into RAM as windows slowly get redrawn, and everything runs slow... but wait! Developers are piling more and more on, since there's 4 gigs of RAM then EVERY program can use 2-3 gigs of RAM, and now... yes! 6 gigs of swap, and a computer that barely runs at all with 6 8 core processors!

      What OS are you running? I have around 6 gigs of RAM and hardly ever swap, much less experience churn, actually I hardly ever hit 4 gigs utilized outside of having a large amount of browser windows open while processing a hefty RAW image in Photoshop. The only genre of software that ever chokes up my computer is browsers, mostly. Firefox does nasty things, and Chrome is a bit better but still would perform unacceptably if it was anything else but a browser. Yes, this computer is a bit of a workhorse (quad-core PhenomII@3.4GHz, 6GB Ram), but even my older Core 2 Duos run pretty much everything fine, without any of the symptoms you list.

      The only computers I have that experience any real issues with modern software is an old Mac Mini (first generation Intel, upgraded to a 1.8GHz Core 2 Duo, and 2GB of memory), and a Zotec nettop HTPC running some little Atom dual core, with an ION gfx chip, running Ubuntu. Both of these are old and a bit underpowered, and I suspect that both of them run into issues more because of shoddy graphics chips, than actual hardware.

      It does annoy me that most programs still can't use half my cores, though.

      --
      A patriot must always be ready to defend his country against his government. -edward abbey
    65. Re:Number of components, not computing power by bertok · · Score: 1

      You're still using a mechanical hard-disk, right? That's the component that's bottle-necking your PC, not programmers!

      Actually, if you're having performance issues on a modern computer that are solved by swapping out your system/application disk with an SSD chances are your real problem is that you're low on RAM.

      I have 8 GB in my laptop, and 24 GB in my desktop. Both became massively faster with an SSD.

      There's other IO activity that goes on that isn't effectively cached, even on a 64-bit operating system.

      Cache does nothing for boot times, first-time application launch, opening a document for the first time, etc...

    66. Re:Number of components, not computing power by mikael_j · · Score: 1

      Well, it is true that there are plenty of things that aren't helped by having more RAM.

      I was thinking in a more general sense. Ever since the late 90s I've seen way too many users, both "regular people" and people who should know better, who have nowhere near the amount of RAM they should have.

      For most people it seems RAM is still the main bottleneck when it comes to getting decent performance, and there's really no reason for this anymore. Back in the days when a 4 MB SIMM would cost as much as a netbook loaded with 2 GB costs these days RAM shortage was just something you had to live with but it's 2011 now, you can get a couple of 2 GB DIMMs for well under $100.

      Still, most people seem more willing to spend their money on an SSD than on more RAM even though they'd get more of a performance boost from more RAM. Not that I don't use SSDs, I just think it's an unnecessary expense for those who use it to compensate for not having enough RAM.

      --
      Greylisting is to SMTP as NAT is to IPv4
    67. Re:Number of components, not computing power by sznupi · · Score: 1

      To put it another way, all the processing power recently has been put toward making computers more accessible and engaging to people and feel like actual appliances instead of obscure gadgets. Sign me up!

      Don't forget to mention how, if one were to single out a machine which currently best fits such description, it would be probably the iPad. Or, generally, many smartphones. With processing power a decade "behind".

      --
      One that hath name thou can not otter
    68. Re:Number of components, not computing power by rdebath · · Score: 1

      You think you're joking, but in Windows a lot of the GUI stuff depends on timer ticks and it's very easy to end up waiting for the next tick. So it doesn't matter how fast the CPU is, some jobs will take exactly the same time.

      Possibly the worst part of this is that for "windows task manager" the CPU time taken by these timer tick tasks is invisible. The tick is assigned to whatever task is running at the end of the timer tick and these tasks must not run that long because they'll run into their next start time. Occasionally this can mean that 90% of the CPU time is just 'lost'.

      Still a 20-30 second wait is likely to be the result of caching (indexing?), a machine on the network is assumed to still exist, but it was turned off six months ago...

    69. Re:Number of components, not computing power by Carewolf · · Score: 1

      Adding components is easy. Making faster computers is not.

      Well, thank god Moore's Law only states the number of transistors double every 18 months, and says NOTHING about speed?

    70. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      Aahhhh... Extrapolation. That will always give meaningful results.

    71. Re:Number of components, not computing power by bluefoxlucid · · Score: 1

      I remember running Wingroove and having software MIDI wavetable emulation on 64MB of RAM and a 200MHz Pentium with MMX technology; and playing Quake a LOT on Windows 98. 64MB was HUGE.

    72. Re:Number of components, not computing power by bluefoxlucid · · Score: 1

      What OS are you running? I have around 6 gigs of RAM and hardly ever swap, much less experience churn, actually I hardly ever hit 4 gigs utilized outside of having a large amount of browser windows open while processing a hefty RAW image in Photoshop.

      Ubuntu Linux, Gnome, to desktop in about a gig (not counting cache/buffers), Thunderbird, Chromium, Rhythmbox, Xchat-Gnome, Pidgin, a terminal... usually I don't have OpenOffice.org open because holy crap.

    73. Re:Number of components, not computing power by Stooshie · · Score: 1

      What exactly do you mean by bloat? Do you mean software that is badly written (e.g. they could have exited that loop when the condition was met rather than loop round everything) or do you mean changes to the Look and Feel of the OS (Which, in my opinion, are improvements and not bloat)?

      --
      America, Home of the Brave. ... .and the Squaw.
    74. Re:Number of components, not computing power by Stooshie · · Score: 1

      Moore's law was always about transistor count and only about transistor count!

      --
      America, Home of the Brave. ... .and the Squaw.
    75. Re:Number of components, not computing power by Stooshie · · Score: 1

      Also, Naysayers have always predicted the end of advancements!

      --
      America, Home of the Brave. ... .and the Squaw.
    76. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      What OS are you running? I have around 6 gigs of RAM and hardly ever swap, much less experience churn, actually I hardly ever hit 4 gigs utilized outside of having a large amount of browser windows open while processing a hefty RAW image in Photoshop.

      Ubuntu Linux, Gnome, to desktop in about a gig (not counting cache/buffers), Thunderbird, Chromium, Rhythmbox, Xchat-Gnome, Pidgin, a terminal... usually I don't have OpenOffice.org open because holy crap.

      Yeah, you have a point there. Open office and the browser Flash plugin are terrible in Linux. (They are terrible in Windows 7 too, but not quite as terrible.)

      But overall, flash pages in 2010 are faster than the average Shockwave (or whatever ir was) page in 2000. Open Office in 2010 is faster than MS Word was in 2000.

      There is too much bloat and too little optimization in software, but despite that hardware is winning over software bloat over time.

    77. Re:Number of components, not computing power by Omestes · · Score: 1

      A lot of that is, sadly, Linux. Don't get me wrong, I love Linux, and currently have two computers with some flavor of Linux as the sole OS (OpenSuse and Ubuntu), but they often churn much worse than my Win7 or OS X boxes, regardless of the OS being less resource hungry. I blame half-assed support, Flash, terrible driver hacks.

      Its now 2011, and Linux still really can barely handle full screen flash (much less something like Hulu) on most configurations.

      With both of my Linux computers, I know damn well that if I installed a flavor of Windows (even Vista... grrr) they would run a bit better. This pains me. And oddly, Ubuntu (and now OpenSuse) runs better on my underpowered, almost 10 year old lap-top, than on the technically superior and more modern Nettop.

      --
      A patriot must always be ready to defend his country against his government. -edward abbey
    78. Re:Number of components, not computing power by bluefoxlucid · · Score: 1

      Actually, proper accelerated graphics in X11 work rather well. VLC and Totem/gstreamer etc work, but Flash is still horrible trying to get SOUND right. I'll pull down Flash FLVs and play them in Totem locally better than Youtube can with Adobe's flash player.

    79. Re:Number of components, not computing power by Omestes · · Score: 1

      I haven't noticed many problems with Flash's sound on either of my Linux boxes. full screen Flash video, on the other hand, sucks. On my Atom/ION2 box full screen streaming Flash is almost completely unplayable. It sucks in both Firefox and Chrome, even when downgrading Flash to 9.xx. The Hulu client completely chokes (which is near 100% Flash, AFAIK). Oddly Boxee works almost perfectly, outside of some choking from HD content from only CBS.

      No issues with Youtube in either Chrome or Firefox, though.

      This is one huge problem I've had trying to fix anything Flash or video related on Linux... There is no one problem common to 100% of the population, but 100% of the population has a problem. You might have perfect video, but bugged sound, and I have the exact opposite. Even with identical symptoms, one fix will work for some people, but not others.

      Hell, I've been trying to get sound through HDMI on my HTPC for a year now, even though people with identical hardware have managed it, following their steps exactly has done nothing for me.

      --
      A patriot must always be ready to defend his country against his government. -edward abbey
    80. Re:Number of components, not computing power by bluefoxlucid · · Score: 1

      No, video on flash sucks on linux, I don't have perfect video. But try this: Firefox for Windows, under Wine, with Flash for Windows. Try it. Try it and see what happens.

    81. Re:Number of components, not computing power by owlstead · · Score: 1

      Well, if you work in a managed software environment you get things like memory protection, where you can't do pointer arithmetic and have to be in bounds. That kind of work more or less requires a VM, which incorporates a slow down - or at least a latency issue.

      If you have things like reflection, you need to store the method names and class names in memory. You get great stack traces in return if you ever run into trouble when you are in production in return.

      If you use unbounded integers (ones that don't round robin you into trouble) then your software will need to grow them and perform additional commands to make everything work.

      If you have modules, you will need to load them separately. If you have modules and services you will have to verify, load and start them.

      More secure software does mean overhead, although a well designed application should behave slower, but not *exponentially* slower. So we should be alright.

      And you are wrong: software is much more functional and reliable nowadays, we just tend to forget the mistakes from the past and substitute a better yesterday in return. We *could* do much much better though.

    82. Re:Number of components, not computing power by owlstead · · Score: 1

      I've found out that it is amazing how fast programmers-turned-managers can forget how quickly something can become hard.

      I've just had to do a bit of programming, but I had to get a new IDE/API first. It turned out that required a newer version of Eclipse, so I started to convert parts of my old workspace to this new version. Zap, half a day gone. Add a few network issues, a McAfee that inserts minutes into every edit, a new-year speech of the CEO, a few issues around other software packages....

      Yeah, the update just takes half an hour. Getting it done can still take a week. Maybe those hours are not all spent on the project, but they take away time none-the-less. If you ever get a project manager that does not understand software time tables, hide, move or - if possible - get him of the project!

      Other programmers often understate things too, but they can be worked around. If they are really irritating, give them the job. If they perform well, great. I'm not afraid of programmers that perform better than I do. If not, they've learned a good lesson. Beware design and code quality though.

    83. Re:Number of components, not computing power by toddestan · · Score: 1

      I have an SSD, and while it does help with a lot of things, I get this too occasionally and it is rather mysterious, though I have a sneaking suspicion that it has to do with my secondary 1.5 TB Seagate drives. One thing to check with Vista and Windows 7 in task manager is to make sure you press the "Show processes from all users", otherwise if it's a system process that's hogging all the CPU time you may not see it. Also, if you have Readyboost enabled check that it is not thrashing the USB drive.

    84. Re:Number of components, not computing power by rdnetto · · Score: 1

      There's no good reason why a PDF reader or a CD/DVD burner should be in the 0.1-1 GB range.

      --
      Most human behaviour can be explained in terms of identity.
    85. Re:Number of components, not computing power by Anonymous Coward · · Score: 0

      That phenomenon is called "Wirth's law" ( Software is getting slower more rapidly than hardware becomes faster)

      I tried to avoid that by being very picky about the software i use. That means a Linus OS with fast window manager. And using apps that are written in c/c++. Puppy linux is a good example of that. Small, fully featured and running in ram.

  2. Virus? by Anonymous Coward · · Score: 1, Insightful

    lodging hold like a stubborn computer virus you just can't eradicate

    Stop using Microsoft Windows.

  3. A Better Question: by justin.r.s. · · Score: 5, Insightful

    45 Years Later, Does Moore's Law Still Matter?
    Seriously, hardware is always getting faster. Why do we need a law that states this? Which is a more likely scenario for Intel: "Ok, we need to make our chips faster because of some ancient arbitrary rule of thumb for hardware speed.", or "Ok, we need to make our chips faster because if we don't, AMD will overtake us and we'll lose money."?

    1. Re:A Better Question: by __aapopf3474 · · Score: 2

      Agreed. When watching a presentation, I have a corollary to Moore's Law, where if a slide mentions Moore's Law and has "the graph", then it is ok to ignore that slide and the following two slides because no new information will be transmitted. It is like a nicer (and temporary) version of Godwin's Law.

    2. Re:A Better Question: by kenrblan · · Score: 4, Interesting

      Well said. I was about to post the same question. The progress definitely matters, but the prediction is really not much more than an engineering goal at this point. That goal is secondary to the goal of remaining the market leader. Without intending to start a flame war, I wish the programming side of computing was as interested in making things smaller and faster in code. Sure, there are plenty of academically oriented people working on it, but in practice it seems that most large software vendors lean on the crutch of improved hardware rather than writing tight code that is well optimized. Examples include Adobe, Microsoft, et al.

      --
      Make everything as simple as possible, but not simpler. - Albert Einstein
    3. Re:A Better Question: by alvinrod · · Score: 4, Informative

      Funny you should say that as there was a /. story not terribly long ago about how algorithm improvements have improved beyond hardware.

      The problem with products from Adobe and Microsoft is that the codebase is massive and it can be a pain to fix and optimize one part without breaking something else. Software vendors deal with the same issue of needing to be faster than the competitor as Intel/AMD. If Adobe and Microsoft don't, I think it speaks more to the lack of competition in some of their product areas than it does to simply being lazy.

    4. Re:A Better Question: by avandesande · · Score: 1

      Yes, I think it does matter, because eventually the law will 'fail'.
      I have no idea at what point that will come but it will certainly be an important inflection point for technology.

      --
      love is just extroverted narcissism
    5. Re:A Better Question: by flonker · · Score: 1

      The utility of Moore's Law is not that "hardware is always getting faster", but rather, it is a good rule of thumb for the specific rate of change.

      You can also throw in "transistor count != speed", but that's been beaten to death already.

    6. Re:A Better Question: by Anonymous Coward · · Score: 0

      Poor software performance is a result of both lazy programmers and the fact that people worry about optimizing "too early". The fact is, you have to think about performance from the beginning, it can't be left to be done after the system has been designed and built. It's damn hard to optimize after the fact even though it doesn't look that way. This problem is compounded by the fact that "smart" and experienced people (teachers, even managers that used to be programmers) think you should save optimization for later.

    7. Re:A Better Question: by houghi · · Score: 2

      but the prediction is really not much more than an engineering goal at this point

      No, it is a prediction, not a goal. There is a HUGE difference between the two. The worst that could happen (pr the best) is that it becomes a self fulfilling prophecy.
      If they get there, they stop trying as they reached the prophecy.
      If they do not get there, they will try harder to reach the prophecy.

      Now the question is if the self fulfilling prophecy speeds up the process or slows it down in the long term.

      --
      Don't fight for your country, if your country does not fight for you.
    8. Re:A Better Question: by epte · · Score: 5, Insightful

      My understanding was that the prediction was indeed important, for inter-business communication. Say, for example that a company purchases cpus from a vendor, for use in its product when it releases two years from now. The product development team will shoot for the expected specs on the cpus at that future date, so that the product will be current when it hits the market. Such predictability is very important for some.

    9. Re:A Better Question: by hedwards · · Score: 4, Informative

      Don't be stupid. AMD did overtake Intel on a couple occasions and the response most recently was to bribe companies not to integrate AMD chips into their computers.

    10. Re:A Better Question: by HelloKitty2 · · Score: 1

      It seems more reasonable business-wise to follow this rule than just create and release a 1000 core CPU today, and the company has no new products and tons of competitors tomorrow.

    11. Re:A Better Question: by mangu · · Score: 2

      If they get there, they stop trying as they reached the prophecy.
      If they do not get there, they will try harder to reach the prophecy.

      Now the question is if the self fulfilling prophecy speeds up the process or slows it down in the long term.

      Let's try it out:

      -"Boss, I have this fantastic idea for a chip that will have ten times more components than the ones we have today".
      -"No way! That would violate Moore's Law, make it just twice the number of components!"

      No, I don't think Moore's Law is slowing down progress.

    12. Re:A Better Question: by JustinOpinion · · Score: 1

      Without intending to start a flame war, I wish the programming side of computing was as interested in making things smaller and faster in code.

      I don't think it's as bad as all that. Believe me, I would love it if all the software I used were trimmed-down and brilliantly optimized. There is indeed quite a lot of software that is bloated and slow. But it really just comes down to value propositions: is it worth the effort (in programming time, testing, etc.)? For companies, it comes down to whether making the software faster will bring in more sales. For many products, it won't bring in new sales (as compared to adding some new feature), so they don't bother.

      But in places where it does matter, there actually is some good competition. In browser rendering, for instance, the big players are all competing to improve performance (e.g. Mozilla). Think even of something as horribly inefficient as Adobe Acrobat Reader... It's inefficiency has in fact led to the creation of lighter-weight alternatives (e.g. Sumatra or FoxIt). Another example is in graphics: there are all kinds of brilliant and powerful algorithms and optimizations working in modern software to make the slick graphics we now take for granted.

      In an ideal world, every piece of software would be crafted to perfection, and would ship as a perfectly secure, extremely small chunk of code that runs blazingly fast because of the thousands of meticulous assembly-level optimizations that were performed. Reality falls short. But, on the other hand, our modern computers are really quite functional and fast. So I would say we should keep putting pressure on vendors to ship faster software, to the extent that we notice the slowness and it bothers us... but we should also acknowledge the real effort that is going into optimization all the time.

    13. Re:A Better Question: by RandCraw · · Score: 2

      Fact is, software development has relied on exponential hardware speedup for the last 40 years, and that's why Moore's Law *is* still relevant.

      If a global computer speed limit is nigh then mainstream computing will slowly decelerate. Why? 1) Perpetual increase of bloat in apps, OSes, and programming languages. 2) Ever more layers of security (e.g. data encryption and the verification & validation of function calls, data structures, and even instructions). 3) Increasing demands of interactivity (e.g. event polling of network & GUI & the explosion of sensors).

      The care, feeding, and survival and all of this crap depends on a nonstop increase in hardware horsepower. If hardware no longer improves (regardless of whether it was due to transistor density, clock speed, or microarchitecture design), the effect is the same -- computers won't keep up with the rising demands on them, and they will slow down.

      In fact, Moore's Law died the minute that multicore CPUs were announced as its heir apparent. Parallelism has always been the last ditch solution to hardware speedup. (Amdahl's Law is a harsh mistress). Parallel CPUs have been available forever and were mercifully avoidable as long as clock speeds multiplied. But when CPU Hz topped out at around 3 billion (around 2003), the hardware pros knew the party was over.

      Moore's Law, RIP.

    14. Re:A Better Question: by TheRaven64 · · Score: 1

      Actually, it's important for intra-business communication too. Intel takes around five years to bring a chip to market. First, marketing works out what kind of chip will be in demand in five years, and roughly how much they will be able to sell it for. They produce some approximate requirements and the design team starts work. In the meantime, the process team works on increasing the number of transistors that they can fit on a chip, improving yields, and so on.

      At the end of the five years, they produce the chip that the design team came up with. The cost of production depends on the number of transistors that the design team used and the amount of progress that the process team has made in this time.

      It is incredibly important for the design team to have an accurate prediction of their transistor budget early on. If they get this guess wrong, then they end up with a chip that's too expensive to produce, or one that uses fewer transistors than it could (for the target market segment) and underperforms.

      Intel made bad predictions a couple of times. I had the opportunity to talk to the lead designer on the Pentium 4 team, which suffered from two bad predictions. The first was marketing not realising that power consumption was becoming an important factor, so fast-clock-at-all-costs was not the correct design goal. The second was the belief that they'd be able to ramp the clock speed up to 10GHz by the 'tock' cycle of the NetBurst architecture's lifecycle (they didn't even hit 4GHz).

      --
      I am TheRaven on Soylent News
    15. Re:A Better Question: by rawler · · Score: 1

      It does, since something needs to counter the increasing sluggishness of software.

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

    16. Re:A Better Question: by tlhIngan · · Score: 1

      45 Years Later, Does Moore's Law Still Matter?
      Seriously, hardware is always getting faster. Why do we need a law that states this? Which is a more likely scenario for Intel: "Ok, we need to make our chips faster because of some ancient arbitrary rule of thumb for hardware speed.", or "Ok, we need to make our chips faster because if we don't, AMD will overtake us and we'll lose money."?

      Actually, Moore's law does not imply anything about computing power. It says that the number of transistors doubles every 18 months or so. A billion transistors? That's not a lot - your 4GB MLC storage card has easily 2 billion transistors on it for the storage array.

      Also, random logic blocks like that in a CPU are not the most transistor-dense things out there - memory is. Whether it's SRAM, DRAM, or flash, a memory device is always silicon-area limited. In fact, a majority of those transistors are probably used for memory blocks (caches etc).

      The good thing with Moore's Law is that it means storage will double every 18 months or so, so cheaper SSDs for all.

    17. Re:A Better Question: by Fulcrum+of+Evil · · Score: 1

      I wish the programming side of computing was as interested in making things smaller and faster in code.

      They are, just not everywhere. There just aren't that many people who care about how fast their spreadsheet is any more, and it isn't nearly as profitable to get devs optimizing speed vs add features. It's hard enough to get bugs fixed.

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

      Does it even matter anymore?
      With todays CPU speeds, who can claim to have had their core processor maxxed out even a single time in an arbitrary period of time?

      Today - for desktops anyway, it all seems to be about boosting your graphics cards and having a huge amount of RAM.
      CPU speeds are of less importance, even if you are a "heavy" user of games, image processing, and so on.
      Granted, if you are the sort of person with a fetish for recoding all of your bluray movies onto your computer, you might stress it a bit.

      For the server market, we have had faster CPU's than was ever needed for many years, even for ERP systems.

      It's been years since CPU's have been the bottleneck of systems, desktop and servers alike.

    19. Re:A Better Question: by aztracker1 · · Score: 1

      IIRC, the original observation was that the number of Transistors that could be placed on a given Integrated Circuit pretty much doubled every 18-24 months... I don't think it's held true to that timeline, as the process shrinks for die manufacturing haven't held quite that fast, and is approaching a point where interference from other points on a circuit is close to becoming an issue.

      --
      Michael J. Ryan - tracker1.info
    20. Re:A Better Question: by Anonymous Coward · · Score: 0

      AC's Corollary : Every 18 months, the discussion on the legitimacy of Moore's law doubles.

    21. Re:A Better Question: by stripes · · Score: 1

      My personal pet theory is yes it really does matter. For a long time doubling every 18 months was the arbitrary goal, and Intel could say "if we don't hit X by Y then AMD will overtake us because they double every 18 months", and AMD could say "If we don't hit X by Y then Intel will smash us because they double every 18 months". So each poured whatever they needed into R&D to make it more or less happen. Sometimes one got more ahead then the other and got to roll in the hay for a while (or be unable to fill all the market demand).

      If Moore's law wasn't sitting their prodding them to double or die every 18 months my guess is they would have sat there and gone "Will they REALLY invest $12.6 billion dollars on a new fab? That seems stupid, I bet they will try to get by with a 10% bump from a new microarchicture, so we should aim for 15%". We would have seen a LOT more severely lopsided product matchups, but overall I'm guessing slower growth.

      Not that it matters so much now since they don't seem to be able to keep up with doubling processing capability (unless your problem set is very parallel...and even so Amdahl's Law will get them sooner or later -- add as many CPUs as you like, at some point there is a non-parallel part of your problem space and that part's performance will dominate, even with an infinite number of CPUs).

    22. Re:A Better Question: by Anonymous Coward · · Score: 0

      My experience is that Windows 7 is faster than Windows Vista and that Ubuntu 10.04 and 10.10 are faster than Ubuntu 9.10. The latest version of Mac OSX uses less disk space than the previous version.

      It seems as if the OS bloat peaked in 2009. I wonder if Ubuntu 20.10 will run on my oldest box and if it will run faster or slower than 10.10...

      Time will tell.

    23. Re:A Better Question: by Tordre · · Score: 1

      It a way it could be seen as such as opposed to sending a lot of money developing a chip with 10x the components in 2 years you could instead break that into a six/seven year cycle with 2x every 2 years, each chip iteration has an cost but it should also have a profit which will fund the next iteration.

      It would be better to follow Moores Law from a economic stand point. The Guy in your example does not give the cost it would take to get his 10x chip production ready which is where you example may fail.

    24. Re:A Better Question: by Tordre · · Score: 1

      Apologies for the spelling errors, my eyes did not see them in the preview.

    25. Re:A Better Question: by rdebath · · Score: 1

      If they're bribing someone it's reducing their profits. A bribe is "lost money".

      I guess you mean they dropped their prices, but if you mean they started putting in some Microsoft style anti-competitive terms into their OEM contracts, this can only work if you've got a near monopoly, Intel are not in that position. They could get away with it in the short term because lead times on new designs are very long, but in the longer term working round such contract terms isn't difficult and the differences between AMD and Intel hardware are so minor that the "take my marbles home" threat is quite realistic.

    26. Re:A Better Question: by Krneki · · Score: 1

      So I guess they are stupid. Since they plead guilty and paid AMD a fine for the wrongdoing.

      --
      Love many, trust a few, do harm to none.
  4. Re:Moores law of first posts by alvinrod · · Score: 1

    I'd say you'd run out of stories in which to post first, but it seems as though /. follows a Moore's law of duplicate stories so you should be alright.

  5. Again? by Verdatum · · Score: 5, Funny

    Is there some corollary to Moore's law regarding the frequency at which articles will be written commemorating the age of Moore's law and asking if it is relevant?

    1. Re:Again? by Anonymous Coward · · Score: 0

      That would be Moore's law's law.

    2. Re:Again? by skine · · Score: 1

      And if it were studied by someone whose last name was Moore, it would be Moore's Moore's law's law.

    3. Re:Again? by Anonymous Coward · · Score: 0

      And if it were studied by someone whose last name was Moore, it would be Moore's Moore's law's law.

      Too late,
      Les

    4. Re:Again? by Galestar · · Score: 2

      From the article:

      It's also been so frequently misused that Halfhill was forced to define Moron's Law, which states that "the number of ignorant references to Moore's Law doubles every 12 months."

      --
      AccountKiller
    5. Re:Again? by Scroatzilla · · Score: 2

      Cole'slaw.

    6. Re:Again? by TheRaven64 · · Score: 1

      There is also Moron's Law, which states that no one who links to Moore's paper is capable of correctly stating Moore's Law.

      --
      I am TheRaven on Soylent News
    7. Re:Again? by noidentity · · Score: 1

      You, sir, are a genius. I dub this Verdatum's Law.

    8. Re:Again? by gringer · · Score: 1

      "the number of ignorant references to Moore's Law doubles every 12 months."

      An exponential increase in the number of articles written about any subject is happening pretty much everywhere. Researchers will occasionally claim that this means their particular subject area is becoming more important (because they don't consider that it happens elsewhere). If we assume that a constant proportion of articles referencing Moore's Law are ignorant, and articles referencing Moore's Law also increase at an exponential rate, it follows that there will also be an exponential increase in ignorant references to Moore's Law.

      --
      Ask me about repetitive DNA
    9. Re:Again? by kantos · · Score: 1

      no.... but there should be one about mis-quotes... like the one in the original post, moore's law is about the performance per PRICE point not about performance

      --
      Any and all content posted above may be ignored, considered irrelevant, or otherwise dismissed.
    10. Re:Again? by Anonymous Coward · · Score: 0

      Will there be a diminished accuracy of Moron's Law as the number of ignorant reference's to Moore's Law becomes a significant fraction of the total number of references being made, or will the the total number of references increase to that Moron's Law holds true?

  6. Well, if it didn't... by pedantic+bore · · Score: 2

    Well, if it didn't, then would we still be talking about it, forty-five years later?

    --
    Am I part of the core demographic for Swedish Fish?
  7. Answers by noidentity · · Score: 2

    No, yes, no, no, no.

    1. Re:Answers by BlueWaterBaboonFarm · · Score: 1

      Bravo!

  8. The real problem: Access Speeds by Chowderbags · · Score: 1

    The real problem is access speeds. Even if you had an arbitrarily powerful CPU, you'd still have to load in everything from memory, hard disk, or network sources (i.e. all very slow). Until these can keep up the same pace as CPUs (SSDs are still expensive), it's pretty much just AMD and Intel having a pissing match. How often do you really max out your CPU cycles these days anyway?

    1. Re:The real problem: Access Speeds by Anonymous Coward · · Score: 5, Funny

      How often do you really max out your CPU cycles these days anyway?

      Every-fuckin'-time Flash appears on a web page!

    2. Re:The real problem: Access Speeds by serviscope_minor · · Score: 2

      How often do you really max out your CPU cycles these days anyway?

      All the time. Why?

      --
      SJW n. One who posts facts.
    3. Re:The real problem: Access Speeds by alvinrod · · Score: 1

      If that continues to be a big problem, chip makers will just using the extra transistors to increase the cache sizes. That doesn't solve every problem, but if they're hitting a wall in terms of clock speed or core utilization, then having more cache can keep what is being used well fed.

      The other side of this is that a general PC might not get much more powerful, but notebooks, tablets, and phones will be able to pack the same amount of power into smaller chips, resulting in reduced power consumption or increased capabilities until they run into the same wall, which would take about a decade.

    4. Re:The real problem: Access Speeds by Anonymous Coward · · Score: 0

      How often do you really max out your CPU cycles these days anyway?

      If you're not, then you're wasting valuable resources that would be better spent on those less fortunate than you. In other words: why must you be so greedy and hog more power than you require?

      Useful car analogy: why buy a car with 500hp if you only require 114?

      P.S. I'm only kidding; FTW--consume! More! Er, Moore! Moore!

    5. Re:The real problem: Access Speeds by hedwards · · Score: 1

      Because it's cheaper than getting your penis permanently enlarged?

    6. Re:The real problem: Access Speeds by Pieroxy · · Score: 1

      +1

    7. Re:The real problem: Access Speeds by TooMuchToDo · · Score: 1

      Somewhat true. At my last gig, we were churning through collider data from the CMS detector at the LHC. We took the stream of data directly from CERN at 10-40Gbps, staged it to several TB of fast spinning disk while waiting to write it to a tape archive (17PB), and then ran specially written software on 5500 "workers" that would suck the data back in from a distributed filesystem and recreate collision events from the data. Using 10Gbps hardware, fast disks, and condor for work management, we were able to keep those workers pretty damn busy. Floored 100% of the time? No, but awfully close.

      Note: I'm aware this is a special case, but don't discount how heavily computing resources are used in both industry and scientific/academic settings.

    8. Re:The real problem: Access Speeds by aztracker1 · · Score: 1

      Well, you shouldn't have bought that stupid netbook then, should you?

      --
      Michael J. Ryan - tracker1.info
    9. Re:The real problem: Access Speeds by 517714 · · Score: 1

      Maybe if you used Windows, it would max out less on Flash and more on other tasks.

      --
      The US government have made it clear that we have no inalienable rights; any we do not defend vigorously will be taken.
    10. Re:The real problem: Access Speeds by rcw-home · · Score: 1

      How often do you really max out your CPU cycles these days anyway?

      Anytime it executes something. Although there are a number of things such as frequency stepping and pipelining that complicate the issue to an extent, a core is either executing instructions at its operating clockspeed or it is not. Similarly, a network interface is either transmitting data or it is not. Memory is either being accessed or it's not. A disk is either idle or it is not.

      If those components operated faster, they'd finish any given task faster, leaving room for more stuff in their queues. The reduced latency of those faster components would make the system feel more responsive, and if you timed a large task, you'd note that it'd be done sooner. If "sooner" means "these video frames consistently finish rendering within the desired refresh rate" or "these VoIP packets leave the transmit queue before the next VoIP packet arrives" or "that computer finished logging in before the user got tempted to go get coffee or call the helpdesk" then that can be a big deal. But either way, those components would still be fully maxed out until the task completes.

      I admit this is just pedantry, but perhaps what you meant to say is "Is it really your CPU that you're waiting on most of the time?"

    11. Re:The real problem: Access Speeds by syousef · · Score: 1

      You should be modded insightful not funny

      --
      These posts express my own personal views, not those of my employer
  9. Check the Wiki sources. by 0100010001010011 · · Score: 1

    Is it really that difficult?

    The complexity for minimum component costs has increased at a rate of roughly a factor of two per year... Certainly over the short term this rate can be expected to continue, if not to increase. Over the longer term, the rate of increase is a bit more uncertain, although there is no reason to believe it will not remain nearly constant for at least 10 years. That means by 1975, the number of components per integrated circuit for minimum cost will be 65,000. I believe that such a large circuit can be built on a single wafer.[7]

    Original Article:
    Cramming more components
    onto integrated circuit
    Article 2: Excerpts from A Conversation
    with Gordon Moore: Moore’s Law

  10. fox news at work here by Anonymous Coward · · Score: 0

    So an article on Fox News concludes that it doesn't really matter if it's true so long as people think it's ok by consensus. Par for the course.

    1. Re:fox news at work here by houghi · · Score: 1

      it doesn't really matter if it's true so long as people think it's ok by consensus

      Is that Fox's new motto?

      --
      Don't fight for your country, if your country does not fight for you.
    2. Re:fox news at work here by Elros · · Score: 1

      Sorry, I thought that was NPR.

    3. Re:fox news at work here by Anonymous Coward · · Score: 0

      You thought not only wrong, but backwards.

    4. Re:fox news at work here by Anonymous Coward · · Score: 0

      No; but certain people use "consensus" to justify their hidden agendas. E.g.: "global warming" readily comes to mind. There are others of course. FUD factors in, too.

    5. Re:fox news at work here by Sulphur · · Score: 1

      Some years ago, Ted Koppel moderated a show with half Israelis and half Palestinians in an auditorium.

      Did he invent Fair-and-Balanced?

  11. Transistor count doubling every 2 years. by RightSaidFred99 · · Score: 1

    There's no question on what "Moore's Law" is as the article would paint. Originally, he said double transistor count every year. Then, in 1975, he revised it to every two years.

    It's obviously not a scientific law but it is based on the manufacturing process for circuits and how they evolve, and it has been a good rule of thumb number and has proven as accurate as can be expected while we continue to make chips in basically the same ways.

    It's fairly easy to look this up, there's no need for a lame mainstream media article link.

  12. /. doing its part by deapbluesea · · Score: 2

    It's also been so frequently misused that Halfhill was forced to define Moron's Law, which states that "the number of ignorant references to Moore's Law doubles every 12 months."

    There are only 13 posts so far, and yet /. is still on track to meet this law. Great job everyone.

    --
    Government is not reason; it is not eloquent; it is force. Like fire, it is a dangerous servant and a fearful master.
    1. Re:/. doing its part by Anonymous Coward · · Score: 0

      What did Moore actually say then? The version I heard was that the number of transistors able to be fitted on a chip at a given price point would double approximately every 18 months.

  13. Ask a vague question, get a vague answer. by JustinOpinion · · Score: 5, Insightful

    Well the problem here is that the question "Does Moore's Law Hold True?" is not very precise. It's easy to show both that the law doesn't hold, and that it is being followed still today, depending on how tight your definitions are.

    If you extrapolate from the date that Moore first made the prediction, using the transistor counts of the day and a particular scaling exponent ("doubling every two years"), then the extrapolated line, today, will not exactly match current transistor counts. So it fails.

    But if you use the "Law" in its most general form, which is something like "computing power will increase exponentially with time" then yes, it's basically true. One of the problems with this, however, is that you can draw a straight-line, and get a power-law exponent, through a lot of datasets once plotted in a log-linear fashion. To know whether the data "really is" following a power law, you need to do some more careful statistics, and decide on what you think the error bars are. Again, with sufficiently large error bars, our computing power is certainly increasing exponentially. But, on the other hand, if you do a careful fit you'll find the scaling law is not constant: it actually changes in different time periods (corresponding to breakthroughs and corresponding maturation of technology, for instance). So claiming that the history of computing fits a single exponent is an approximation, at best.

    So you really need to be clear what question you're asking. If the question is asking whether "Moore's Law" is really an incontrovertible law, then the answer is "no". If the question is whether it's been a pretty good predictor, then answer is "yes" (depending on what you mean by "pretty good" of course). If the question is "Does industry still use some kind of assumption of exponential scaling in their roadmapping?" the answer is "yes" (just go look at the roadmaps). If the question is "Can this exponential scaling continue forever?" then the answer is "no" (there are fundamental limits to computation). If the question is "When will the microelectronics industry stop being able to deliver new computers with exponentially more power?" then the answer is "I don't know."

    1. Re:Ask a vague question, get a vague answer. by machinegunhand · · Score: 1

      Moore's Law will eventually find itself to be a construct, which will lead to its own dissolution.

    2. Re:Ask a vague question, get a vague answer. by Anonymous Coward · · Score: 0

      Again, with sufficiently large error bars, our computing power is certainly increasing exponentially.

      i am amused.

      no wait, now i am concerned... oh okay, i'm amused again.

  14. It's not the law of gravity by Opportunist · · Score: 1

    It's not a natural law. It's neither a law of physics nor one of biology. Heeding or ignoring it has no real meaning. And, bluntly, I doubt anyone but nerds that double as beancounters really care about Moore's "law".

    Computers have to be fast enough to do what tasks they're supposed to solve. Software will grow to make use of it (or waste it on eye candy). Nobody but us cares about the rest.

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  15. Wait just one minute here! by gman003 · · Score: 3, Funny

    What the fthagn is this? A Fox News article on /.? And it's actually accurate, non-politicized reporting on a scientific matter?

    Apparently, I have entered the Bizarro World. Or perhaps the Mirror Universe. I can't be dreaming, because I'm not surrounded by hot women in tiny outfits, but something is most definitely WRONG here, and I aim to find out what.

    1. Re:Wait just one minute here! by blueg3 · · Score: 1

      It's neither scientific nor accurate, but other than that, yes.

    2. Re:Wait just one minute here! by kenrblan · · Score: 2

      This was probably the work of a single reporter who had a New Year's resolution to write a factually correct article without political bias. The writer has fulfilled the terms of the resolution, and will probably resume business as usual tomorrow.

      --
      Make everything as simple as possible, but not simpler. - Albert Einstein
  16. Moore's law is not a law by ahodgkinson · · Score: 3, Insightful
    Moore made an observation that processing power on microprocessor chips would double every 18 months, and later adjusted the observation to be a doubling every two years. There was no explanation of causality.

    At best it is a self-fulfilling prophesy, as the 'law' is now used as a standard for judging the industry, which strives to keep up with the predictions.

    --
    ---- It won't be as bad as you fear or as good as you hope, but it will take twice as long as you plan.
    1. Re:Moore's law is not a law by Anonymous Coward · · Score: 0

      I believe he said that transistor density would double every 18 months (and then two years), not computing power...

    2. Re:Moore's law is not a law by dkleinsc · · Score: 2

      It should be pointed out that the various social observations that have often been termed 'Laws' are not always true. For instance, Parkinson's Law states that work expands to fill the time and resources available. It's usually true. But sometimes, it's not, because it's trying to describe something about a system that nobody's been able to fully explain, specifically how an organization / business / bureaucracy actually functions.

      That doesn't make them useless, but it does mean you have to treat them as trends rather than absolutes.

      --
      I am officially gone from /. Long live http://www.soylentnews.com/
    3. Re:Moore's law is not a law by Anonymous Coward · · Score: 0

      It is a statement based on observed patterns that preceded the statement and were extrapolated into the future.

    4. Re:Moore's law is not a law by at_slashdot · · Score: 1

      oh man, it wasn't about processing power, it was about the transistor density on the chip.

      --
      "It is our choices, Harry, that show what we truly are, far more than our abilities." -- Prof. Dumbledore
    5. Re:Moore's law is not a law by 517714 · · Score: 1

      Not an observation; a target. It has held true because every foundry knew that they would meet the target or be at a competitive disadvantage.

      --
      The US government have made it clear that we have no inalienable rights; any we do not defend vigorously will be taken.
  17. Re:Moores law of first posts by fusiongyro · · Score: 5, Insightful

    I feel like I've been reading this article every six months for the last ten years.

  18. In a nutshell... by wcrowe · · Score: 0, Troll

    ...Moore's law is fucking stupid.

    There, I said it.

    In all seriousness, this is not like some sort of law of physics or something. It is just bloody stupid to keep quoting it all the time.

    BTW, I want to add that I don't think Gordon Moore is stupid, only that the myth of this "law" is perpetuated.

    --
    Proverbs 21:19
  19. Precise time to double by jethr0211 · · Score: 1

    The graph in Moore's article clearly predicts double the number of chips every 13 months. Nine "doublings" in 10 years.

  20. Maybe it's My Age... by stewbacca · · Score: 1

    ...but I gave up caring about processor speed about 10 years ago.

    1. Re:Maybe it's My Age... by Anonymous Coward · · Score: 0

      In that case, would you be interested in a bucket of pentium 4's i have lying around?

      I'm sure I can dig up some ram for you too. :)

  21. It's linked in tf summary, it's TFA by grimJester · · Score: 1

    I realize no one reads TFA; not even the submitter did. I don't know which is more absurd, the submitter claiming the above is not in TFA or someone ignoring TFA, reading the wiki page, then linking TFA as the source of Moore's Law without realizing it's TFA!

    Head explodes

    1. Re:It's linked in tf summary, it's TFA by TheRaven64 · · Score: 1

      Yes, that's the WTF. He links to the original paper, and then goes on to incorrectly state Moore's Law. It's like putting up a big sign saying 'click here to see how stupid I am'.

      --
      I am TheRaven on Soylent News
  22. magical thinking from FoxNews by ganv · · Score: 1

    That is an amazingly shallow article on FoxNews.com Maybe they should advertise the source in the summary blurb. They seem to believe that computers will magically keep getting better without any specific hardware improvements required.

  23. Just make a graph by llZENll · · Score: 1

    I clicked only wanting one thing, a graph with three lines showing: Moore's Law, transistor count, and computing power of each processor.

  24. The real problem: Speed of Light by mangu · · Score: 2

    Even if you had an arbitrarily powerful CPU, you'd still have to load in everything from memory, hard disk, or network sources (i.e. all very slow)

    Considering that light only travels 30 cm per nanosecond in a vacuum, the maximum practical clock speed depends on how far your memory is. At a 3 GHz clock rate, a request for data from a chip that's just 5 cm away on the circuit board will have a latency longer than the clock period.

    The only solution to this problem is increasing the on-chip cache. But that will depend on having software that manages the cache well, i.e. more complex algorithms. In that case, since you have to optimize the software anyhow, why not go to a parallel architecture?

    I bet that in the future we will see chips with simpler (read RISC) architectures with more on-chip memory and special compilers designed to optimize tasks to minimize random memory access.

    1. Re:The real problem: Speed of Light by Fict · · Score: 1

      yeah, RISC architecture is gonna change everything

    2. Re:The real problem: Speed of Light by Rockoon · · Score: 2

      I bet that in the future we will see chips with simpler (read RISC) architectures with more on-chip memory and special compilers designed to optimize tasks to minimize random memory access.

      I bet that in the future, you still wont know how much chip space is used by its various components, leading you to continue believing that risc is some sort of space-saving advantage.

      With any instruction set, execution can only be as fast as instruction decoding. Both RISC and CISC machines now have similar execution units, so CISC architectures can feed more execution units per instruction decoded..

      To get the same sort of raw performance on RISC, the decoder needs to be faster than on CISC. When the decoders are already operating at the clock rate, the only way that this can be accomplished is with more decoders.

      Sure, CISC decoders are larger.. but you need less of them to get the same benefits.. so its just about moot. But back to the original point, in neither case are these decoders anywhere near the size of the vast space devoted to cache memory, or execution units.

      We are living in a time when two of the Big Three major chip makers differ significantly over how to organize the many extra decoders they trivially pack on.

      Intel is feeding two banks of decoders into one scheduler and one backing set of execution units while AMD is about to release its new strategy of feeding two banks of decoders into eight schedulers with two banks of integer execution units and one shared floating point unit.

      ...and they do this with the majority of the chip being devoted to cache memory and their controllers.

      When Intel first introduced HyperThreading in the Pentium 4, which is essentially accomplished by tacking on an extra set of CISC decoders to a core, it only took 5% more space than not doing it. A few doublings of the transistor count later, the space those CISC decoders now use is even more meaningless.

      AMD is now introducing its own form of "pack on extra decoders" with its Bulldozer architecture.

      If ARM (a true RISC design) wants to compete on performance, they too would have to pack on extra decoders to feed banks of execution units. ARM is going the other route, tho.. and is focusing on energy efficiency and as such, even cache memory is light on that architecture.

      Just to be clear: Of the Big Three cpu manufacturers (ARM, Intel, and AMD,) the one manufacturer focusing on RISC also offers the *least* amount of cache memory.. the exact opposite of what you think will happen.

      --
      "His name was James Damore."
    3. Re:The real problem: Speed of Light by NicknamesAreStupid · · Score: 1

      When I was at NEC Electronics, there was work on incorporating a processor in each DRAM, effectively creating a massively parallel machine. This did not happen for several reasons -- diverging processes for memory and CPUs, latencies when accessing large blocks of data, and no legacy systems that could even begin to make use of such an architecture. Instead, CPU caches evolved and probably will continue.

      When was this idea? Well, NEC Electronics was the largest semiconductor manufacturer at the time, and CPUs did not have an onboard cache.

  25. pdh by Anonymous Coward · · Score: 0

    First law of journalism.. never in your headline write a question that can easily be answered with a yes or a no....

    Is it true that computing power has exactly doubled for 45 years over any specific length of time?... No... end of article.

  26. No moore by cjseealf · · Score: 1

    Moore's law more than a technologcal vision, is a business strategy powered by a technological vision. I just see corporates pigs, (no ofence to pigs) doing unjustified capitalism. Now we should have other priorities.

  27. you keep using that word 'law' by Tumbleweed · · Score: 1

    None of these are 'laws', where you get punished by breaking them. Not Moore's, not Godwin's, etc. They are more 'generalizations' than anything else. Moore's, especially, could be more acccurately terms an 'observation', as that's what was going on at the time he made it. Everyone repeat after me: "Moore's Observation"

    There we go.

    Even "Moore's Average" would be more accurate.

    1. Re:you keep using that word 'law' by sexconker · · Score: 1

      None of these are 'laws', where you get punished by breaking them. Not Moore's, not Godwin's, etc. They are more 'generalizations' than anything else. Moore's, especially, could be more acccurately terms an 'observation', as that's what was going on at the time he made it. Everyone repeat after me: "Moore's Observation"

      There we go.

      Even "Moore's Average" would be more accurate.

      "Law" comes from early germanic's "lagan", which means to put or to lay. Thus a law is something that is in place.

      Since this is shitdot, I'll post the shittipedia definition: "The term law is often used to refer to universal principles that describe the fundamental nature of something, to universal properties and relationships between things, or to descriptions that purport to explain these principles and relationships."

      Moore's law is accurate. Whether or not it's correct is another matter. So far, it pretty much has been.

  28. Not who you ask, but what you ask... by joeyblades · · Score: 3, Informative

    the future founder of chip juggernaut Intel, predicted that computer processing power would double roughly every 18 months. Or maybe he said 12 months

    What Gordon Moore actually said was that complexity would double every year. Moore was also relating cost at that time, but cost doesn't actually scale well, so most people don't include cost in modern interpretations of Moore's Law.

    For circuit complexity, Moore's Law (with the 18 month amendment) seems to still hold true. However, we are fast approaching some physical limits that may cause the doubling period to increase.

    Performance is commonly associated with Moore's Law (as you mention), However, performance is a function of clock speed, architecture, algorithm, and a host of other parameters and certainly does not follow Moore's Law... It never really has, even though people still like to think it does... or should...

    1. Re:Not who you ask, but what you ask... by thogard · · Score: 1

      The Moore's law doubling gives us other advantages. Early CPUs didn't have a multiply instruction at all. Later ones had enough resources they added the instruction but it simply used the adder many times. At some point thanks to the advantages of Moore's law, there was room for a barrel multiplier. Once those got large enough, floating point became a reality and a floating point multiply ended up being 1000 times faster than it had been just year or so before. Now we are seeing hardware that is close to doing arbitrary ray tracing in near real time yet in 1986 it took a hypercube of 256 Intel 286 chips hours to render what many graphics chips can now do in milliseconds. Just using Moore's law would not have given us that advantage.

  29. memsistors by Anonymous Coward · · Score: 0

    Some people have thought Moore's law was soon to come to a close due to heat restrictions, but with the recent work on memsitors they believe chip technology will continue to grow steadily for quite sometime. I herd this from a professor of mine at the University of Alberta, take it for what you want.

  30. CharlieMopps's Law by Charliemopps · · Score: 2

    CharlieMopps's Law(TM): The quantity of articles posted to Slashdot that mention Moore's Law will approximately double every time Intel or AMD come out with a new processor.

    1. Re:CharlieMopps's Law by sexconker · · Score: 1

      CharlieMopps's Law(TM): The quantity of articles posted to Slashdot that mention Moore's Law will approximately double every time Intel or AMD come out with a new processor.

      I salute you for telling it like it is, and for using "CharlieMopps's Law" to refer to a law that belongs to CharlieMopps. The ess after the apostrophe brings me pleasure.

    2. Re:CharlieMopps's Law by Charliemopps · · Score: 1

      I am the law.

  31. Shut the Fuck Up by sexconker · · Score: 2

    "Moore ... predicted that computer processing power would double roughly every 18 months. Or maybe he said 12 months. Or was it 24 months? Actually, nowhere in the article did Moore actually spell out that famous declaration, nor does the word "law" even appear in the article at all."

    "The complexity for minimum component costs has increased at a rate of roughly a factor of two per year (see graph on next page). Certainly over the short term this rate can be expected to continue, if not to increase."

    Moore's law is about minimum cost per unit. In traditional manufacturing, this is volume. In the IC world, component volume is simply chip density, but unit volume is affected adversely by chip density (complexity up, yields down). Thus, there is a balancing act. Moore's law is about the minimum, the optimal point on the curve from a manufacturer's standpoint.

    This minimum has traditionally directly correlated with performance. Why? Because we tend to add components that end up doing work.

    No, Moore didn't call it a law. It was an observation, and a prediction. As it proved to hold true over the next several decades, people referred to it as a law.

    And it continues to hold true.

    So please shut the fuck and stop asking about it every 6 months. Moore's law isn't about to be broken. Tablets aren't replacing desktop PCs any time soon. The cloud isn't changing the face of computing as we know it. This isn't the year of the Linux desktop. That breakthrough in solar panel efficiency will never materialize. Batteries still suck ass and there are no signs of any significant improvement on the horizon.

    If you've got no news to report, just throw up "Not much news today. People are still talking about those new Intel CPUs, though.".

  32. Performance still increasing steadily by Anonymous Coward · · Score: 0

    Take a look at top500.org and you can see a fairly steady doubling of performance every 13-14 months for the last 17 years or so. From what I understand, I'd expect the current growth trend to continue for the next few years.

  33. Back in '73 ... by Michael+McClary · · Score: 1

    Back in 1973 I made it to my first NCC (the AFIPS National Computer Conference - the annual big industry shindig in those days). At that time Moore's law was quite the buzz. Memory chips were still following it, but complex function chips were starting to fall off from the straight line on the log graph. At that time there were a few microprocessors out. But it was far before the stage where you could put a microprocessor on every device control card. Most such functions - including the "glue" around the microprocessors themselves - were constructed of small-scale integration chips. Support chips were starting to graduate from things like four independent gates, a couple flops, or a multiplexer per package. But chips were essentially all still being designed by silicon manufacturers. A few might have been done under contract with companies designing boxes. But most were based on the semiconductor companies' marketing departments' guess at what would be wanted a couple years in the future. I realized that one explanation for the shortfall might be that, as the complex function chips became larger, the engineering of more of the circuitry was moving from the system designers - including the garage and venture-financed startups - to the semiconductor manufacturers. This reduced the number of engineers on the job and their connection to the needs of the final products. Further, it changed the incentives on the engineers, making them more conservative (since they needed to keep an established company in business rather than take risks to establish a new venture or product). There was a panel with several of the silicon companies that discussed the problem. Come the Q and A session I brought up the above, and proposed a solution: That the silicon companies license their design tools to the system designers and build the chips THEY design. That way the complex-function engineering, along with its risks and costs, could be moved back to the ventures, while the silicon companies could concentrate their engineering on what they do well - improving the process. And I asked whether any of their companies would consider such an approach. (I thought of it as a "silicon breadboard", but I don't recall actually using the term in the question.) At least three of the companies' representatives - Mororola, Intel, I forget who else - said that there was no way they would ever do such a thing. (The Motorola guy was quite emphatic about it.) And the guy beside me gave me his card and suggested I interview with him. (He was from Signetics, which was already doing a mask-programmed gate array chip which the customer could customize. I DID interview with him - and to this day I kick myself for not taking a job there. It would have gotten me out to Silicon Valley 12 years earlier, two years before both the release of the Altair 8080 and the founding of the Homebrew Computer Club. B-b ) A few months later that year, IBM announced they'd make their design tools available to customers and would fabricate chips under contract. Over the next couple years several other manufacturers followed suit. One of them transitioned from custom silicon design to tool licensing as a business and several others started up just to do tools. For a while it was known as the "silicon foundry" system. Now it's ASIC (application specific integrated circuit) design, there are standards for the major design languages, and a whole ecosystem of manufacturers of chips and of computer-aided design tools for all stages of the process. And ASIC design is what I do for a living since I went back over to the hard side of the force in the early 1990s.

  34. POC? by serbanp · · Score: 1

    What's up with the inane mention of Pirates of the Carribean? The writer even got it wrong, as the first one to utter the words was Geoffrey Rush's character (Ctp. Barbossa). It's probably a FauxNews specialty...

  35. Re:Back in '73 ... (Formatting fixed up.) by Michael+McClary · · Score: 1

    (Trying again with paragraph breaks. B-b )

    Back in 1973 I made it to my first NCC (the AFIPS National Computer Conference - the annual big industry shindig in those days). At that time Moore's law was quite the buzz. Memory chips were still following it, but complex function chips were starting to fall off from the straight line on the log graph.

    At that time there were a few microprocessors out. But it was far before the stage where you could put a microprocessor on every device control card. Most such functions - including the "glue" around the microprocessors themselves - were constructed of small-scale integration chips. Support chips were starting to graduate from things like four independent gates, a couple flops, or a multiplexer per package. But chips were essentially all still being designed by silicon manufacturers. A few might have been done under contract with companies designing boxes. But most were based on the semiconductor companies' marketing departments' guess at what would be wanted a couple years in the future.

    I realized that one explanation for the shortfall might be that, as the complex function chips became larger, the engineering of more of the circuitry was moving from the system designers - including the garage and venture-financed startups - to the semiconductor manufacturers. This reduced the number of engineers on the job and their connection to the needs of the final products. Further, it changed the incentives on the engineers, making them more conservative (since they needed to keep an established company in business rather than take risks to establish a new venture or product).

    There was a panel with several of the silicon companies that discussed the problem. Come the Q and A session I brought up the above, and proposed a solution: That the silicon companies license their design tools to the system designers and build the chips THEY design. That way the complex-function engineering, along with its risks and costs, could be moved back to the ventures, while the silicon companies could concentrate their engineering on what they do well - improving the process. And I asked whether any of their companies would consider such an approach. (I thought of it as a "silicon breadboard", but I don't recall actually using the term in the question.)

    At least three of the companies' representatives - Mororola, Intel, I forget who else - said that there was no way they would ever do such a thing. (The Motorola guy was quite emphatic about it.)

    And the guy beside me gave me his card and suggested I interview with him. (He was from Signetics, which was already doing a mask-programmed gate array chip which the customer could customize. I DID interview with him - and to this day I kick myself for not taking a job there. It would have gotten me out to Silicon Valley 12 years earlier, two years before both the release of the Altair 8080 and the founding of the Homebrew Computer Club. B-b )

    A few months later that year, IBM announced they'd make their design tools available to customers and would fabricate chips under contract. Over the next couple years several other manufacturers followed suit. One of them transitioned from custom silicon design to tool licensing as a business and several others started up just to do tools. For a while it was known as the "silicon foundry" system. Now it's ASIC (application specific integrated circuit) design, there are standards for the major design languages, and a whole ecosystem of manufacturers of chips and of computer-aided design tools for all stages of the process.

    And ASIC design is what I do for a living since I went back over to the hard side of the force in the early 1990s.

  36. more about market/marketing forces than technology by neurocutie · · Score: 1

    I'd say that the fact that computing PRODUCTS have largely tracked "Moore's Law" says more about market forces and competition, and "Wintel" (Microsoft/bloat/software purchases, etc), than it says about physics, engineering and computing technology... It says more about what kind of products and features are needed to drive the IT money machine to spend and spend even though actually the computing needs to write letters, emails and most documents was attained more than a decade ago. Don't forget about advertising in the equation, all those Flash-drive websites throwing ads at you, requiring 2-4GB of RAM and plenty of CPU and GPU just to support a browser to display all that marketing crap without a true increase in substantive content...

  37. havent hit "diminishing returns" yet by peter303 · · Score: 1

    Technology often follows an "ess-curve", a steep upward slope of exponential improvement followed by a flattening, diminished returns. Micro-electronics is still in the exponential growth part, but will flatten some unknown decade hence. Its always been a decade or two in the future in my life. Trains and automobiles are technologies that achieved most of their efficiencies now. Although the incorporation of computing has reinvigorated them somewhat.

  38. Moore wasn't the first, only the most famous. by altnuc · · Score: 1

    Moore wasn't the first person to recognize this, only the most famous. See for example: http://docs.google.com/viewer?a=v&pid=explorer&chrome=true&srcid=1PX1HUsIBhnOSOsxcM2HoJZHv-9rtnNPOu-CA--584-UA4GLXxhWz842JmRDy&hl=en which describes Selengut's results from 1959. Selengut predicted computer speeds would double in magnitude every 10 years.

  39. At least state the law reasonably accurately by fnj · · Score: 1

    1) A law does not imply causality.
    2) Moore's Law does not state that processing power doubles every 2 years. It states that the number of transistors that can be placed reasonably economically on an integrated circuit doubles every 2 years. It's not the same thing.

  40. What Moore Actually Said... by chromatix · · Score: 1

    ...had more to do with the *cost* of transistors than the quantity or speed of them. The increasing quantities per device are, however, simultaneously a cause (economy of scale) and effect (your dollar goes further) of this reducing cost.

    We can now buy a device with a billion transistors in it for a couple of hundred dollars. That's about 50K transistors per cent. It follows that about 30 years ago, it would have been about 1 transistor per cent, or in other words the original 68000 would have cost about $680 in about 1980. Since it is described as originally being "quite expensive", this seems to fit. I don't have any data on the cost of transistors in 1965, though.

    --
    --- The key to knowledge is not to rely on people to teach you it ---
  41. Re:Moores law of first posts by psithurism · · Score: 1

    I feel like I see twice the rate of stories about this every 18 months or so.

  42. Moore's Law roughly seems to hold by kriegs · · Score: 1

    Look at PCs and storage as the bellwether here - both have considerably declined in price per unit of (whatever) over time. Storage was $1 per byte for RAM around the time Moore made his prognostication. Disks held 5MB per 14" platter. Today quite a lot more in quite a lot less volume. Same for compute power. A million transistors on a chip seemed like a lot just 20 years ago. Now we're pushing a billion and the CPUs still cost less than they did a score ago. Is it an exact straight line over time? Of course not. But I wish I could get the same value per dollar from just about any other commodity. Pizzas would be about .001 cents per slice by now. Mmmmm Pizzas.

  43. Self fulfilling prophecy by junglebeast · · Score: 1

    Chip makers intentionally regulate (slow down) their advancement to meet Moore's law because it allows them to make greater profits by forcing user's to upgrade on a regular basis, while still giving them enough time to thoroughly test the next iteration and make a profit on it.

  44. No, a different question. by psithurism · · Score: 1

    Sure, I don't care why intel is making their chips faster, but I would like to know how much faster and how?

    If you have a software project, scheduled for three years of development, can I rely on my average customer to be running computers 2 ^ 1.5 times as fast as they are now, or will multi-core machines proliferate?

    As an intel share holder, all I'd need is your question, but as a computer user looking to the future, I'm more interested in the answer to the original question.

  45. Re:Just make a graph -- goog is your friend... by anon+mouse-cow-aard · · Score: 2
  46. Re:Moores law of first posts by hairyfeet · · Score: 1

    That is because you have, and it is even less relevant now. I mean so what if we haven't hit the wall on Moore's Law yet, we sure as hell hit it when it came to speed VS heat. So now everyone is having to trade more cores for raw speed only problem? It does not actually work beyond a couple of cores for 95%+ of the population. They just don't have enough jobs for the cores to do and most jobs are still depending on single threaded performance.

    So they can reprint this article every year like Moore's Law is the gospel of Gordon or something but to the average folks it just doesn't matter. Trying to increase performance by constantly adding more cores (what are we up to, 6 each for AMD and Intel?) is putting band aids on the bullet wound. Most jobs simply don't benefit from more cores, and we can't figure out how to fix the heat problem above 3.6GHz.

    It is a shame we are down to just two CPU manufacturers, because if someone could find a way to make a 5GHz+ CPU triple core that doesn't get so hot you could cook your lunch on it? Well THAT would be a real breakthrough. But at the way we are going we are gonna end up with everyone and their grandma on an octacore CPU that spends most of its time twiddling its thumbs.

    --
    ACs don't waste your time replying, your posts are never seen by me.
  47. Intel's smallest chip is a Nand chip by NAND_Flash_Guy · · Score: 1

    Fabricated on 25nm: http://www.intel.com/pressroom/archive/releases/2010/20100201comp.htm over 36 billion transistors in 167 mm^2.

  48. Re:Moores law of first posts by Anonymous Coward · · Score: 0

    FusionGyro's Constant

    Upon tracking various technology articles over the last decade, FusionGyro's observed semi-annual publishing of article's questioning whether Moore's Observation would still hold true

  49. Re:Moores law of first posts by 517714 · · Score: 1

    You don't belong here if you RTFA!

    --
    The US government have made it clear that we have no inalienable rights; any we do not defend vigorously will be taken.
  50. Von Neuman Bottleneck. by Ungrounded+Lightning · · Score: 2

    Unfortunately its the aggregate of a pile of small independent undemanding tasks that drags modern PCs to a crawl. And these aren't even bottlenecking the CPU itself... to be honest I don't know what the bottleneck is right now in some items... I'll open up the task manager... cpu utilization will be comfortably low on all cores, hard drive lights are idle so it shouldn't be waiting on IO... and the progress bar is just sitting there... literally 20-30 seconds later things start happening again... WHAT THE HELL? What are the possible bottlenecks that cause this?

    Might be thrashing or a task scheduler issue. Try a different OS on that machine to see if the performance changes, or try a similar machine configured with more memory.

    But it might also be the Von Neumann Bottleneck. If your working set - either data or instructions - is bigger than the on-chip caches, you get constant cache misses. It's like thrashing but between cache and memory rather than between memory and the swap partition.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    1. Re:Von Neuman Bottleneck. by rdebath · · Score: 1

      But it might also be the Von Neumann Bottleneck. If your working set - either data or instructions - is bigger than the on-chip caches, you get constant cache misses. It's like thrashing but between cache and memory rather than between memory and the swap partition.

      This manifests as a larger than expected CPU time on just about every performance tool you can mention.

      If you're running multiple tasks you can sometimes measure it as a decrease in the amount of work done per cycle in other tasks on the machine.

  51. really sick of this human hair analogy by ecloud · · Score: 1

    Seriously I remember hearing it back in the 70's. Enough already. Transistors are so small that human hair isn't even a reasonable comparison to make.

  52. Guidelines by dar · · Score: 1

    It was Geoffrey Rush as Captain Barbossa and not Johnny Depp who first used the phrase "guidelines" in the Pirates movies.

    Is this enough of an error to doubt the veracity of the rest of the article? ;-)

    --
    My other Slashdot ID is much lower.