Slashdot Mirror


Transmeta Founder Talks Chips

gManZboy writes "Dave Ditzel, CTO and Founder of Transmeta (you remember Transmeta? weren't they supposed to kick some Intel booty?) sits down and speaks with Alpha and StrongARM chip designer Dan Dobberpuhl about the history of CPUs, where they're heading, and how the heck we'll keep up Moore's Law (if we can)."

3 of 153 comments (clear)

  1. total energy available by glassesmonkey · · Score: 4, Interesting

    I can't find it again, but I saw an interesting discussion that took the number of processors and embedded processors and the exponential growth of these devices and also the MIPS scaling and the energy per MIPS and compared it to the amount of energy in the sun. It was very clear that at some point you will run out of energy to power all the CPUs in a surprisingly short amount of time.

    I wish I could find it again. (please let me know if you know)

  2. What I'd like to see: by Anonymous Coward · · Score: 5, Interesting

    I'd like to see the future of computing (and I do mean desktop computing) where the whole system has no moving parts. You read me, no spinning hard drive, only solid-state MRAM drives (or something.) No fans, not even in the power supply. 5W CPUs with the more processing muscle as today's 60W beasts. Oh, and OLED screens.

    Well that's enough fantasizing for one day.

  3. How Moore's Law affects some computer users by Skapare · · Score: 4, Interesting

    How Moore's Law affects some computer users as measured in the time it takes to do something, like render a page of a document on the graphical screen in a window opened for a word processor, is shown as an example here:

    • 1992 1.25 seconds
    • 1993 800 milliseconds
    • 1994 500 milliseconds
    • 1995 320 milliseconds
    • 1996 200 milliseconds
    • 1997 125 milliseconds
    • 1998 80 milliseconds
    • 1999 50 milliseconds
    • 2000 32 milliseconds
    • 2001 20 milliseconds
    • 2002 12500 microseconds
    • 2003 8000 microseconds
    • 2004 5000 microseconds
    • 2005 3200 microseconds
    • 2006 2000 microseconds
    • 2007 1250 microseconds
    • 2008 800 microseconds
    • 2009 500 microseconds
    • 2010 320 microseconds
    • 2011 200 microseconds
    • 2012 125 microseconds
    When you are doing something interactively and have to wait the better part of a second (or worse) for each step to complete, it can be a big pain. A faster CPU would be nice. But once that wait gets down into a certain range (varys depending on what the task actually is), it won't really matter as much, if at all.

    There will still be needed even faster CPUs for many things. The use of cryptography will certainly be increasing and that is a big need for more CPU speed. Larger, more bloated (in terms of steps of code, in addition to RAM and disk space), operating systems and applications will need faster (and larger) CPUs, too (though many have learned to avoid these steps to avoid the costs of upgrades to software and hardware).

    But the market for faster CPUs will gradually be leaving behind more and more people who do the kinds of things that just don't need it. The threshhold has been reached for many, and soon will be for many more. Hopefully new and expanded uses will keep (or restore) the markets in a thriving condition.

    --
    now we need to go OSS in diesel cars