Slashdot Mirror


IBM Creates World's Fastest Semiconductor Circuits

Todd Heidesch writes: "'IBM announced it has created the world's fastest semiconductor circuit, operating at speeds of over 110 GigaHertz (GHz) and processing an electrical signal in 4.3 trillionths of a second.' IBM expects the new technology to be pumping out 100 gigabit/sec network switching chips by the end of the year (on an optimistic schedule, I presume)." dr_zeus contributes a link to this Reuters article running on Wired (also fairly thin) on the release, writing: "Granted, this isn't a PC chip, but one wonders how long it will be before we hear 'dude, you've got a 110GHz Dell!'"

4 of 240 comments (clear)

  1. Power Consumption by Zo0ok · · Score: 5, Funny

    Dude, your 110GHz Dell consumes 450kW, and requires its own diesel generator...

  2. 110 Ghz Dell by Reality+Master+101 · · Score: 5, Funny

    And Steve Jobs will still claim that his 2 Ghz G6 is "twice as fast" on some obscure benchmark.

    --
    Sometimes it's best to just let stupid people be stupid.
    1. Re:110 Ghz Dell by sharkey · · Score: 5, Funny

      ...some obscure benchmark

      Probably the number of Bunny People ignited per second.

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
  3. Diary of a 110GHz Dell Computer by MavEtJu · · Score: 5, Funny

    Dear Diary,

    Life can be hard if you're a 110GHz computer. It wasn't until my 3.168x10E15th clockcycle that there was a movement on the mouse and I had to present a password-requestor on the screen. That might look nice, but I had to wait several million of clockcycles before I got all the needed information from the memory. Memory is sooo slow these days, I recall stories from previous generations that you could have the data the next clockcycle after you had set the address! The downfall started when but right now it's waiting waiting waiting.

    Fortunatly the password typed was wrong, so I had the fun of producing a beep for 44 billion clockcycles. It sounds an impressive length of time, but I got bored after about twenty million clockcycli and I changed the tone-height a hertz or two. That'll teach them to make these stupid mistakes!

    Yeah... life is as good as you make of it. Hmm... an interrupt. Hold on. Back. Well, 80 clockcycles for that... Stupid optimized code. How much more before we get another timer-interrupt? Aaargh, still more than 80 billion clockcycles...

    --
    bash$ :(){ :|:&};: