Slashdot Mirror


End Of The Line For Alpha

Scareduck writes "Infoworld reports HP has released the last iteration of the Alpha chip. I used these babies in the late 90's, and for a time, they were da bomb. Sadly, the economics weren't there, DEC management really didn't have much of a clue, and Alpha has, at long last, bit the dust. Alpha-based servers will continue to be sold through 2006, and supported through 2011. Farewell, Alpha; the world's line of chips seems to have declined to Intel and a handful of niche guys." Slashdot ran for the first 7 or 8 months off an Alpha box.

514 comments

  1. Shouldn't they rename it by Stop+the+war+now! · · Score: 5, Funny

    to "Omega" then?

    1. Re:Shouldn't they rename it by Anonymous Coward · · Score: 0

      That's the name of my BSD-box.

    2. Re:Shouldn't they rename it by jayhawk88 · · Score: 2, Funny

      You Bastards! You blew it up!

      Oops, wrong movie.

    3. Re:Shouldn't they rename it by Anonymous Coward · · Score: 0

      because it's dead?

    4. Re:Shouldn't they rename it by nozell · · Score: 2, Interesting

      The name 'Alpha' was the codename, the original product name was 'AXP', but that was quickly changed.

      My favorite Alpha memory is being in the VMS group and being told that Ultrix wasn't going to be allowed to port to it. It was going to be a VMS-only chip. Of course, this was back in the 'UNIX is snake oil' days.

    5. Re:Shouldn't they rename it by nozell · · Score: 1

      I made a graphic to commemorate the Alpha:

      http://nozell.com/blog/archives/2004/08/18/alpha-r ip/

  2. Well by Sv-Manowar · · Score: 0, Redundant

    I for one, welcome our new Intel overlords

    1. Re:Well by Kourino · · Score: 1

      I don't :(

    2. Re:Well by fader · · Score: 5, Funny

      Shouldn't that be "I for 1.000000000317"? Or did they fix that bug?
      (-1, reference to overblown P1 rounding errors)

      --
      - fader
    3. Re:Well by avronius · · Score: 3, Funny

      I am Pentium of Borg
      Division is futile
      You will be approximated

      (stolen from a sig - circa Pentium I)

    4. Re:Well by Anonymous Coward · · Score: 5, Informative
      So what does HP do anymore. Once HP stood for a lot of great things, including loyalty to their employees (which reaped loyalty from their employees as a reward, and great printer products.

      Then tey had the stupid idea and buddies decided to kick out Hewlett (who at least knew that the employee loyalty went both ways, and recognised the strength in their printers), and decided to , support Carly's silly idea of

      1(HP) + 1(Compaq) + 1/2(Dec) = 0.95(HPQ)

      which made them #1 for a very brief moment until they decimated themselves with the first major layoffs in cocmpany history making themselves #2 or worse in most things within a quarter or two after they were #1. Amazing that they try that hard to become #1 (which for some reason they pitched to investors as being more important than having a sustainable business), only to then trim themselves down to be #2 to save costs.

      Turns out Hewlett was right in the ind. They were a great printer company, and if they ditch the Compaq crap and the random software that they bought and never used (remeber the "$470 million mistake in buying Bluestone"), they might become a great printercompany again.

      Between Compaq&HP this should be a case study of how stupid executive decisions can kill a company. They had the best CPUs (Alpha, and PA-RISC), the best search engine (Alta Vista), etc. They could dhave been Intel+Google.

      Now what the hell have they become? A more expensive(at least til they finish their layoffs)-than-Dell reseller of Wintel. God what an embarassment.

      Bring back Walter Hwelett!!!! At least he rememberd and understood what HP once stood for.

    5. Re:Well by Tired+and+Emotional · · Score: 2, Interesting
      Right on.

      HP used to make a lot of cool tools as well - Oscilliscopes and such.

      Their calculators were very cool

      They were in at the begginning of the laser printer market. My Laserjet III is still going strong (did have to replace the power supply once but that was a job I could do myself with a screwdriver)

      They have a pretty good claim to having invented the personal computer even though they never sold huge numbers since they were aimed at labs rather than end users. IBM can also put in a claim on that front with their APL desktop machine (HP's ran Basic or their own algebraic langauge, depending on model). We are talking early to mid 70's here.

      They used to make PCs that you could run over with a truck - I know someone who did that on a loading dock and it kept on working.

      And they made a cool range of mini-computers (although their OS and compilers were somewhat of a pain to use). In at least one of the early models you could actually add your own instructions using writable control store.

      --
      Squirrel!
    6. Re:Well by cinnamon+colbert · · Score: 1

      Just because the hp/compaq strategy did not work out, does not mean that the alternative - being a printer comany - would have worked out. Been down to compusa lately ? printers are sold to drive cartridge sales, and it is hard to see epsom vs hp vs whatever going in hps favor. Printers, if not this year, in a year or two will be like cell phones.. a cut throat market of semi disposable units dominated by asia

      As for this employee loyalty thing...it is easy to look good on a bicycle going downhill with a tailwind. For a long time, for whatever reason, hp was in a good posistion, and then they were not, adn whenever that happens, formerly great companys start firing
      people. Its like companies doing really basic researcy: only companies with monopoly power, like the old att or ibm, can afford tht.

      PS: whenever I check out prices in the sunday paper, hp looks cheaper then dell.
      PPS: MY boss, who is now in his 70's, told me that hp stands for high priced...

    7. Re:Well by pkhuong · · Score: 1

      It also stood for quality. My father bought 41, with 3 expansions. I still have the receipt: ~900 CAD (back in the time when CAD was more expensive than USD). But it's probably one of the best buy (doh! ;) he ever made: I'm still using it more than 20 years later, and i'm still more efficient* with it than with modern calculators. Solid engineering and manufacturing is expensive.

      *By more efficient, i mean faster and more reliable. There's no way i'll ever balance shifts with anything but an rpn calculator with a good keyboard (hear that 49g+?).

      --
      Try Corewar @ www.koth.org - rec.games.corewar
    8. Re:Well by SocietyoftheFist · · Score: 1

      That's great, we'll all take your bosses word as scripture. For those of use around long enough to come up with our own thoughts, we miss the quality and reliability of the old HP.

    9. Re:Well by Anonymous Coward · · Score: 0

      printers are sold to drive cartridge sales, and it is hard to see epsom vs hp vs whatever going in hps favor.

      I'd pay a premium for a printer that was actually built to last. You can pry my HP Deskjet 690C from my cold, dead hands because the day it dies (Or I can't find cartriges for it any more) I know I'll have to replace it with a "modern" hunk of shit that will work for three months before I have to bin it and replace it. Oh deep fucking joy, how much fun that will be.

  3. Beta by Anonymous Coward · · Score: 5, Funny

    Damn, sure took them a while to get to Beta...

    1. Re:Beta by donkeyoverlord · · Score: 0, Redundant

      See it's not only open source projects that never make it to version 1.0!

    2. Re:Beta by attam · · Score: 5, Interesting

      incidentally, at MIT there is a course called 6.004 (Computation Structures) that all CS and EE undergrads have to take... in that class we implement a simulator for a processor called the "Beta" which is essentially a scaled-down alpha...

  4. At last... by Anonymous Coward · · Score: 1, Insightful

    one of the "X is Dead" comments can be true!

  5. Sad by AKAImBatman · · Score: 5, Interesting

    It's truly scary how the Intel is becoming the only mainstream chip architecture left alive. Pretty good for something that intel originally created as a stopgap solution! I'm just hoping that UltraSparcs don't go anywhere.

    BTW, better colors.

    1. Re:Sad by plover · · Score: 5, Insightful
      I read this in the article too, and all I could think was "but what about the PowerPC family?" Is that all the Mac is: a "niche" player?

      And who knows what the future will bring? AMD may diverge so far from Intel that they may eventually be considered their own architecture.

      I think the chip market is about as dead as *BSD (*according to Netcraft.)

      --
      John
    2. Re:Sad by Ghost-in-the-shell · · Score: 2, Interesting

      What is really sad is you have not heard of the highly powerful, and successful AMD series of chips and well as the Motorola chip sets.

      When it comes to the PC market sure the Intel Chips are popular, but the Motorola chips are used far more in other technology applications. Like Telephone Switches, routers, calculators and so forth.

      Do a little looking around. I have only ever seen Intel stamped on the backs of chips in the PC markets.

      --
      -Ghost
    3. Re:Sad by AKAImBatman · · Score: 5, Informative

      What is really sad is you have not heard of the highly powerful, and successful AMD series of chips

      You mean the one's BASED on Intel's architecture?

      as the Motorola chip sets

      No one uses Motorola's chips for PCs anymore. All of Apple's PowerPC chips come from IBM, and IBM uses its bigger cousin (the POWER chip) in its Unix servers.

      Of course, I'm not a big IBM fan so I tend to have selective memory about those.

    4. Re:Sad by Anonymous Coward · · Score: 0

      wow. the left menus are overlapping the thread area.

      you

      fail

      it

    5. Re:Sad by dj245 · · Score: 2, Interesting
      I think its OK that there's only one mainstream architecture, as long as there is more than one company making it. That way, they can compete against each other to make architectures that will be used in the future, and the best architecture hopefully will win. We're already seeing that with AMD64 and Itanium. Arguably, the better architecture won.

      As long as there is competition for architectures, advancements in architecture will continue. Does it really matter that there is only one mainstream architecture?

      --
      Even those who arrange and design shrubberies are under considerable economic stress at this period in history.
    6. Re:Sad by mikael · · Score: 1

      What about Sony's "Cell" architecture?

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    7. Re:Sad by boisepunk · · Score: 1
      It's truly scary how the Intel is becoming the only mainstream chip architecture left alive.

      I'd hate to give any kind of praise or credit to Apple, but the above statement is not true. There's plenty of machines out there running on the famous PowerPC architecture.

      --
      main(0)
    8. Re:Sad by sp0rk173 · · Score: 5, Insightful

      yeah i'm agreeing with this one. I hope PPC starts really moving - it's got some damn nice architecture behind it...POWER5's are going to be awesome. I would love to see the market open up for PPC, and start to see them sold next to Athlons and P4's.

      As far as AMD goes, they did a damn fine thing with AMD64. Hopefully they keep it up and keep diverging from intel, while still offering a cheaper and (in some cases) technologically superior competating product. I would hate to see the day when Intel really does own the processor market.

    9. Re:Sad by drinkypoo · · Score: 4, Informative

      AMD and intel processors do not share an architecture. AMD and intel have been making their own RISC-architecture x86-compatible processors (AMD is more RISCy than intel) since the K5 and Pentium, respectively. In particular the K6 is entirely RISC inside, with an emulator strapped on the front and back ends (fetch and restore.)

      I think you mean the one based on intel's instruction set.

      Of course, intel's new 64 bit processors are in turn based on AMD's instruction set...

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    10. Re:Sad by Anonymous Coward · · Score: 1, Informative

      > No one uses Motorola's chips for PCs anymore. All of Apple's PowerPC chips come from IBM,

      False. The eMac and all current Apple laptops ship with Motorola chips. In units, Apple sells more Motorola than IBM.

    11. Re:Sad by stratjakt · · Score: 2, Interesting

      Is that all the Mac is: a "niche" player?

      Umm, yeah. They've been at about 2-4% market share for as long as I can remember. They sure as hell aren't mainstream players.

      --
      I don't need no instructions to know how to rock!!!!
    12. Re:Sad by StalinsNotDead · · Score: 2, Funny

      competating

      probably a typographical error, but what is this word supposed to be?

      --
      Thanks to the internet, we can now all die alone together! -SomeWoman
    13. Re:Sad by arivanov · · Score: 1
      keep diverging from intel

      Minor problem here. What if Intel takes their prerelease specs and implements them again (just like with the Xeon 64bit extensions)?

      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
    14. Re:Sad by Nintendork · · Score: 1

      I remember that IBM and Motorola were working together. I've been out of the Apple community for a while now. Did things change?

      -Lucas

    15. Re:Sad by Anonymous Coward · · Score: 0

      nice wrong answer.

    16. Re:Sad by Pieroxy · · Score: 1

      If they diverge from Intel, they're dead. See, Intel is still the norm and is here to stay.

      I honestly don't know how AMD could get out of the outsider solution.

    17. Re:Sad by Anonymous Coward · · Score: 1, Funny

      My advice, "sell".

    18. Re:Sad by SideshowBob · · Score: 4, Insightful

      The 2-4% is overall market share. You have to consider that an awful lot of WinTel PCs end up as cash registers or some other single-purpose vertical market application. In the market for "i'm going to buy a computer, sit it on my desk, and interact with it" I think Apple's share is probably higher. Would you buy a Mac to use it as a cash register? Unlikely unless you happen to be Apple. Would you buy a Mac for office productivity, email, web browsing, and maybe a game or two? Reasonable people can and do say yes.

    19. Re:Sad by Anonymous Coward · · Score: 0

      but not many... Besides, we are talking servers here. Not many big Mac server shops out there...

    20. Re:Sad by daveschroeder · · Score: 5, Informative

      No one uses Motorola's chips for PCs anymore. All of Apple's PowerPC chips come from IBM, and IBM uses its bigger cousin (the POWER chip) in its Unix servers.

      Actually, Apple gets all of the 74xx family (G4) chips - i.e., all PowerBooks, iBooks, current iMacs, etc...in other words, the majority of computers it sells - from Motorola (the semiconductor unit now being "Freescale").

      Only the recent 75x (G3) and 97x (G5) family chips come from IBM, and Apple doesn't ship anymore G3-based machines.

    21. Re:Sad by thejoelpatrol · · Score: 1

      Even the newest Powerbooks have Motorola chips in them, and the next generation may feature dual-core Freescale (Moto) G4's. iBooks don't use IBM chips, either

    22. Re:Sad by Cobalt+Jacket · · Score: 1

      PowerPC

    23. Re:Sad by 4of12 · · Score: 4, Insightful

      It's truly scary how the Intel is becoming the only mainstream chip architecture left alive.

      That dominant 386 instruction set has grown larger than life, threatening even Intel, who was responsible for its initial creation.

      Intel's Itanium line has been a business flop, while AMD stuck to x86 compatibility in its K8 x86-64 development and is thereby is making inroads into Intel's market.

      The realities of a market demanding

      1. cheap,
      2. standard and
      3. backward compatibility
      are dictating to mighty Intel where they have to go if they don't want to end up dead-ended in the high end RISC market like SPARC, PA-RISC, MIPS and Alpha.
      --
      "Provided by the management for your protection."
    24. Re:Sad by TheGavster · · Score: 1

      For PPC to be accepted, they must emulate the norm (IA32) as well as the originator of the norm, and then diverge doing something so revolutionary that people want to switch over. This is what AMD did, and now they are an actual player. They made really good copies of Pentiums, and then came out with their 64-bit extensions. Intel did the following and emulating in that move.

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

      It eats x86 words, and shits x86 words, therefore it's an x86 processor.

      To vomit up implementation differences from an arstechnica article doesn't make them any different in practice, only performance.

    26. Re:Sad by sp0rk173 · · Score: 2, Insightful

      Competing. I saw that right after I hit submit, and cringed in fear of spelling nazis.

      Competating is kind of a neat sounding word, though.

    27. Re:Sad by Anonymous Coward · · Score: 0

      Actually, they managed to leap in front of intel with X86-64bit - in the end, Intel had no choice but to follow suit and adapt to the new AMD standard.

    28. Re:Sad by sp0rk173 · · Score: 2, Insightful

      It would be a slow evoultionary process. They've already started it by implementing x86-64, and Intel had to play catch-up. I would imagine them continuing the AMD64 line for a while, then crafting another intersting innovation, and continue, in an iterative fashion, while you see big propritary operating systems like windows adapting to their changes and taking advantage of it (assuming these changes are beneficial to adapt to, of course). Slowly you'll see two different achitectures emerge from the same base arch as 64-bit becomes commonplace. I think the fan base behind both AMD and Intel will keep both companies alive, so long as they both perform on around the same level. It'll probably take a damn long time - if it happens at all - but with x86-64, amd showed that it can actually innovate and not just make a cheap, fast, hot pentium-clone. If they keep that up, and keep their quality where it's at right now...i think it could happen.

    29. Re:Sad by Blakey+Rat · · Score: 1

      Plus all the game consoles (except Sony) are using PowerPC chips in their next generation machines. (And I believe GameCubes have them now.)

      There's a lot of PPC chips in production and in all kinds of devices. 68k, however... I'd bet 68k is mostly dead, if not altogether dead.

    30. Re:Sad by atrizzah · · Score: 2, Informative

      Well not totally dead. TI is still rockin the 68k's in their higher end graphing calculators, for one thing

    31. Re:Sad by grahamlee · · Score: 1

      Erm, they kindof do emulate IA32... and there are plenty of architectures that don't have x86 emulators (of note, anyway) and get along fine. None of the SPARC or PowerPC boxen where I work have so much as a SunPCI, let alone any emulated x86. IA-32 isn't the "norm" in a number of environments.

    32. Re:Sad by grahamlee · · Score: 3, Informative

      It's still the CPU to teach machine language or assembler on, and I even know people who are still using old SUN or similar-vintage workstations based on the m68k. The MC6809E CPUs also make good washing machine controllers, alledgedly.

    33. Re:Sad by Anonymous Coward · · Score: 0

      You mean the one's BASED on Intel's architecture?

      ONES. It's ONES. You don't need an apostrophe there!

      When is the rest of the world going to learn to spell?

    34. Re:Sad by upsidedown_duck · · Score: 1

      Competing. [fragment] I saw that right after I hit submit, [misplaced comma] and cringed in fear of spelling nazis.

      What about the grammar nazis? Grammar nazis need to feel loved, too!

      --
      -- "Makes Little Debbie look like a pile of puke!" - Moe Szyslak
    35. Re:Sad by Anonymous Coward · · Score: 0
      What about the grammar nazis? Grammar nazis need to feel loved, too!

      No, "feared." Not "loved." We're not talkin' about the "grammar fluffy bunnies" here.

      And "Nazi" is usually capitalized.

      Feelin' the love now, Spunky?

    36. Re:Sad by Halfbaked+Plan · · Score: 1

      Motorola saw the 'desktop wars' for PC-oriented processors as a money-sinking disaster and bailed out of PPC awhile ago. I'm personally glad they did so, because their core competence is in embedded chips. I would have hated to see their relationship with Apple pulling the whole Motorola processor operation down.

      --
      resigned
    37. Re:Sad by drinkypoo · · Score: 1

      First of all, vomiting up stuff from ars technica is the last thing I want to do. I like the site as much as the next guy but plagiarism isn't interesting or entertaining enough - if I were using Ars as a resource, I'd make a citation. Second of all, no one said it wasn't an x86 processor, though I would say that about Hammer-core chips - I said they weren't intel architecture processors, which is up for debate but technically correct.

      Third: Come in out of the cold and join us - register as a slashdot user. Or, if you just checked the box to indicate cowardice, have the courage of your convictions and post as yourself.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    38. Re:Sad by Anonymous Coward · · Score: 0

      Where are all these 'reasonable' Mac users?

    39. Re:Sad by Antique+Geekmeister · · Score: 0

      Of course: they've been stealing all the marketable, already developed aspects of other architectures for years and using it to save R&D dollars and re-inforce the x86 monopoly.

      Too bad they've now gotten so market-controlling they'll have to do their own R&D, unless AMD can manage to stay ahead with things like an actual 64-bit architecture instead of that fake 64-bit nonsense Intel is marketing.

    40. Re:Sad by Anonymous Coward · · Score: 0

      RISC and CISC apply only to instruction sets. Not architectures.

      Reduced
      Instruction
      Set
      Computing

    41. Re:Sad by roomba · · Score: 1

      The Pentium Pro (which came out just before k5) was the first processor to use an internal RISC format, called PRISC (Pentium RISC). AMD followed with K5. So AMD is not more 'RISCy' than Intel. Besides, its *not* that current AMD and Intel chips are RISC architectures with x86 emulators. They're still x86 architectures: just that instructions, after being decoded, look more like RISC instructions. For the more technically inclined, this is needed because you want the register numbers and opcodes to be in fixed places internally. These architectures still need to decode complicated CISC instructions, and therefore, a number of pipeline stages are allocated to decode. Which was the original argument for RISC processors. There are no 'emulators' inside any of the AMD/Intel x86 processors. Maybe you were referring to the Itanium, which has an x86 emulator, or the Transmeta Crusoe, which also has one. I, for one, am a big fan of RISC architectures. Unfortunately, they're pretty much dead and buried, and that too for completely non-technical reasons. The mainstream general-purpose architecture is x86, which is a really ugly instruction set.

    42. Re:Sad by Halfbaked+Plan · · Score: 1

      I have a Macintosh SE/30 running NetBSD. It has a 2 gig hard drive in it and 32 megs of RAM. Since I hardly ever go over and touch the actual machine it classifies as a server. A slow file server, in fact.

      Running X11 on it is sorta a trip.

      --
      resigned
    43. Re:Sad by Halfbaked+Plan · · Score: 1

      The MC6809E CPUs also make good washing machine controllers, alledgedly.

      Not the 6809 so much as the 6805 and some of it's derivatives in the 6808 family. There are scads of them all over the place in appliances and automobiles.

      I want a 68K based Sun box but haven't chased one down yet.

      --
      resigned
    44. Re:Sad by Predius · · Score: 3, Insightful

      'fake 64-bit nonsense' - Care to elaborate?

      emt-64 is an amd-64 compatible extenstion to the P4. How is it fake 64 bitness unless Opteron and the A64 line are also fake 64 bit nonsense?

      Or are you refering to Itanium? Last check, it was a fully 64 bit capible sysetm, no signs of 'fake 64-bit nonsense' there either.

      Geez, if you're going to troll, atleast do a good job at it.

    45. Re:Sad by Halfbaked+Plan · · Score: 1

      Apple gets all of the 74xx family (G4) chips

      I guess I'm old fashioned. When I think of the 74xx family, the only CPU-like that comes to my mind is the 74181 ALU. I guess maybe some of the shift registers and latches, too, though.

      --
      resigned
    46. Re:Sad by macjohn · · Score: 2, Interesting

      The best architecture doesn't win. I know. I was personally involved in the battle for 16 bit processors: 8086 vs several others.

      "Other" won every single engineering battle as the best architecture, but Intel brought rooks of vice presidents into every board room and convinced companies that Intel was the better choice, regardless of architecture.

      Intel won.

      Signed:
      Operation Crushed.

      --
      --Hi. I'm in Portland and it's raining. This appears to be a permanent condition.
    47. Re:Sad by Anonymous Coward · · Score: 0

      When is the rest of the world going to learn to spell?

      Right after you do.

    48. Re:Sad by grahamlee · · Score: 1
      I want a 68K based Sun box but haven't chased one down yet.

      I occasionally see them on eBay but not for sensible moneys...the oldest SUNW box I have is a MicroSPARC :-(. Just have to make do with the NeXT slabs for the time being I suppose!

    49. Re:Sad by Anonymous Coward · · Score: 0

      Wow, you've only just noticed a Gecko rendering bug that everyone on Slashdot has been complaining about for the past two months.

      You

      cock

      gobler.

    50. Re:Sad by Antique+Geekmeister · · Score: 1

      I urge you, sir, to actually hop over to www.tomshardware.com and read the evaluations of the Intel 64-bit chipsets. They're 64-bit like gluing 4 extra cylinders onto the roof of your car makes it a V-8 engine: there's enough funky glue and plumbing to actually make the cylinders fire, for a little while, but it tends to fall off under load and leave the system dead on the roadside.

    51. Re:Sad by TonyMeatballs · · Score: 1

      It's going to be difficult for AMD to diverge too far, to the point where they are so different from the Intel architecture that they no longer run the same binaries. As much as I am not a fan of windows, this probably wouldn't happen until AMD has enough support from Microsoft to make a second version of MS Windows geared towards the AMD architecture... something I can't see happening in the near future.

    52. Re:Sad by bhtooefr · · Score: 1

      Virtual PC doesn't run on the PPC 970s, because it relied on the fact that the previous chips could be switched into little endian...

    53. Re:Sad by bhtooefr · · Score: 1

      Then again, the K6 was hardly an AMD design...

      It was to be the NexGen Nx686, but they decided they couldn't compete against Intel, AMD, Cyrix, and IDT, and AMD needed some help in design, so they bought out NexGen, and the Nx686 design was retrofitted to Socket 7, and released as the AMD K6.

    54. Re:Sad by bhtooefr · · Score: 1

      Huh? The NexGen Nx586 was the first x86 RISC chip. The K5 was hardly a RISC chip. The K6, on the other hand, was very much a RISC chip (in fact, it was originally going to be called the Nx686 before AMD bought NexGen out).

    55. Re:Sad by Predius · · Score: 1

      And A64 is any different how? They are both extentions to a 32bit isa, which was an extention to a 16bit isa... I urge you to hop over to Anandtech and see their comparison which shows their implimentation working quite nicely.

      Don't bother reposting unless you have actuall technical details to discuss.

    56. Re:Sad by poisson_bete · · Score: 1

      There are 2 games for Macs now? Where is the other one?

    57. Re:Sad by Lost+Race · · Score: 1
      No, chip "architecture" generally means "Instruction Set Architecture" by default unless further qualified. Implementation details like pipeline stages, cache associativity, TLB organization, bus widths, etc, are sometimes referred to as "microarchitecture". AMD's x86 chips have different microarchitectural features from Intel's (and from each other!) but they share the same architecture (i386) with some varying extensions (3dnow, x86-64).

      Calling any x86 chip "RISC" is a big big stretch of the terminology. The microcode engines inside the last few generations are sort of RISCy but that is an implementation detail, not an architectural feature.

      Disclaimer: I am not an IC designer, but I have been reading comp.arch for 10 years.

    58. Re:Sad by Lost+Race · · Score: 1
      Ooops, my fingers got ahead of my brain and typed "microcode" when I meant "micro-op". Try this instead:
      The micro-op engines inside the last few generations are sort of RISCy but that is an implementation detail, not an architectural feature.
    59. Re:Sad by grahamlee · · Score: 1

      The version I heard for "this doesn't work" is that the code did something that, back when 32-bit PPC was all there was, worked and no-one assumed that this would change, then it did change for the 64-bit PPC which kindof scuppered the plan. One or more of us may be wrong, and I expect it's at least me.

  6. Barely Knew Ya... by blueZhift · · Score: 1

    Goodbye Alpha, I barely knew ya... I remember at Fermilab when we got our first batch of Alpha powered Vaxes how wicked fast they were. And I think Altavista was running on Alphas in those days too.

    1. Re:Barely Knew Ya... by jpmkm · · Score: 4, Informative

      IIRC, Altavista(originally altavista.digital.com) was just a little demo project used to show off the digital alpha systems that it ran on.

    2. Re:Barely Knew Ya... by Anonymous Coward · · Score: 0

      Alpha powered Vaxes

      They were almost as cool as my first batch of PowerPC powered Apple ]['s

      (In case you don't get the joke, Alpha and Vax are completely different architectures and the parent's post is completely retarded.)

    3. Re:Barely Knew Ya... by Nutria · · Score: 1

      when we got our first batch of Alpha powered Vaxes

      There's no such thing as as Alpha-powered VAX. Both the Alpha and VAX are chip architechtures.

      --
      "I don't know, therefore Aliens" Wafflebox1
    4. Re:Barely Knew Ya... by Anonymous Coward · · Score: 0

      When they look at Intel and Google know, I bet they can't believe how much they must be kicking themselves for having the best CPU and the best Search Engine; and screwing it all up by trying to become a reseller or Windows. Has such stupidity ever been achieved in the business world before?

    5. Re:Barely Knew Ya... by avronius · · Score: 1

      My first introduction with Alphas were running Windows NT 3.something. That was the least stable OS, but the machines kicked some serious butt as raster(ized) image processors (RIPs). Back around 93 I think.

      I suddenly feel old.

    6. Re:Barely Knew Ya... by javiercero · · Score: 1

      Actually the firs series of big Alpha systems (7000) were a VAX with an alpha CPU. So the parent wasn't that retarded afterall.... so believe it or not your apple ][ analogy wasn't a joke but a real description of what the early alpha servers were. /EOL

    7. Re:Barely Knew Ya... by avronius · · Score: 1

      It is quite likely that this person has mistaken VMS with VAX. Unfortunately, an all too common mistake.

    8. Re:Barely Knew Ya... by Jeremy+Erwin · · Score: 1

      Dec did release the VAX 7000 and VAX 10000, both of which used the Alpha processor. They weren't terribly compatible with the original VAX architecture, though.

    9. Re:Barely Knew Ya... by Anonymous Coward · · Score: 0

      > There's no such thing as as Alpha-powered VAX.

      I beg to differ.

      > Both the Alpha and VAX are chip architechtures.

      You're correct in a sense. It is true that VAX (Virtual Address eXtension) refers to the original CPU in these systems, but it's also the name of the machine.

      The same was true of IBM's AS/400, where the machine and its proprietary CPU had the same name -- until PowerPC processors took their place.

      Similarly, the VAX was updated to use Alpha CPUs. Eventually HP retired the name "VAX" and just called the machines AlphaServers running OpenVMS. Same difference, just a marketing change...

    10. Re:Barely Knew Ya... by wfbush · · Score: 2, Insightful

      What the hell are you all talking about?!

      VAXes (surprise, surprise) had VAX CPUs, not Alphas.

      They had to rename the operating system from VAX/VMS to Open VMS/VAX and OpenVMS/Alpha.

      Kids today... I'm surprised no-one's made a comment about Pentium-powered PowerMacs or something equally non-sensical.

    11. Re:Barely Knew Ya... by javiercero · · Score: 1

      Actually it is VAXen, as in FOXen...

    12. Re:Barely Knew Ya... by wfbush · · Score: 1

      No, the VAX 7000 and 10000 used VAX CPUs

      They released DEC7000 and 10000's with Alphas

  7. amd is niche?? by lavaface · · Score: 1

    interesting . . . doesn't seem that way to me

    1. Re:amd is niche?? by MoralHazard · · Score: 2, Insightful

      I think we're conflating "manufacturer" with "architecture", here. AMD's 32-bit offerings are basically software-compatible with Intel's 32-bit stuff (the exceptions would be SSE2 and such).

      I guess the poster's point was that there aren't any widely-used architectures out there besides the x86 stuff, which was originally developed by Intel, was a solely Intel offering for a very long time (close to 15 years, I think), and which is still synonymous with Intel. Despite the fact that AMD, VIA, and a couple of other outfits make x86 CPUs.

    2. Re:amd is niche?? by Mateito · · Score: 1

      Agreed.

      If Taco had was talking about architectures, you could lump it all under Intel, but AMD are definitely a force.

      Maybe they're enhanced instruction sets will set them apart in the future.

      Wouldn't suprise me if we see some collaboration between AMD and Sun on a hybrid Risc set at some point in the future.

    3. Re:amd is niche?? by Anonymous Coward · · Score: 0

      AMD chips are the same architecture as Intel's. The poster was obviously referring to architectures, not manufacturers.

    4. Re:amd is niche?? by fitten · · Score: 1

      AMD has their own line of RISC type microcontroller processors (AMD29000 IIRC is one of them) in addition to their Intel x86 ISA processors.

    5. Re:amd is niche?? by Kiryat+Malachi · · Score: 5, Informative

      PowerPC architecture is probably more widely used than x86.

      ARM architecture is VERY widely used.

      M68k architecture is still used.

      Just because desktops and servers don't use it doesn't mean it isn't used. For example, I worked on a program that sold ~2 million PowerPC chips per year. For one automotive module. How many Pentium 4s does Intel sell in a year? A lot, to be sure, but the number of chips used in embedded applications dwarfs that of desktops, and in the embedded arena there's still a ton of choice of architecture.

      --

      ---
      Mod me down, you fucking twits. Go ahead. I dare you.
      (I read with sigs off.)
    6. Re:amd is niche?? by Nutria · · Score: 1

      was a solely Intel offering for a very long time (close to 15 years, I think)

      There have been 2nd sources for Intel chips since the late 70s. Some, like the Z80 and the AMD64, have been supersets, and others were/are strict work-alikes.

      Zilog, AMD, Harris, Next-Gen, Cyrix & IBM all have been 2nd sources.

      --
      "I don't know, therefore Aliens" Wafflebox1
    7. Re:amd is niche?? by Nutria · · Score: 1

      program that sold ~2 million PowerPC chips

      Many dozens of millions (pushing 100M) of x86 chips are sold each year.

      That dwarfs everything except the "small stuff": 8085, MC68K/Dragonball, 6809, etc.

      --
      "I don't know, therefore Aliens" Wafflebox1
    8. Re:amd is niche?? by tverbeek · · Score: 4, Informative
      the x86 stuff ... was a solely Intel offering for a very long time (close to 15 years, I think)

      Which 15 years? In the early years of the "IBM PC" architecture, Intel (which didn't have the manufacturing capacity it has today) directly licenced Harris, AMD, IBM, and Hitachi to make their own 808x/80286 chips. (Lots of IBM-brand computers had "IBM Inside", not Intel.) There were also the NEC V20 and V30 chips, which were unlicenced 808x clones. Then AMD, Cyrix, IBM, and TI all produced 386-equivalents, and then the whole slew of 486-alikes that prompted Intel to switch to the trademarkable "Pentium" name, while others sold similar "586" and "686" chips. Which brings us to the modern crop of AMD Athlons, Transmeta Crusoes, VIA C3's and such to which you referred. I'm not sure there was even a 15-month period in which Intel was the only source of x86-compatible CPUs.

      --
      http://alternatives.rzero.com/
    9. Re:amd is niche?? by Kiryat+Malachi · · Score: 3, Informative

      Sorry. I said ONE PROGRAM. I.E. one specific module. That performed one specific function in an automobile. Not even a very big program. I work for someone who buys PPCs, not makes them - I have no idea what total sold is, but it dwarfs x86.

      Most automobiles currently sold have at least 5 embedded processors in them. Some have upwards of 50. Very few of those (I've never even run across one, actually) are x86 architecture. The point is that while x86 may lay claim to the desktop, the desktop is an absolutely minimal part of the entire CPU market, and x86 barely even plays in that market.

      --

      ---
      Mod me down, you fucking twits. Go ahead. I dare you.
      (I read with sigs off.)
    10. Re:amd is niche?? by Dogtanian · · Score: 1

      That dwarfs everything except the "small stuff": 8085, MC68K/Dragonball, 6809, etc.

      8085? 6809? My God, they're still using those?!

      Now I'm curious. Do you have any good examples of their use? (Google turned up a lot of info, but very few applications).

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    11. Re:amd is niche?? by Cobalt+Jacket · · Score: 3, Informative

      He was talking about one product line. How many cars use Bosch Motronic? That's PowerPC. How many Fords? That's PowerPC. How many Cisco devices? How many Macs? How many GameCubes (and coming up, Xbox2/PS3/Next gen. Nintendo), how many other devices? How many PowerPC-based printers? And, well, you can count a few satellites and planetary probes.

    12. Re:amd is niche?? by bofkentucky · · Score: 1

      I seem to remember 286/16's ending up in the Chrysler K-Car back in the early pentium days, of course it could have been Popular Science blowing smoke.

      --
      09f911029d74e35bd84156c5635688c0
    13. Re:amd is niche?? by Kiryat+Malachi · · Score: 1

      I just said I'd never seen one, not that it didn't happen. But the majority of the automotive programs I've seen use M68K/Coldfire, SuperH, HCXX, PowerPC, and TriCore architectures.

      --

      ---
      Mod me down, you fucking twits. Go ahead. I dare you.
      (I read with sigs off.)
    14. Re:amd is niche?? by Detritus · · Score: 1

      I recently bought a programmable scientific calculator (HP-33S) that uses a single chip processor with an enhanced 6502 core as its CPU, along with RAM, ROM and LCD controller logic. The 6502 is from the same era as the 8080A and the 6800. It was the first cheap 8-bit microprocessor.

      --
      Mea navis aericumbens anguillis abundat
    15. Re:amd is niche?? by afidel · · Score: 1

      Nope, AMD had an 8080 compatible chip is 1974 as seen here.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    16. Re:amd is niche?? by Anonymous Coward · · Score: 0

      How many Fords? That's PowerPC.

      The big 3 buy from the lowest bidder. It may be PPC this year, M68K the next, or Intel if they give them $2 off for orders of 10,000 or more. The 94 - 97 Mustang could have 3 different processors for engine management depending on the date of manufacture: Motorolla, Intel, and I forgot the third.

    17. Re:amd is niche?? by Halfbaked+Plan · · Score: 1

      Well, cripes. If you're gonna be that way about it, then the dominant processor in the marketplace is probably a Hitachi 4 or 8-bit processor, or maybe a Motorola 68HC05, 08, or 12 part. Maybe even the lowly PIC.

      After all, there are 'multipler effects' that completely null out Intel, AMD, and PPC chips, i.e. every computer that has an Intel/AMD/PPC processor as it's main cpu has a scad of the little chips in it. With every keyboard and every mouse having a processor of some time, it's easy to demonstrate that the 'main desktop' processors are by definition in the minority.

      --
      resigned
    18. Re:amd is niche?? by Anonymous Coward · · Score: 0

      There have been a clones of all Intel desktop microprocessors except the 4004. Even the 8008 had Russian equivilents.

    19. Re:amd is niche?? by Kiryat+Malachi · · Score: 1

      The big 3 buy from the lowest quoting supplier, actually. They don't do much on their own anymore.

      And Intel's offerings these days are not very good compared to the competitors.

      --

      ---
      Mod me down, you fucking twits. Go ahead. I dare you.
      (I read with sigs off.)
    20. Re:amd is niche?? by Kiryat+Malachi · · Score: 1

      PPC isn't just desktop. PPC is, in fact, barely at all desktop. PPC sees a ton of use as the main embedded micro in systems ranging from network computing to automotive to scientific equipment.

      And yes, I am going to be that way about it, because its the truth. There are a lot of people employed making designs using and programming those smaller CPUs; just because you don't, don't assume no one cares about them. People say "Intel has 90% CPU market share" all the time; if they want to, they damn well better define the market.

      --

      ---
      Mod me down, you fucking twits. Go ahead. I dare you.
      (I read with sigs off.)
    21. Re:amd is niche?? by Halfbaked+Plan · · Score: 1

      AMD's 32-bit offerings are basically software-compatible with Intel's 32-bit stuff (the exceptions would be SSE2 and such).

      I suppose so. Unless you're into stacking enough AMD 2900 series bit-slice processors end-to-end to make a system 32 bits wide. 70's bipolar logic rulez.

      But that would be fun, unlike using a phillips screwdriver to assemble yet another PC Clone.

      --
      resigned
    22. Re:amd is niche?? by Halfbaked+Plan · · Score: 1

      The 'mulitplier effect' of there being always at least as many of a microcontoller-type as an Intel chip, (because for example, every PC has a mouse and every mouse has a small processor, often a PIC, in it, and almost every PC sold comes with a mouse) doesn't apply to the PPC family nearly as much as it does to the lesser parts, i.e. the stuff Motorola makes real money selling millions of (their salesmen are somewhat responsive if you only want a few hundred thousand, but that's a low-volume order).

      I haven't been following their embedded PPC market, since my focus has always been smaller, i.e. parts with under a few K bytes of RAM on-chip, but I know they've pushed it for years.

      --
      resigned
    23. Re:amd is niche?? by Halfbaked+Plan · · Score: 1

      But where AMD got the real muscle to be an Intel cloner (as opposed to the whole handful of vendors who were licensed to produce 8088 parts back in the heyday of the XT clone) was when they got their license to produce a '286 part. Something in the way the agreement was written gave them a 'foot in the door' right to produce their competing '386 part, which was a right they uniquely had, unlike the other non-Intel chipmakers.

      --
      resigned
    24. Re:amd is niche?? by mudshark · · Score: 1

      And aren't Z80s still around in gigalots of auto, industrial and consumer electronics applications? Not to mention the 68k...I bet the sum of those two venerable chips smothers the Intel population out there.

      --
      In other news, astrophysicists have announced that they now know what all that dark matter is: it's stupidity.
    25. Re:amd is niche?? by Lehk228 · · Score: 1

      as well as graphing calculators and game boy color, the sound chip in sega genesis, among other things.

      --
      Snowden and Manning are heroes.
    26. Re:amd is niche?? by Kiryat+Malachi · · Score: 2, Interesting

      Embedded PowerPC is doing pretty well these days, as the cost comes down. Somewhere else in the thread I mentioned working on a program that was using a couple million mid-high end embedded PPCs; there's definitely a place for them. OTOH, I just saw an article on a micro that, while it runs at 4 MHz and can't do much, costs 50c. Retail. On-chip crystal, too, so it really is single-chip, add power and ground. I think it has something like 256 bytes of flash and 64 bytes of RAM.

      That's just neat. It's a 4 MIPS processor, and it costs about as much as the postage to mail it.

      --

      ---
      Mod me down, you fucking twits. Go ahead. I dare you.
      (I read with sigs off.)
    27. Re:amd is niche?? by Dogtanian · · Score: 1

      Yeah, I remember the 6502; it was the CPU in my first computer (Atari 800XL) and I wrote some simple stuff for it.

      However, I'm kind of surprised that they used a chip that simple inside a moderately powerful calculator, if only because of the speed ('course, there's a very good chance that the embedded 6502 is running *way* faster than the traditional ones could).

      I guess that most calculators don't have to be all that clever (the scientific ones out 15 years ago weren't much more primitive than the majority being sold today; the price has maybe halved, but in technology terms, they've remained static).

      Wonder if anyone will release a (probably unofficial and possibly "illegal") kickass calculator app for the Nintendo DS when that arrives. I can just see all the geeks in maths(*) class using their DSs and getting into trouble from their less techno-friendly teachers.

      (*) Dammit... I almost said 'math' there. I've been reading this damn website so much I'm turning into an American. Sigh...

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    28. Re:amd is niche?? by bhtooefr · · Score: 2, Informative

      Umm... there's a difference between 2nd source and clone.

      Zilog's Z80 was a CLONE of the 8080.
      AMD WAS a second-sourcer until the Am486.
      Harris was a second-sourcer until the 386, at which point they dropped out.
      NexGen? I thought they made the Nx586 and Nx686 (released as the AMD K6), never any Intel chips under license. They were fabless, and used IBM.
      Cyrix? Same here. I thought they designed their own chips. They were fabless, though, so EVERY Cyrix chip was made by a CYRIX second-sourcer.
      IBM both designed their own chips (Blue Lightning) and was a Cyrix and NexGen second-sourcer, and is going to be a VIA second-sourcer at .09u.
      TI and ST were Cyrix second-sourcers.
      IDT designed their own chips (it could be argued that Centaur ran almost completely seperate from IDT, that Centaur was fabless, but was funded by and used the fabs of IDT, but it's a real stretch, as they WERE owned by IDT).
      VIA (well, Centaur) designs their own chips, and is fabless. They use TMSC for .13u, and will be using IBM for .09u.
      TMSC is a VIA second-sourcer.
      NEC was an Intel second-sourcer and designed their own chips (the V20 and V30).

      I think I got it all in there...

    29. Re:amd is niche?? by bhtooefr · · Score: 1

      When did the second-sourcers start? Remember, the 8086/8 didn't come out in 1981. The 8086 came out in 1978.

      Ah, AMD started in 1979. I didn't get months on those, but it could be as much as 23 months...

    30. Re:amd is niche?? by bhtooefr · · Score: 1

      Not really that much faster. While the 65C02 is available in up to 14MHz speeds, this is an 8502 (more commonly referred to as a 6502A). An 8502 is a 2MHz 6502, plain and simple.

      BTW, why would the 6502 be under-powered? After all, a ~1MHz 6510 (not any more POWERFUL than the 6502) can run a multitasking GUI with web browser and TCP/IP stack.

      I think a 4004 could almost do what this thing does... (albeit slowly)

    31. Re:amd is niche?? by Dogtanian · · Score: 1

      An 8502 is a 2MHz 6502, plain and simple.

      (Actually, I remembered after making my post that my Atari had the 6502A, not the 6502. Not that it matters...)

      After all, a ~1MHz 6510 (not any more POWERFUL than the 6502) can run a multitasking GUI with web browser and TCP/IP stack.

      Is that a reference to the Commodore 64? Yeah, I guess that's pretty impressive.

      I guess my way (*) of thinking is that normally it's not worth trying to optimise stuff, if it's running on a PC with performance that would have scared national security agencies a couple of decades earlier.

      But try to produce some cheap-ass calculator ICs, where every penny counts (I'd guess) and it'd probably be impressive to see what those motivated programmers could do given the constraints. (Not that the $50 calculator mentioned above seems particularly cheap)

      I think a 4004 could almost do what this thing does...

      Hey, they're all functionally equivalent to a Turing Machine, after all...

      (albeit slowly)

      Now, that *is* where the snag arises.

      (*) Actually, the modern way of thinking, which infected me...

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    32. Re:amd is niche?? by bhtooefr · · Score: 1

      Yes, it is Contiki on the C64.

      BTW, it's not as impressive on the Apple II, as it's a curses-style GUI, and the TCP/IP stack is implemented on the Ethernet card (there IS an A2 ethernet card that doesn't do that, but it costs $150 IIRC, so someone went the easy way out and offloaded the TCP/IP onto the card that ended up being used to get Contiki running on the A2).

    33. Re:amd is niche?? by tverbeek · · Score: 1
      If you're including the pre-IBM-PC era, ZiLOG introduced the Z80 (an unauthorized improvement on the 8080) in 1976. The 8080 didn't run MS-DOS, but in the days before Armonk entered the microcomputer market, CP/M was the "industry standard" OS, and the Z80 was a serious alternative to Intel's offering. It was even more popular than the 8080 itself, powering TRS-80s, Sinclairs, later game consoles, current embedded systems, etc.

      Competition is nothing new to Intel.

      --
      http://alternatives.rzero.com/
    34. Re:amd is niche?? by bhtooefr · · Score: 1

      I was referring to x86 second sourcers, not 8080 cloners. I think AMD actually started second sourcing in 1974, and I THINK it was the 8008 that they made (it might have been the 8080).

  8. Heh by Burgundy+Advocate · · Score: 5, Funny

    Isn't this the fourth or fifth time Alpha has died? Let it rest already!

    Zombie Alpha needs brains, badly.

    --
    Dragging people kicking and screaming into reality since 1996.
    1. Re:Heh by Mateito · · Score: 1

      But how many of those declarations came from NetCraft?

    2. Re:Heh by Anonymous Coward · · Score: 1, Insightful

      NetCraft confirms: NetCraft jokes are dying!

      Long live NetCraft jokes!

    3. Re:Heh by Mr2cents · · Score: 1

      It would have been really funny if Amiga had announced its' new Alpha-based hardware a week ago..

      (I owned two Amiga's, and its' endless death-struggle eventually made me switch to I-don't-care-anymore mode, after all, I had discovered GNU/Linux).

      --
      "It's too bad that stupidity isn't painful." - Anton LaVey
    4. Re:Heh by Bert64 · · Score: 1

      Funny you should mention that...
      When DEC were developing the alpha processor, they approached commodore and offered to port the amigaos to the alpha architecture.. the amigaos was always very efficient, and that coupled with the fastest processors available at the time would have made for an awesome machine.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  9. Niche guys.... by Chicane-UK · · Score: 3, Insightful

    Yeah, like that little known outfit called AMD. I know you might not of heard of them, but they do make some good chips ;) :)

    --
    "Hey! Unless this is a nude love-in, get the hell off my property!!"
    1. Re:Niche guys.... by badriram · · Score: 1

      And the King of them all IBM... (dont forget the Power architecture)

    2. Re:Niche guys.... by Anonymous Coward · · Score: 4, Informative

      He meant intel architecture, you could argue that AMD64 is a new arch but it's still X86. What sort of nerd are you anyway?

    3. Re:Niche guys.... by cuerty · · Score: 0, Flamebait

      And the nostalgic?
      There'll no like Alpha. Is like the Commodore 64 of servers.

      --
      >Linux is not user-friendly.
      It _is_ user-friendly. It is not ignorant-friendly and idiot-friendly.
    4. Re:Niche guys.... by drgonzo59 · · Score: 2, Informative

      AMD is still an Intel architecture.

    5. Re:Niche guys.... by erikharrison · · Score: 4, Insightful

      Lets say x86 instead, and then the meaning becomes clear. The reason we say "Intel" when we mean "x86" is because, no matter how many other manufacturers make x86 chips (Via, AMD, and doesn't Unisys have there own x86 chip?) the technology is Intel's. All the other companies are niche players when it comes to controlling x86 technology. Via is for embedded, AMD is for price to power in the midrange market, and Unisys is x86 for mainframes.

      The fact that AMD seems to be getting the upperhand in driving x86 technology doesn't change the fact that there is one technology which dominates the market, and everybody else either controls a nice slice with another technology, or competes with the major x86 player in a more specialized niche.

      Alpha is dead, UltraSPARC is in doubt, and Via seems intent on shoving ARM out of the market. m68k is an abberation. There are two battles left. The battle of the archetecture (x86-64 vs POWER5/PowerPC), and the battle of x86 innovation (AMD vs Intel). That's sad.

    6. Re:Niche guys.... by cadelor · · Score: 1

      I dont think the folks at sparc.org can be considered a niche either.

    7. Re:Niche guys.... by drinkypoo · · Score: 4, Informative

      No it isn't. Stop repeating this garbage. AMD has been making their own RISC-internals processors since the K5. The K5 is not very RISCy, but the K6 certainly is, although both of these processors, as well as the K7 (Athlon) and K8 (Hammer) all emulate the x86 instruction set. The Hammer-core processors in particular do not resemble the cores of the older intel processors, or did you totally fail to notice the 16 externally-expressed 64 bit registers? Intel's cores meanwhile have also changed dramatically since the simple days of the 486 and they have many more registers than are directly addressable, and utilize register renaming (among many other techniques) to speed up execution.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    8. Re:Niche guys.... by Just+Some+Guy · · Score: 2, Interesting
      You mean, AMD64 is just like IA32, with the exception of different operators, wider paths, different supporting chipsets, different interconnects, and a metric buttload of registers (but other than that they're identical)?

      No, I wouldn't say that AMD is an "Intel architecture", although they make a line of chips that implement an Intel ISA. Their new stuff is markedly different.

      However, I admit that there are better examples of non-Intel architectures, such as those made by the small upstarts IBM and Motorola.

      --
      Dewey, what part of this looks like authorities should be involved?
    9. Re:Niche guys.... by mahdi13 · · Score: 1

      Lots of people seem to confuse Intel with architecture.

      Intel makes x86 processors, same as AMD, VIA and a few others. Intel is a COMPANY not a PROCESSOR. They make processors (the public will never learn, but here's hoping the Slashdot will)
      When was the last time you heard someone call a Mustang a Ford? It's partially correct but inaccurate.

      Those that think AMD is a 'rip-off' of Intel are mis-informed. Back in the 80's Intel and AMD worked together and standardized the x86 architecture then went their separate ways, both owning the rights to use x86 (I think technically AMD licensed the rights but after much design change the license is no longer needed)

      Either way, I don't think the AMD64 was designed to compete against the Itanium, but to take the next step in x86 the architecture. If it was I would think the prices of the AMD64's would be closer to the $6000 that the Itanium holds.

      --
      "Some things have to be believed to be seen." - Ralph Hodgson
    10. Re:Niche guys.... by Anonymous Coward · · Score: 1, Interesting

      I assumed he meant manufacturers. If he meant architectures, then what about ARM? There are probably more ARM chips out there as there are chips from all other architectures put together. The PC/laptop/server market is pretty small compared to the embedded market.

    11. Re:Niche guys.... by avandesande · · Score: 1

      With the 64 bit extension amd has co-opted x86 and made it it's own, which is even more relevant because intel tried to kill x86 with itanic.

      --
      love is just extroverted narcissism
    12. Re:Niche guys.... by PedanticSpellingTrol · · Score: 2, Informative

      They've got a permanent cross-licensing agreement that lets either party use what the other comes up with.

    13. Re:Niche guys.... by Nutria · · Score: 1

      I dont think the folks at sparc.org can be considered a niche either.

      Sure they can. Significantly less than a million SPARCs are sold each year, and that qualifies the architecture as niche.

      --
      "I don't know, therefore Aliens" Wafflebox1
    14. Re:Niche guys.... by Jahf · · Score: 1

      But Hypertransport, which is a large part of what makes the Opteron/Athlon64 perform so well under load, was from a technology used for DEC Alpha buses.

      --
      It is more productive to voice thoughtful opinions (reply) than to judge (moderate) others.
    15. Re:Niche guys.... by Anonymous Coward · · Score: 0

      I agree, AMD64 has nothing to do with intel x86 and anybody who says it does must be able to read domain names. Or are you saying that AMD64 doesn't just support and extend the x86 instruction set?

    16. Re:Niche guys.... by Anonymous Coward · · Score: 0

      You've said this several times already. You're wrong.

      In the context of this article, the "architecture" is the instruction set. It is the part of the architecture of your system that is the result of the choice of CPU.

      If the article were about how CPUs were implemented (the internal architecture), then "intel architecture" wouldn't make any sense. The "pentium architecture" and the "pentium II architecture" are not the same. There is no standard micro-op instruction set used in all Intel CPUs. As that's internal to the implementation, there's no reason they have to keep it the same.

    17. Re:Niche guys.... by drinkypoo · · Score: 1

      I can't really make a decision on whether or not AMD64 is an extension of the x86 instruction set until I actually sit down and read the instruction set reference that AMD was kind enough to send me paper copies of, and examine the bytecodes for the instructions - that is the only real test.

      The AMD64 instruction set certainly looks like it's just an extension of x86 when I look at the mnemonics but that doesn't mean anything and I haven't taken the time (I have way too many other projects going, many of them not even computer-related) to make the determination.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    18. Re:Niche guys.... by drgonzo59 · · Score: 1

      I wasn't referring to the 64 bit AMD processors just to ones designed to compete with I32. It doesn't matter how the Intel x86 instruction set is implemented or what microinstructions are used in the core, the point is that an x86 instructino set is exposed to be compatible with Intel's x86 architecture. Whatever executable runs directly on Pentium IV will run directly on an Athlon (except for ones taking advantage of some SIMD instructions). On the other hand Alpha has a different instruction set. You would need a different executable compiled specifically for Alpha architecture.

    19. Re:Niche guys.... by drinkypoo · · Score: 1

      Intel architecture doesn't make any sense, that's why people calling it ia32 instead of x86 is so annoying. The processors are not the same architecture. Even intel processors are not tied to x86, that's just the kind of decoder they stick on the front.

      P.S. I heartily encourage you to get over your cowardice.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    20. Re:Niche guys.... by Anonymous Coward · · Score: 0

      yeah.. and what about Frito-Lay

    21. Re:Niche guys.... by Anonymous Coward · · Score: 0

      There's an ABI reference on the site I linked, but like you I just have too many projects to sit down with the docs :-( As somebody below said, the instruction set is the defining characteristic of a processor, even if I do appreciate your technically-correct pedantry ;-)

    22. Re:Niche guys.... by canavan · · Score: 1

      There are at least two different definitions for "computer architecture" in use. One is used by hardware people, the other one by software people, the latter beeing essentially equivalent to "instruction set". You - like many other posters here - are a hardware person, the AC is not.

    23. Re:Niche guys.... by drinkypoo · · Score: 2, Interesting

      The technology isn't even intel's, only the instruction set is. The technology in between fetch and store is all entirely different not only between AMD and Intel (at least since the K5, the Am-386 is not significantly different from the i386 as far as I know) but also between one generation of intel processor and the next - From what I understand there's not all that much difference between P2 and P3, but P3 and P4 are pretty different, as evinced by the fact that intel has decided that they have to base their next generation of processor (multi-core) on the Pentium M, which is based on the P3.

      I agree entirely that we should not say intel architecture, and that we should be referring to the instruction set, because what with the current state of computing, an instruction set does not necessarily imply anything whatsoever about the processor architecture. We have come a long, long way since the four stage pipeline.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    24. Re:Niche guys.... by cant_get_a_good_nick · · Score: 1

      All the other companies are niche players when it comes to controlling x86 technology.

      AMD Opteron x86_64 (renamed AMD64) is so successful that Intel had to, after numerous denials, copy it to it's chips, called EM64T. By that definition, AMD is not a niche player.

    25. Re:Niche guys.... by Frank+T.+Lofaro+Jr. · · Score: 0, Troll
      --
      Just because it CAN be done, doesn't mean it should!
    26. Re:Niche guys.... by julesh · · Score: 1

      I've heard that Intel made a lot of mistakes with the P4 architecture. Optimisation guides for it recommend avoiding several techniques that were very good on previous designs... for instance use of the Load Effective Address instruction, which apparently is substantially slower on a P4 than it is on a P3.

      One document said the mistake they made was in removing the ability for the processor to perform shift operations efficiently, presumably because a substantial number of transisters were previously committed to this and they wanted to reduce complexity.

    27. Re:Niche guys.... by Lost+Race · · Score: 1
      From what I understand there's not all that much difference between P2 and P3, but P3 and P4 are pretty different
      Intel "Pentium" x86 generations:

      P5 - "586" - Pentium, Pentium MMX
      P6 - "686" - Pentium Pro, Pentium II, Pentium III, Pentium M (and some Celerons and Xeons)
      P7 - "786" - Pentium IV (and some Celerons and Xeons)

      Nobody (especially not Intel) ever calls them "586" etc but if they had stuck with the original generational numbering system (86, 186, 286, 386, 486) that's what they would have been called.

      The P5 is characterized by dual-pipeline in-order execution; the P6 by out-of-order micro-op execution; the P7 by the trace cache and double-clocked ALUs.

  10. Cost of the servers by wolfemi1 · · Score: 4, Informative

    "Pricing for the ES47 and ES80 systems with the new 1.15GHz EV7 will start at $29,200 and $49,300, respectively."

    Holy crap! And here I was, thinking that the Xeon servers were expensive!

    1. Re:Cost of the servers by Kourino · · Score: 3, Insightful

      HP doesn't want people buying them, else they might realize that they perform better than comparitively- clocked Itanium kit :3

      (Though to be fair, Itanium 2 was a lot better ... what's on the IA-64 roadmap, I wonder.)

    2. Re:Cost of the servers by Anonymous Coward · · Score: 0

      IA64s designed by Alpha engineers. :)

  11. Steak in the heart of VMS now by random+coward · · Score: 0, Troll

    I suppose this should put a steak in the heart of OpenVMS, and now we can say VMS is dead now also? That will be at least one positive result of this.

    1. Re:Steak in the heart of VMS now by unstable23 · · Score: 1

      Steak? Mmmm, beefy OS.

      Some people still love OpenVMS, especially as it now runs on Itanium. It's pretty solid, and if they don't have to change, why should they?

    2. Re:Steak in the heart of VMS now by Echemus · · Score: 1

      Erm, I understand the porting effort of OpenVMS to itanium began a fair while ago. I really do not think we will see the end of OpenVMS any time soon have a look here for details.

    3. Re:Steak in the heart of VMS now by Anonymous Coward · · Score: 0

      I suppose this should put a steak in the heart of OpenVMS...

      Yeah, OpenVMS always did need a little more meat.

    4. Re:Steak in the heart of VMS now by homer_ca · · Score: 1

      Mmmmm... Steak....

      Seriously, this isn't a stake through the heard of OpenVMS. It's being ported to Intel Itanium, but this isn't very popular with the users. TheReg article here about HP World.

  12. The Alpha by BubbaThePirate · · Score: 1

    "I am the Alpha and the Omega, the first and the last, the beginning and the end." - Revelations 22:13.

    --

    -- "I'm not a religious man, but if you're up there, save me Superman..."

    1. Re:The Alpha by sidmystic · · Score: 1

      That's "Revelation," heathen ;)

      /pedantic SOB

    2. Re:The Alpha by Nutria · · Score: 1
      That's "Revelation," heathen ;)

      /pedantic SOB

      That's "The Revelation of St. John".

      If you want to be pedantic, at least get it right...

      --
      "I don't know, therefore Aliens" Wafflebox1
  13. AMD by Snowdog668 · · Score: 3, Insightful

    Does AMD count as one of the "niche guys"? Granted, they're not as big as Intel but I've always thought of them as the chip to buy when you don't want to buy Intel.

    --
    I wouldn't say I'm a bad gambler but the last time I went to Vegas I even lost a buck on the soda machine.
    1. Re:AMD by kneecarrot · · Score: 1
      So, what was the greatest thing *before* sliced bread?

      The cat's ass?

      --

      I always save my last mod point to mod up a good troll. You people are too serious.

    2. Re:AMD by vrtladept · · Score: 1

      I think the problem is that while AMD is a fine chip maker (I run an AMD processor proudly), they are essentially similar to the Intel processor as they were initially clones of the Intel x86 line.

      I think what people are worried about is that we will loose some of the diversity of research without chips like Alpha that have a different base architecture than the Intel Chip

      Of course I hope I just didn't put my foot into my mouth, I'm not an electrical engineer or anything. Can someone expound or clarify?

    3. Re:AMD by JLyle · · Score: 2, Funny
      Does AMD count as one of the "niche guys"? Granted, they're not as big as Intel but I've always thought of them as the chip to buy when you don't want to buy Intel.
      I think the author was lamenting that, given Intel's dominance of the microprocessor market, it seems truer than ever that niche guys finish last.
    4. Re:AMD by Anonymous Coward · · Score: 0

      Well, the newer AMD chips have a very different memory bus architecture (nicked from Alpha, in fact). And very nice it is too in high-end (or highish - high end for x86ish, low) SMP systems.

      Actually, both the AMD and Intel chips translate the abysmal x86 ISA into RISCy microops, so there is room for a lot of difference there, too.

    5. Re:AMD by Anonymous Coward · · Score: 0

      AMD is not niche. Not even close. They compete in many other markets Intel does not.

    6. Re:AMD by akuma(x86) · · Score: 1

      I would consider AMD slightly above a niche because they force Intel to react to their moves, even though they hover around break-even when it comes to making money - You can see that their stock price for the last couple of decades has literally gone nowhere while Intel's has increased exponentially.

  14. only intel? by lavaface · · Score: 5, Insightful

    what about IBM's powerPC ???

    1. Re:only intel? by akuma(x86) · · Score: 5, Insightful

      IBM is a niche. Sun is a niche. Alpha, even in it's glory days, was a niche. AMD has 15-20% of the x86 market and is just slightly larger than a niche.

      Intel ships 1 million Prescotts a week(http://www.xbitlabs.com/news/cpu/display/2004 0512151634.html). This is not even full production capacity. This all done in 90nm technology -- a full 6 months ahead of anyone else. There were on the order of hundreds of millions of Northwoods sold and they are still selling.

      That's probably more volume in a single week than the entire IBM + Sun + Alpha volume for an entire year.

      Why is this the case? It is RIDICULOUSLY expensive to manufacture CPUs in this day and age. If you DON'T ship on the order of 1 million a week, you will never recover the costs necessary to build the all of the fabs.

      This is why Sun will eventually abandon SPARC. This is why IBM loses money in their microelectronics division, but will probably maintain POWER and eat the costs for strategic reasons. This is why HP/SGI and others have gone with Itanium.

      This is not to discount the technical acheivments of the these CPUs. I design processors for a living and have great respect for the Alpha design team. But at the end of the day, the only reason someone is going to fund the design a computer is to make money. Only the profitable survive.

    2. Re:only intel? by ajs · · Score: 1

      Yeah, I kind of wondered about the PowerPC there... it's used ALL OVER in Macs, MANY embeded systems, IBM RISC machines (mostly AIX-based) and probably many other places I don't know about. Hardly a niche.

    3. Re:only intel? by bedouin · · Score: 1

      There's a PPC chip in every Gamecube as well.

    4. Re:only intel? by cloudturtle · · Score: 1

      Actually, it is IBM's power. PowerPC belongs to IBM, Moto, and Apple (that whole AIM alliance thing). Henceforth, there is only one designer of Power chips (although IBM has started to license out this tech) but two competing PowerPC shops (Moto with the G4 and IBM with the G3 and G5).

    5. Re:only intel? by HogGeek · · Score: 1
      Don't forget about the iSeries from IBM.

      It uses the POWER5 today!

    6. Re:only intel? by Kiryat+Malachi · · Score: 1

      ARM-based processors number about 400 million per year, last estimate I saw. The general number for microprocessors is around 4.7 *billion*. Most of which aren't x86.

      Now, if you had said "desktop" architecture, or even "workstation and desktop" architecture, I might agree with you, but the truth is that in the larger scheme of things, *desktop* is a niche.

      --

      ---
      Mod me down, you fucking twits. Go ahead. I dare you.
      (I read with sigs off.)
    7. Re:only intel? by codemachine · · Score: 1

      And soon there will be 3 of them in every X-Box 2, if the rumours about it were true.

    8. Re:only intel? by peawee03 · · Score: 1

      And the XBox 2 once released, IIRC.

      --
      I wish I could write clever and witty sigs.
    9. Re:only intel? by akuma(x86) · · Score: 1

      ARM-based processors number about 400 million per year, last estimate I saw. The general number for microprocessors is around 4.7 *billion*. Most of which aren't x86.

      Granted.

      I should have said something about dollar volume instead of unit volume. Intel makes more money from CPUs than anyone else.

    10. Re:only intel? by T-Ranger · · Score: 1

      At the last marketing-day I was at (IBM/Linux), IBM talked about how it uses Linux on their new fab plant. The largest ever IBM investement. The largest ever investement in New York state. $5,000,000,000. Construction costs. Expected life span: 5 years. I find it unlikely that IBM looses money at that level.

    11. Re:only intel? by akuma(x86) · · Score: 2, Insightful

      It's not like they're going to lose the entire 5 billion. They just haven't been making enough to recoup the costs of their fabs.

      "In the first quarter of 2004, IBM Microelectronics lost about $150 million" -- Source http://www.infoworld.com/article/04/04/21/HNibm_1. html

      IBM makes several billions in profit per year. A 150 million per quarter loss isn't going to bury them.

    12. Re:only intel? by Anonymous Coward · · Score: 0

      So they make it back by selling services to the new fab....

  15. Will anyone actually be *using* this? by sarahemm · · Score: 5, Insightful

    I can't see this bringing in much revenue. If I was a company currently using Alpha, it seems like a dead-end choice to buy yet another Alpha-based machine, knowing this was the last one. Seems like a better decision to migrate away now, rather than just prolong it.
    Of course, that's just my opinion, and business decisions rarely make much sense ;)

    1. Re:Will anyone actually be *using* this? by Cheeko · · Score: 2, Insightful

      I think the idea is that this is a migration move. This allows current alpha users more time to migrate off of alpha and to another HP platform, rather than forcing them right now particularly if a third party app isn't avialable yet. HP'd rather have customers on alpha, than not have them at all. They can migrate at their own pace.

    2. Re:Will anyone actually be *using* this? by johnalex · · Score: 4, Interesting

      Actually, we're signing for a new one in a few days now. If you have software running on OpenVMS, the Alpha is still the chip to have.

      BTW, we're retiring a 1994-model DEC (yes, Digital!) Alpha 2100 with a 200 MHz (yes, that's megahertz) processor. The thing has run 24x7 for nearly 10 years and probably averaged less than a day downtime a year. We downed it only for hardware upgrades. We're replacing it with an DS 25, 2 processors, 2 GB RAM (our original had a whopping 64 MB when we bought it) and 5 36 GB drives (our original 2100 had 4 1 GB drives, and we were top stuff in town!). My, I'm feeling old.

      --
      JA
      http://www.johnalex.org/
    3. Re:Will anyone actually be *using* this? by beowulf2003 · · Score: 1

      There are still a number of contracts esp. with the DoD (and a few with the French & Australian military too IIRC) that Compaq had signed that would use these machines. Don't forget that the number 3 supercomputer in the Top500 is still a Alpha machine. There are probably a number of applications in that arena that would cost more to port than simply upgrading to these machines.

    4. Re:Will anyone actually be *using* this? by tverbeek · · Score: 1
      If I was a company currently using Alpha, it seems like a dead-end choice to buy yet another Alpha-based machine, knowing this was the last one. Seems like a better decision to migrate away now, rather than just prolong it.

      Well, people started migrating away from Alpha years ago, which is why HPaqital made the decision they've just announced.

      But if that shiny new Alpha box in the window is going to be supported for another several years, and I need a bigger box that runs all my Alpha machine code right now, why wouldn't I buy it? I'm probably going to buy a new system after that in several years anyway, but that's a purchasing decision to make then, not now. This announcement simply means I can spend the time between now and then making sure all of my applications can run on something else... which is a lot better than doing it this month because the bigger box I just ordered has a PowerPC or something in it.

      --
      http://alternatives.rzero.com/
    5. Re:Will anyone actually be *using* this? by leandrod · · Score: 2, Insightful
      it seems like a dead-end choice to buy yet another Alpha-based machine

      Only that (1) Alpha still has more than good enough performance, (2) you stick to what you already have working, (3) competitors don't have yet a compelling story on the viability of their RISC offerings, (4) going Intel feels like downgrading, (5) HP's migration proposals are still ridiculous, because (a) there is no good substitute for Digital Unix yet, HP-UX being much inferior, (b) no one believes in Itanium.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    6. Re:Will anyone actually be *using* this? by 0racle · · Score: 1

      Your thinking like a home user/Small business user. Governments and many very large companies are running Alphas with Tru64 or VMS migrating away from those systems is a very tall order. As such those types of customers are going to be sticking with Alphas running VMS/Tru64 for as long as they can because it gives them the time to properly plan for the migration while at the same time upgrading their hardware to keep up with current needs.

      --
      "I use a Mac because I'm just better than you are."
    7. Re:Will anyone actually be *using* this? by flaming-opus · · Score: 3, Insightful

      As it turns out many HP customers are refusing to migrate to itanium/hp-ux. When one is considering real server-iron the currentness of the processor is not always of utmost importance. If there's a legecy app that runs on tru64 (I mean ultrix, I mean osf) and it's really expensive to port, a lot of shops are just going to keep running alphas until the wheels fall off and burn. [Look at all the guys still running on sperry 1100-series machines]

      True, it's a dead-end choice, but one that might limp along for another 6-8 years. Not everyone has the option of migrating NOW. That works if you're talking about tru64/apache to linux/apache, but not if your talking about tru64/Legecy-app-from-company-no-longer-in-busines s to anything else. A migration might cost millions of dollars. A dead-end alpha server might cost tens of thousands and put off the more for a long time.

      My call is that makes lots of sense.

    8. Re:Will anyone actually be *using* this? by Nutria · · Score: 1

      we're retiring a 1994-model DEC (yes, Digital!) Alpha 2100 with a 200 MHz (yes, that's megahertz) processor. The thing has run 24x7 for nearly 10 years and probably averaged less than a day downtime a year. We downed it only for hardware upgrades.

      We still have a 2100 (purchased in 1995, I think), that we maxed out years ago. Still usable as a development system for our small project, which runs on a cluster of AS100s.

      DEC sure did make good hardware, back in the day. Sigh

      Our GS1280s run OVMS 7.3 & Rdb 7.1. Kick-ass fast, Galaxy shared-memory clustering, SAN, the works, but flakier than any VAX or early AS ever were....

      --
      "I don't know, therefore Aliens" Wafflebox1
    9. Re:Will anyone actually be *using* this? by Anonymous Coward · · Score: 0

      If you've already deployed a bunch of Alpha hardware running OpenVMS or Tru64 and you have need for expansion immediately you don't really have a choice. Buying Alphas now to sate current demand while building your new infrastructure is a pretty attractive option.

    10. Re:Will anyone actually be *using* this? by papa248 · · Score: 1
      a lot of shops are just going to keep running alphas until the wheels fall off and burn. [Look at all the guys still running on sperry 1100-series machines]

      I work for a very large automotive supplier...at my plant we use a VAX running OpenVMS to process the broadcasts from Chrysler to know what parts to build and ship. Works great, that and 5 DEC servers we have connected to VT120s. Why upgrade/change what works fine?
      --


      The higher, the fewer.
    11. Re:Will anyone actually be *using* this? by tricorn · · Score: 1

      If now is the time to migrate, then it was actually time to migrate several years ago, to avoid being forced to migrate now. But, of course, that means it was time to migrate several years before that. Etc. SImilar reasoning says you should migrate off of whatever you're using immediately, because at some time in the future you'll have to migrate off of it. Everyone using x86 machines now should switch to using Itanium immediately.

      Being able to not migrate off of something that is working for you now is very valuable. It means you don't lock yourself into something that may turn out to be a bad choice, if only you had waited a little longer. For instance, migrating to Itanium right now would be foolish. Perhaps it will turn out to be a winner. Perhaps it will turn out to be a loser. Much better to examine the situation over the next several years to determine the answer. Perhaps one of the licensees of the Alpha processor will decide to continue developing and producing them. Maybe the big winner in in 5 years will be the PPC-64.

      Remember, whatever processor you end up with (either this new one, or continue with your old Alpha CPU if it still serves you well enough), it will basically last until it would have been time to switch to another more powerful system anyway. At that time, you'd have had to make a decision anyway on whether to stick with the same architecture or not. It's not like your current machines are all of a sudden going to stop working.

      It is, of course, prudent to start PLANNING for a migration path now, since your simple option (just switch to a faster Alpha) is not going to be very useful for much longer, and repair and maintenance will become more and more expensive as time goes by.

  16. Dead? by ThrasherTT · · Score: 1

    And here I thought Alpha had been dead for years... maybe it was just the impression DEC gave. Perhaps this is a lesson in self-fulfilling prophecy.

    --

    All Your Memory Are Belong To Java
  17. My Alpha Story by Anonymous Coward · · Score: 3, Funny

    *sniff*

    *sob*

    Oh, this is just too much for me to handle. The greatest Quake platform is dead.

    Good bye, cruel world!

    Really, tho, this is a shame. Alpha procs are (*sob* were *sob*) the fastest thing a mortal could get. Ignoring compile problems, I'd take an Alpha over an x86 or PPC any day.

    Back when Quake2 was the latest id title, I set up a dedicated server on my alpha box (a tiny multia). My roommate and I were amazed -- gameplay was glass -- it was actually better than running on an x86 dedicated server and better than running against a local server (same box). Could not believe it. It was so smooth.

    Sorry, I'm going to go get drunk cry a lot (I'm working on solaris today, and I just can't take all the pain).

    1. Re:My Alpha Story by Tickenest · · Score: 1

      id software also used to run a 64(!)-player Quake II deathmatch server on a 400 mHz Alpha. It was quite the place to be.

      --
      This is the NFL, which stands for "Not For Long" if you keep making those bulls*** calls.
  18. You can't handle the truth. by Anonymous Coward · · Score: 0

    Go pick on Realplayer today, apple zealots !!!

  19. freeshell by essreenim · · Score: 0, Offtopic

    Anyone use freeshell? My mail account is a freeshell account.
    *
    As far as I know their (Unix) cluster is Alpha 64 based. Guess they'll have to switch..

    1. Re:freeshell by Anonymous Coward · · Score: 0

      why would they have to switch?

    2. Re:freeshell by essreenim · · Score: 1

      in the future. I dont think Alpha's last forever, and my mail account is a lifetime deal, so..
      at some point I guess they'll have to switch. I hope they dont need to (for a long time) though..

    3. Re:freeshell by boffy_b · · Score: 2, Funny

      I for one, do. It runs on NetBSD on DEC Alphas. Dead OS on dead chips. :)

      --
      Windows is only $500 if your time is worthless.
  20. Don't forget PowerPC by PCM2 · · Score: 5, Insightful

    I'd say the PowerPC is a pretty mainstream architecture, considering how it shows up in everything from workstations to Power Macs to Cisco routers. Also -- sad, maybe, but scary? PC computers are kind of a niche market compared to all of the embedded applications out there. So what if it's all based on old Intel ideas, so long as you've got folks like AMD and Transmeta to keep pushing the envelope?

    --
    Breakfast served all day!
    1. Re:Don't forget PowerPC by MtViewGuy · · Score: 1

      The PowerPC and its related POWER CPU architecture will still be around for one reason: IBM.

      After all, IBM invented the POWER CPU architecture, and they're using this CPU architecture for many of their larger big iron machines.

      Also, the PowerPC CPU is still much-liked for its very powerful FPU section, something that makes for impressive work on programs that demand a lot of FPU power like illustration and multimedia editing programs that run on the current generation of Apple Macintosh machines.

  21. I like my alpha BYEBYE by Anonymous Coward · · Score: 0

    I run a very busy mail server running FreeBSD on a "COMPAQ" Dual Alpha 500

    its still qucik to this day

    1. Re:I like my alpha BYEBYE by Anonymous Coward · · Score: 1, Funny

      I run a very busy mail server running FreeBSD on a "COMPAQ" Dual Alpha 500

      So which will die first, BSD or the Alpha?

      / kidding

  22. niche? by dj245 · · Score: 0, Redundant
    the world's line of chips seems to have declined to Intel and a handful of niche guys.

    I'm no fanboy, but AMD is more than just a niche guy.

    --
    Even those who arrange and design shrubberies are under considerable economic stress at this period in history.
    1. Re:niche? by Anonymous Coward · · Score: 0

      most of AMD's chip are based on the intel architecture. I think the poster meant the "intel architecture" when he said "intel"

    2. Re:niche? by Anonymous Coward · · Score: 0

      You aren't much of a computer geek either, AMD chips are Intel X86 clones. (for the 20th time this story - why don't you people learn to read?)

    3. Re:niche? by gl4ss · · Score: 1

      * You aren't much of a computer geek either, AMD chips are Intel X86 clones. (for the 20th time this story - why don't you people learn to read?)*

      and for the 100th time, amd is a player of it's own.. and the article specifially said Intel in a manner of meaning the COMPANY, not the architechture anyways.

      --
      world was created 5 seconds before this post as it is.
  23. Wikipedia by sometwo · · Score: 4, Informative

    Here's the article about the alpha: http://en.wikipedia.org/wiki/DEC_Alpha

  24. Alpha Envy by Neon+Spiral+Injector · · Score: 4, Funny

    I was talking with CmdrTaco and Keith Packard along wtih a few of the other XFree86 people. They were all going on about heating the bedrooms with Alphas in the winter. And telling other Alpha related stories. Then Keith looks at me and asked if I have an Alpha. I never felt so inadequate as a geek. So a couple months later I did pick up a dual 21164 (EV56) based machine. Sure enough it did keep my bedroom warm, that is when it wasn't tripping the circut breaker. So I moved it to the server room at work, where it sits now still hosting my websites.

    1. Re:Alpha Envy by akuma(x86) · · Score: 1

      It's funny how Alpha gets such praise for taking a high-power high-heat high-frequency approach (low-IPC) to processor design. Compare the Alphas of their day to the HP PA-RISC offerings which were lower frequency but higher IPC. It reminds me of the Intel vs. AMD battles. There was a famous Microprocessor Report that pitted the speed-demons (Alphas) against the Brainiacs (PA-RISC).

      When Intel tries the same Alpha design style, they get buried in the press. I guess it's natural to fight the leader and go for the underdogs - but Alpha was the top dog and never did receive the criticism that Intel does.

  25. The real question is... by saintp · · Score: 1

    Does Netcraft confirm it?

  26. ARM? by nullset · · Score: 5, Informative

    I'd hardly call Intel the biggest CPU architecture out there.... maybe for PCs.

    ARM comes to mind. what about the embedded market? Atmel's AVRs, Microchip PICs, Motorola HC08's,HC11's, there's billions of non-intel architecture CPUs shipped every year. To those guys, intel is just a niche player....

    [flame suit off]

    1. Re:ARM? by sarahemm · · Score: 1

      Last I heard, Motorola was still shipping more microprocessors than any other company. VCRs, microwaves, TVs, stereos... This was a few years back, however. I'd still bet that Intel is behind one of the embedded chip companies. How many appliances does your average household have compared to PCs?

    2. Re:ARM? by Westech · · Score: 2, Funny

      How many appliances does your average household have compared to PCs?

      That depends on whether you mean average household or average slashdot reader household.

    3. Re:ARM? by Cheeko · · Score: 1

      Funny you should mention ARM. If memory serves DEC sold off the StrongARM technology to Intel, and Intel is now a major player in the handheld market as a result.

      Side note, DEC/Compaq also offloaded most of the Alpha design guys into Intels Itanium development group. Supposedly stuff that was supposed to go into the next gen (EV8) Alpha, will be showing up in Itanium in a year or two.

    4. Re:ARM? by Anonymous Coward · · Score: 0
      Arm (ARMPHY:Nasdaq) market cap $1.85B. Intel (INTC) $142.5B.

      Which would you say is bigger.

      Or, if I want a funny mod... which chip has a bigger heat-sync/power-output.

    5. Re:ARM? by sarahemm · · Score: 1

      Very true! Me and my partner were up to about 19 machines in the living room (computer room) at last count, if you include embedded gear like the security system controller (which is an x86 PC/104 based system). Not quite a typical household though (though we're probably computer-light for a double-slashdot household! ;) )

    6. Re:ARM? by Anonymous Coward · · Score: 0

      Intel is the world's largest manufacturer of ARM chips.

    7. Re:ARM? by Anonymous Coward · · Score: 0

      In 2003 Intel's revenues were 27 billion, more than DOUBLE the next highest semiconductor manufacturer Samsung. AMD was 12th with under 4 billion. No one else is even in the same league. Certainly no other microprocessor manufacturer.

      The search

    8. Re:ARM? by Anonymous Coward · · Score: 0

      How much money did ARM make last year?

      How much money did Intel make last year?

      In terms of dollar volume, ARM is a niche. Yes, I know that Intel licenses ARM.

    9. Re:ARM? by Pius+II. · · Score: 1

      I read that more ARM CPUs are shipped than any other sort. However, this is not a contradiction to the above post: ARM licenses it's core out to manufacturers. That would mean that they ship less cores than Motorola themselves.

  27. Ahh exposure... by dmayle · · Score: 1

    My first exposure to Linux was with an Alpha box. A friend of mine had bought a Multia to run as a server for his network. This was just at the time that MP3 was starting to show up (late '95), and he decided to run Linux on it, giving me the grand tour. Because of this, I toyed with Slackware a bit, but since I didn't have enough disk space at the time, I dropped it for a while. A couple of years later, I came into two Multia's by chance, and, remembering the old experience, bought them and installed Linux on them. I've since moved to a full time Linux user, both at home, and at work, and I have DEC/digital to thank for it.

    So long, Alpha, we'll miss you...

    1. Re:Ahh exposure... by Anonymous Coward · · Score: 0

      96-97 more like.

      they got the patent in '96 or so..

  28. ummmmmmm by Anubis350 · · Score: 2, Informative

    hmmmmmmmmmmm.....
    lessee, we have the powerPC by IBM, used both in their own machines and in apple hardware. We have the sparc machines by sun (which may or may not exist for much longer). We have AMD, which is becoming more and more mainstream, perhaps the biggest competitor intel has had in a long time. Oh and we forgot one other thing... how about all the chips that go into devices like phones and PDAs. You know, the motorola chips and such. For that matter, what about GPUs on graphics cards?
    seems like there are a long more processors out there than the article says, dont you think?

    --
    "goodbye and hello, as always" ~Prince Corwin, from Zelazny's Amber series
  29. Nifty Niche by Anonymous Coward · · Score: 0

    Finally, Transmeta's closest competitor is gone. Oh, wait... nuts...

  30. New life...kinda :) by hot_Karls_bad_cavern · · Score: 1

    Just had a prof that i know spend a good deal of money to have Gentoo put on his alphas. He simply is in love with them and just won't let them go. Admittedly, he's an older, British guy studying 12th century Chinese music (no, that is not a joke) and codes *everything* in lisp (the mere mention of anything other than emacs will launch a long, but very well defended argument). He even had his wife's computer done too (she's a heavy alpha user and prof too).

    i'm not sure what the point of this is, other than to say, there are still people who love and use alphas for some very important work (not that i'm waiting for 12th century chinese tunes to save the world, but you know what i'm saying). It's still sad to see something that was once great kinda wander off into non-production :(

  31. What's Changed? by CommieOverlord · · Score: 5, Insightful

    Before there was Intel x86 (comptabile) and a number of niche processors, and now there's still Intel and a number of niche processors. The submitter's closing statement seems a tad alarmist.

    We still have Itanium, two Sparc variants, a number of Power variants, Transmeta, Opteron, and whole bunch of other niche processors, most of which probably have more market share than alpha.

  32. Slashdot History by Lord+Kano · · Score: 4, Informative

    Slashdot ran for the first 7 or 8 months off an Alpha box.

    If memory serves, Slashdot ran on a Multia.

    LK

    --
    "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
    1. Re:Slashdot History by PotatoHead · · Score: 1

      Your memory was correct. Taco got 'em on a deal while building /.

      Those were fairly cool times to be around here then... My how far we have come.

    2. Re:Slashdot History by Lord+Kano · · Score: 2, Interesting

      By the UIDs, I can tell I registered here a little after you. My original name was "Lord Kano-The Gangster Of Love", but I had to shorten it when Rob lowered the maximum number of characters in the names.

      Damn I miss Sig11. Also, I couldn't be happier that Jon Katz is gone. Right after the Hellmouth series I put clicked the Ignore checkbox. I got sick of the daily buzzword soup with a thinly veiled attempt to pimp his new book. I didn't know he had finally gone away until about a year ago when someone mentioned it in another thread.

      Ahhh, the good old days. Before the GNAA, before 1.2.3 Profit jokes, when people were seriously imagining Beowulf clusters of E2K machines, Naked Petrified Natalie Portman, before Hot Grits in people's trousers, before goatse.cx links, when we had numeric karma, before the karma cap, when I was a rank n00b instead of the worldly /. veteran that I am today, when I actually got fucking mod points, and most importantly BEFORE JON FUCKING KATZ!

      LK

      --
      "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
  33. Personally, I'm not buying until ... by burgburgburg · · Score: 1

    they get to at least Epsilon.

  34. Bah! Back in the good old days... by Anonymous Coward · · Score: 2, Funny

    We didn't have any of this fancy-pants CPU-on-a-chip stuff. We built our computers by hand. 74xx TTL IC chips wirewrapped together. And by god we LIKED it.

  35. A tasty steak, that's the ticket by Anonymous Coward · · Score: 0

    I'll take a steak in my stomach any time over a steak in the heart. How would you get a steak in the heart of something, anyhow? It's too soft to penetrate (unlike, say, a STAKE).

  36. AMD CPU's are using licensed Alpha tech by Locutus · · Score: 4, Informative

    IIRC, AMD licensed the Alpha memory bus design and it's still used today. It's how AMD ended up with such a fast bus and beat Intel for ~2 years with a faster FSB.

    So, if you run and AMD CPU then you're keeping the DEC Alpha technology alive. Also, don't forget that the DEC StrongARM was part of the DEC technical vision too. It's how Intel got into the handheld market. Too bad DEC thought Microsoft was it's future....

    LoB

    --
    "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    1. Re:AMD CPU's are using licensed Alpha tech by beowulf2003 · · Score: 1

      IIRC, AMD licensed the Alpha memory bus design and it's still used today. It's how AMD ended up with such a fast bus and beat Intel for ~2 years with a faster FSB.
      No they do not. AMD used the EV6 bus in the K6-K7 processors. But the current AMD chips uses Hypertransport which was developed primarily by AMD and an on-chip memory controller. In fact, there used to be an independent group that included AMD, Samsung (and Compaq) that was promoting the EV6 bus and the Alpha ISA, but they switched to promoting the hypertransport after Compaq killed the project.

    2. Re:AMD CPU's are using licensed Alpha tech by lophophore · · Score: 1

      Yeah, and if you are using Itanium, you are keeping Alpha technology alive. Intel and DEC had a huge suit over Intel stealing DEC IP that was used in Itanium. The suit was settled by Bob Palmer foolishly selling the DEC semiconductor business to Intel.

      What a waste.

      --
      there are 3 kinds of people:
      * those who can count
      * those who can't
    3. Re:AMD CPU's are using licensed Alpha tech by Dr+Caleb · · Score: 1
      The first Athlons (Slot A) were also pin compatible with the Alphas.

      --
      "History doesn't repeat itself, but it does rhyme." Mark Twain
    4. Re:AMD CPU's are using licensed Alpha tech by TheMatt · · Score: 1

      I don't know if this is true or not, but I might believe it. My Alpha has some horrific number like 8 or 16 memory slots and it is hella fast. Combined with the very good DEC/Compaq/HP Tru64 compilers and CXML, I love my Alpha. I'm sad to see it go. I'm happy though, knowing Itanium will eventually be EV8 (I mean, come on, you keep using Alpha ideas) and MKL is getting to be CXML.

      --

      Fortran programmer...oh yeah. Array math for life!

    5. Re:AMD CPU's are using licensed Alpha tech by Anonymous Coward · · Score: 0

      Hypertransport ... was developed primarily by AMD and an on-chip memory controller

      Wow, that's quite some memory controller.

    6. Re:AMD CPU's are using licensed Alpha tech by Anonymous Coward · · Score: 0

      rotfl

    7. Re:AMD CPU's are using licensed Alpha tech by red+floyd · · Score: 1

      I thought Itanium was based on PA-RISC and VLIW tech?

      There may have been a few patents infringed, but the Itanic was not based on Alpha.

      --
      The only reason we have the rights we have is that people just like us died to gain those rights. -- Cheerio Boy
    8. Re:AMD CPU's are using licensed Alpha tech by red+floyd · · Score: 3, Interesting

      AMD used the EV6 bus in the K6-K7 processors.

      The K6 used the Pentium bus. It was a drop-in replacement. Aanyone remember the Shuttle HOT-569 with the i430TX chipset? Mine has a K6-2 sitting in its little Socket 7.

      The K7 aka Athlon did use the EV6 bus. I never understood why nobody made an Athlon=>Alpha shim board to run to run an K7 in an Alpha EV6 box or vice versa.

      --
      The only reason we have the rights we have is that people just like us died to gain those rights. -- Cheerio Boy
    9. Re:AMD CPU's are using licensed Alpha tech by Paul+Jakma · · Score: 1

      I never understood why nobody made an Athlon=>Alpha shim board to run to run an K7 in an Alpha EV6 box or vice versa.

      I doubt it'd have been pin-compatible.

      However the defunct API Networks, the company into which HP and Samsung divested marketing of Alpha, did make an Alpha/AMD box, the UP100 and UP1100 (best link I could find), which was a Alpha EV67 with an AMD AMD-751 "Irongate" "northbridge" as memory/pci/agp/ev6 controller, as used on early K7 boards. The UP1x00 wasnt too popular though, it's memory performance sucked compared to the EV67 boxes which used the DEC 21272 "Tsunami" northbridge, like the DEC DP264 and API Networks UP2000.

      So yes, the "Athlon" Alpha did exist..

      --
      I use Friend/Foe + mod-point modifiers as a karma/reputation system.
    10. Re:AMD CPU's are using licensed Alpha tech by akuma(x86) · · Score: 1

      And most of the Alpha design team is largely intact and now working for Intel. All of the superstar processor designers now work for Intel or AMD.

      They will pull away from IBM, Sun and the rest.

      Like ir or not, we're converging to a one ISA world -- x86 everywhere in 10 years.

  37. Reminds me of CISC vs. RISC debate by kbahey · · Score: 2, Insightful

    In the early 90s, there was this hot debate about RISC vs. CISC, and the merits of each, ...etc.

    This has all died out now, with CISC (read: Intel) coming out as a winner.

    Regarding the number of chips out there, AMD is not really different from Intel, at least it is instruction set compatible. Maybe this will change a bit in the 64-bit versions, but not right now. PowerPC is a good architecture, but not so wide spread. Outside of some IBM servers, and the 3% that is Apple's share, they are not used much.

    1. Re:Reminds me of CISC vs. RISC debate by mihalis · · Score: 3, Informative

      In the early 90s, there was this hot debate about RISC vs. CISC, and the merits of each, ...etc.

      This has all died out now, with CISC (read: Intel) coming out as a winner.

      Well, maybe. Intel is a big winner, but every single Pentium or Athlon is remarkably RISC inside. In fact these chips are so much more complex than any of the "pure" RISC or CISC chips the statement that CISC won is practically meaningless.

      Which side does Out Of Order Execution come from? Intel did it fast first.

      Who use OOOE now? Everyone.

      Theres a huge laundry list of features in modern high-performance CPUs that do not fit into RISC vs. CISC. Trace cache, micro-ops, CMT, CMP, etc etc

    2. Re:Reminds me of CISC vs. RISC debate by Kourino · · Score: 3, Insightful

      Pff, it's not that clear cut, as most people know.

      Much of the lower level workings of "IA-32" chips are a lot more RISCy than they started out being. More complex instructions are implemented in microcode. On the flip side, architectures like PowerPC (and even SPARC ... register windows are neat, but not very RISC) aren't very RISCy at all compared with stuff like MIPS.

      Neither side won absolutely. This is probably as it should be.

    3. Re:Reminds me of CISC vs. RISC debate by tkanerva · · Score: 1

      > In the early 90s, there was this hot debate about RISC vs. CISC, and the merits of each, ...etc.
      > This has all died out now, with CISC (read: Intel) coming out as a winner.

      However, let me point out that probably the sole reason why CISC came out as a winner (we can argument this as well...) is that simply the economics of scale pushed intel's architecture forward as other companies struggled to stay profitable (look at SGI, they used to make their own chips...)

      of course, AMD prevailed, because it supplied to the same pool (the windows world).

      --
      still running a x86? dinosaurs do exist!
    4. Re:Reminds me of CISC vs. RISC debate by ArbitraryConstant · · Score: 2, Informative

      "they are not used much"

      The numbers of PowerPC embedded processors shipped every year dwarf the combined total numbers of desktop, workstation, and server CPUs shipped every year from every architechture.

      --
      I rarely criticize things I don't care about.
    5. Re:Reminds me of CISC vs. RISC debate by cmowire · · Score: 1

      Hrmm...

      I tend to view it as the window of optimal instruction set usage closed. In that, right now, *any* reasonable instruction set, and quite a few non-reasonable ones, are "good enough" that it mostly is a matter of the performance of everything else. Because, compared to everything else, the hardware translation that is on both the AMDs and Intels (you know, the part that takes an ugly CISC instruction set and turns it into something that the RISC core can deal with) is a pretty small "bag on the side" compared to all of the other stuff on the chip.

      And, really, the only thing holding back the x86 architecture otherwise is the lack of registers, which has been fixed in the AMD 64 bit extensions.

      You also forgot about the ARM architecture, which shows up in a *lot* of personal computing devices -- pretty much all of the PDAs and cellphones have an ARM in them now.

    6. Re:Reminds me of CISC vs. RISC debate by sql*kitten · · Score: 1

      This has all died out now, with CISC (read: Intel) coming out as a winner.

      The end of CISC vs RISC was that they converged. A modern x86 is a hardware instruction decoder surrounding a RISC-ish core. The RISC processors like SPARC and MIPS added more complex instructions, again around a RISC core. The debate died out because BOTH sides won.

    7. Re:Reminds me of CISC vs. RISC debate by tepples · · Score: 1

      Because, compared to everything else, the hardware translation that is on both the AMDs and Intels (you know, the part that takes an ugly CISC instruction set and turns it into something that the RISC core can deal with) is a pretty small "bag on the side" compared to all of the other stuff on the chip.

      That's not what I remember. I seem to remember one of the Athlon processors devoting about half of its silicon to the x86 bytecode translator.

    8. Re:Reminds me of CISC vs. RISC debate by Smallpond · · Score: 1

      PowerPC has around 185 instructions, many of which have modifiers to make multiple forms. Makes you wonder about that "R" in RISC. Some personal favorites from the vast selection are:

      frsqrte - Floating Reciprocal Square Root Estimate
      eieio - Enforce In-Order Execution of I/O
      lfsux - Load Floating-Point Single with Update Indexed (pronounced: Life Sucks)

    9. Re:Reminds me of CISC vs. RISC debate by stratjakt · · Score: 0, Offtopic

      The debate died because there never was a debate.

      It was just zealots out crusading for their favorite buzzword or brand. Like most such "technical" debates (ATi vs nVidia, intel vs AMD, Apple vs Whoever) it was carried out by people with no real understanding of the technology.

      The "debate" typically sounded like this:

      "RISC rocks man! I don't know why anyone wouldnt use it!"

      "NAW man, you're crazy! CISC is teh SHIT! OH MAN I got this CISC chip and it can play MP3s! RISC can only do some things but not everything thats what the R means"

      "Yer such a fuckin fag! CISC is gay! Only gays use CISC!!"

      "Fuck you, yer the fag cuz only fags have RISC chips"

      "Oh ya how come the DEC machine at school is so awesome and I can play quake on it? Can you play it on your 386? Cuz RISC ROCKS!"

      "Fuck you quake is gay only fags play quake" .. ...

      You get the idea. Hop over to nvnews or rage3d and watch the fanboy debates rage over who has the greatest technology, nvidia or ati. It's funny, because none of the posters have any clues to the internals of either chip. How would they, it's all locked up as trade secrets. But, undaunted, they make brilliant comments like "ATI cards cant render shadows because they lack quadalphabileniar mapping support!"

      --
      I don't need no instructions to know how to rock!!!!
    10. Re:Reminds me of CISC vs. RISC debate by javiercero · · Score: 2, Informative

      Sorry Out of Order execution has been done for ages before Intel implemented it. As usual different name, same concept. But the same ideas behind RISC, superscalar, out-of-order, pipelined, etc.. have been around (and implemented) since the 60's.

      Not even in micros, as I believe Metaflow and other vendors had out-of-order CPUS out there way before Intel released the P6 microarchitecture.

    11. Re:Reminds me of CISC vs. RISC debate by javiercero · · Score: 1

      The R in RISC is for complexity not number.. in the opposite as the C in CISC. Has nothing to do with how many Opcodes are present in your ISA.

      RISC just implies that each instruction is easy to decode and can be geared towards achieving an effective single clock execution rate. Whether you have 1 or 2000 instructions in the ISA is irrelevant as long as those instructions are pretty simple.

      This whole CISC being RISCy is not that innovative though, all that Intel and AMD have done is pipeline their microcode. In fact RISC can be viewed as the microcode for the CISC machines of yore, which is in fact how it came to be.

    12. Re:Reminds me of CISC vs. RISC debate by cant_get_a_good_nick · · Score: 1

      This has all died out now, with CISC (read: Intel) coming out as a winner.

      1) There are no IA32 CISC chips since the 486. IA32 CISC is just what your apps see, it's all RISC inside.
      2) The cost of a CISC ABI (is that the term?) is lots of chip space needed for decode logic and deep deep pipelines. Power is a simpler chip, so much so that they'll be on their second generation of multi-core chips before intel has their first. It also consumes a lot of power.

      Don't confuse market share with quality. There are many ways to say which is "better", some have Intel winning, same have "pure RISC" whatver that means winning. Intel is where it is becasue it always targetted the low end space and got economies of scale that RISC vendors can only dream about. With IBM fabbing PowerPC processors for the XBox2 and the new gamecube, it will be intereting to see who wins the next round.

    13. Re:Reminds me of CISC vs. RISC debate by dutky · · Score: 4, Informative
      kbahey wrote:

      In the early 90s, there was this hot debate about RISC vs. CISC, and the merits of each, ...etc.

      This has all died out now, with CISC (read: Intel) coming out as a winner.

      That's an odd take on history, unless by 'win' you actually mean: "all but one CISC architecture (Intel x86) eventually capitulated and either exited the field altogether (either adopting a new RISC architecture) or shifted to a niche (usually embedded) market."

      A little history lesson for all you folks who either didn't exist or weren't paying attention in early days of the microcomputer revolution: Back in the late-seventies/early-eighties there were a fair number of competing architectures in both the mini- and microcomputer markets.

      In the mini-computer world there were:

      • DEC PDP-11 and VAX
      • IBM S/360 and S/370
      • Data General Nova and Eclipse
      • Burroughs B5000
      • Hewlett Packard HP3000
      • and many others

      all of which were CISC designs (relatively few registers, memory-to-memory arithmetic operations, lots of addressing modes, etc.).

      In the microcomputer world there were:

      • Motolorola's 6800 (8/16-bit) and 68000 (16/32-bit)
      • National Semiconductor's 32000
      • Texas Instruments TI9900
      • Zilog's Z80 (and 16 and 32-bit successors Z8000 and Z80,000)
      • Rockwell's 6502 and 65816
      • and, of course, Intel's 8080 and 8086

      all of which were, like the mini-computers of the day on which they were modeled, also CISC variants.

      Ever since the mid-seventies, various research groups (at universities and major corporations) had been toying with ways to make architecturally faster computers. (that is, computers whose arrangement of registers and instruction set were inherently fast, rather than just rely on faster transistors and shorter busses for speed increases) A number of these efforts stumbled upon the same set of concepts:

      1. eliminate all features that are not easily used by contemporary compilers
      2. eliminate most addressing modes
      3. eliminate memory operands for arithmetic and logical operations
      4. eliminate variable length and variable format instruction encoding
      5. eliminate micro-proramming of instructions (hardwire everything),and
      6. break all instructions into parts that can be overalpped (pipelining)

      This was dubbed Reduced Instruction Set Computing, or RISC, as a contrast to the contemporary architectural practices, which the RISC camp lumped together under the term Complex Instruction Set Computing, or CISC.

      The RISC approach payed off pretty quickly with processors that could easily execute one instruction every clock cycle (CISC architectures tended to take many clock cycles per instruction) and a few commercial products appeared in the mid-eighties from MIPS, Clipper, AMD and IBM. The main complaints against the RISC approach came down to one of

      1. fixed-width instructions waste too much memory
      2. RISC instruction sequences are too difficult for assembly language programmers to understand, or
      3. we can make better compilers that will be able to use CISC features to better advantage than do existing compilers (all we need is a measly little research grant and five more years).

      In the end, however, all three arguments proved false (memory capacities followed Moore's law into the stratosphere, most everyone moved to HLL compilers, and the genius level optimizing compilers either didn't materialize or benefitted the RISCs just as much as they did the CISCs).

      One by one, all the big players either came around to the RISC way to seeing things:

      • Motorola and DEC dropped their existing CISC platforms and developed RISCs (M88k and
    14. Re:Reminds me of CISC vs. RISC debate by burns210 · · Score: 1

      "This has all died out now, with CISC (read: Intel) coming out as a winner." Except that the core of modern Intel chips are RISC based, with an abstraction layer to morph them into a CISC frontend to preserve backwards compatability. RISC is superior, that is not questioned, even the biggest CISC processor developers(Intel) recognize RISC's superiority.

    15. Re:Reminds me of CISC vs. RISC debate by mihalis · · Score: 1

      Yeah, but intel were the first to do it -fast- ... as I said.

    16. Re:Reminds me of CISC vs. RISC debate by Anonymous Coward · · Score: 0

      He said Intel did it first fast. And he is correct.

    17. Re:Reminds me of CISC vs. RISC debate by Animats · · Score: 2, Informative
      A key point here is that the original intent of the RISC designers was to design simple CPUs that would execute one instruction per clock. That was achieved. Early Alpha and MIPS machines represent that approach in its purest form.

      Then came the Intel Pentium Pro. It took 3000 people to design. It was far more complicated than any previous microprocessor, or, for that matter, most mainframe CPUs. And it executed more than one instruction per clock, while dealing with all the horrors of the x86 instruction set. Many people had thought that impossible. Intel did it. Actually, several acres of engineers in tiny cubicles in Santa Clara did it. It was an amazing achievement that something designed by 3000 people actually worked well.

      The Pentium Pro was expensive to make, because it was a multi-chip module. But as soon as it became possible to fit the cache and Pentium Pro CPU on one chip, Intel came out with that as the Pentium II, and later, the Pentium III. Those took over the industry, relegating the RISC parts to niche markets.

    18. Re:Reminds me of CISC vs. RISC debate by javiercero · · Score: 2, Insightful

      Not really, the P6 OO was pretty limited, Alphas, POWER3s, and the R10K were much much much more aggressive on the out of order execution.

      Oh, and supers had pretty aggresive modified OO and Tomasulo's like units way before the P6, and they did it FAST too.

      So what was your point?

    19. Re:Reminds me of CISC vs. RISC debate by dutky · · Score: 2, Insightful
      Actually, the key point was that before the RISC/CISC wars there were lots of different non-RISC architectures, after the RISC/CISC wars only one non-RISC architecture survivies in any sort of non-niche application. Every major architecture on the market today, and for the past fifteen years, has is a RISC architecture, either outright or by subtrefuge (as with post-PPro x86). The survival of x86 is not proof of RISC's defeat, it is the last holdout of the defeated CISC design philosophy, and that only in name.

      To bring this back on topic (if only slightly), it's a damn shame about Alpha, but not so much, really. All of the RISC architectures looked pretty similar (unlike the CISC ecology before them). If the surviving RISCs are not quite as elegant as Alpha, at least they illustrate the same basic simplicity and orthogonality. The survival of x86 proves that you don't need a perfect architectural design to achieve high performance (at least not on integer code, and not if you have more money than God), so POWER/PowerPC, MIPS, Sparc and ARM should have few difficulties in the years ahead, despite minor architectural flaws. (actually, I'm not too sure about Sparc's continued survival, but I wouldn't shed a tear at it's demise: register windows are an abomination) IBM has already had to employ PPro-like tricks in the recent POWER5/PPC9xx designs in order to get high performance.

    20. Re:Reminds me of CISC vs. RISC debate by mihalis · · Score: 1

      Alpha was never OOE until 21264 which wasn't available until quite a while after Pentium Pro was out in the field with OOE. PPro took 21164 to the cleaners because it was a classic "speed demon" and running into the memory wall. At PPro launch it had highest SPECInt period. Then after a minor mistake was found with the benchmarks, that declined to it being merely about par with anythying else. 21264 was Alphas big fight back with OOE added to its other strengths (tight logical design and aggressive circuit design).

      I don't care about supercomputers for this debate. This thread has been about microprocessors.

      I really can't comment on POWER3 and R10K, maybe you're right there.

      What I do know is that one of the Alpha designers is on record as saying that Intel taught him that a chip could be OOE and still be -fast-. If he didn't know it until Pentium Pro, then I suggest your comments are plain wrong on some of your details. I can dig the reference up if you like

    21. Re:Reminds me of CISC vs. RISC debate by ChrisMaple · · Score: 1
      M88k was a loser for Motorola, despite pushing it hard. It has been abandoned. M68k lives on (kinda) as Coldfire.

      I didn't know that Data General went to M88k. It apparently didn't help, DG eventually became a storage company, lost market share and profitability, and got bought out.

      --
      Contribute to civilization: ari.aynrand.org/donate
    22. Re:Reminds me of CISC vs. RISC debate by dutky · · Score: 1
      ChrisMaple wrote:
      M88k was a loser for Motorola, despite pushing it hard. It has been abandoned. M68k lives on (kinda) as Coldfire.

      M88k was actaully a technical win for Motorola, they were able to produce a complete new architecure in record time partly becuase RISC design was simple enough to design and verify in only a few months (rather than a few years, as had been the case for the M68020 and M68030). The failure of the M88k in the market may have other causes (the 88100 and 88200 had very high pin counts which drove up the cost of building a circuit board for them) than pure architectural matters. Further, parts of the M88k architecture were used in the initial PowerPC devices, so you could claim that some of the M88k (though, I think, not very much) lives on in the PowerPC.
    23. Re:Reminds me of CISC vs. RISC debate by cmowire · · Score: 1

      Yeah. Same with the Pentium II. Then they moved the cache onto the processor and everything else got much much bigger. ;)

  38. Better colors? Running a filtering proxy? by plover · · Score: 0, Offtopic

    I'm running The Proxomitron, and I simply added a new filter that replaces "it . slashdot . org" with "slashdot.org" (munging required because the filter affects my preview!) So it took me a little while to figure out what your "better colors" meant, as I already had them.

    --
    John
  39. slashdot and the 2,004k bug by nazsco · · Score: 1


    every week, since 1990, we got an article just like that. alpha is dead. PERIOD.

    the only two alpha i had to administer in my life, one was slow as a DEAD COW and the other was stable as a DEAD COW (i think it was some trouble with the power unit, but the support from digital cost more then 12 brand new dell machines).

    1. Re:slashdot and the 2,004k bug by Kourino · · Score: 1

      Alpha's main wins over Intel architectures at the time were clock speed (DEC hit 500 MHz rather before Intel did, I believe) and floating point performance. Of course, a lot of architectures have better floating point performance than Intel's 32-bit stuff ... though this is less true with the advent of SSE.

    2. Re:slashdot and the 2,004k bug by javiercero · · Score: 1

      Intel's FP has been 64bit IEEE for ages btw...

    3. Re:slashdot and the 2,004k bug by Kourino · · Score: 1

      Err, I meant their 32-bit processors. (Their FP was actually 80-bit not-quite-IEEE for a long time, too, so there -_^ )

    4. Re:slashdot and the 2,004k bug by javiercero · · Score: 1

      Actually Intel is one of the few companies to implement the full IEEE FP standard, most other processors do not. The 80 bit is for internal datapaths for the multiplier and stuff, still you get 64bit doubles out.... :)

  40. Niche Guys? by LWATCDR · · Score: 2, Interesting

    Farewell, Alpha; the world's line of chips seems to have declined to Intel and a handful of niche guys."

    You mean small players like IBM? I guess the G5 and Power line of chips are not really big time enough to worry about?

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    1. Re:Niche Guys? by maw · · Score: 1
      If Beavis wrote an open source web browser based in the Mozilla would he call it FireFire?

      That would be cool.

      --
      You're a suburbanite.
    2. Re:Niche Guys? by burns210 · · Score: 1

      No kidding. IBM and the POWER line of chips, Motorola and the PowerPC(very similar to POWER), AMD with their x86 -32 and even cooler -64 bit processors. Sun and the SPARC processors...

      Sheesh, I think processor options still exist and I wouldn't call ANY of those companies 'niche guys' in any respect.

  41. and VIA by essreenim · · Score: 1

    have som epretty neat processors.
    I have no laptop, but my first one will be VIA based!

    1. Re:and VIA by bhtooefr · · Score: 1

      Their performance is WAY subpar. Intel has some even neater processors in the Pentium M CPUs.

  42. Alpha lives! by rabtech · · Score: 1

    Alpha lives on (at least in spirit) within AMD; They hired some of the engineers and licensed some of the technology, the EV6 bus being a prime example. Exactly how many and how much we don't know (for obvious business reasons.)

    --
    Natural != (nontoxic || beneficial)
    1. Re:Alpha lives! by Anonymous Coward · · Score: 0

      I'll belive it when a AMD chip spit's out a Seti@home WU as fast as an EV67 :P

    2. Re:Alpha lives! by Anonymous Coward · · Score: 0

      It really lives on in Intel, Compaq sold the IP and people to Intel several years ago.

    3. Re:Alpha lives! by mikefoley · · Score: 1

      And the EV6 bus stops at the Athlon 32-bit CPU's. After that, it's HyperTransport and built-in memory controllers.

      Not unlike Alpha EV8.

      --
      What's my Karma Mr. Burns? "Excellent"
  43. What's so bad about x86? by MoralHazard · · Score: 2, Insightful

    Taking potshots like this at x86 chips is such bullshit. So what if it's not as optimal an architecture as the Alpha, or if the EV7 bus is pretty neat? The biggest advantage of using x86 systems over anything else isn't that they're the fastest chips, cycle-for-cycle, or that they're a particularly elegant solution. It's that they're CHEAP and FAST ENOUGH.

    Think about how many Intel Xeons you could get, on 9xx chipset mobos, for $30,000. If you built them yourself, probably 15-20. Is one (or four) 1.5 GHz Alphas are more useful than a cluster of 20 Xeons? Hell no!

    See, ever since Intel lost their de facto monopoly on powerful x86 chips (thank you, AMD!), their prices have dropped far enough that it's hard to beat x86 solutions on a price vs. performance basis. Even if you have to stack up more boxes in a rack to do it. Hell, Quad-CPU Xeons can still go for less than $6,000, if you build them from parts, so rackspace isn't really an issue.

    1. Re:What's so bad about x86? by Anonymous Coward · · Score: 0

      But wouldn't it be cool if the competition and price-cutting was happening on a clean, elegant architecture instead of an outdated, cantankerous one?
      The world would be a better place for everyone.

    2. Re:What's so bad about x86? by turgid · · Score: 4, Informative
      The biggest advantage of using x86 systems over anything else isn't that they're the fastest chips, cycle-for-cycle, or that they're a particularly elegant solution. It's that they're CHEAP and FAST ENOUGH.

      Thanks to the ruthless intel vs. AMD competition of the last half decade, that is now the case, but it didn't used to be.

      Back in the early '90s when the 64-bit RISC architectures were coming out, x86 was a joke. Now, Opteron is more or less a DEC Alpha with an x86 translation unit slapped on top and hypertransport, which made its way down from Cray, via the Sun E10k to the desktop.

      If it hadn't been for these radical RISC architectures, and the intel vs. AMD fight, things would be very different.

      Don't even think about multi-processor Xeon systems. The primitive bus architecture and interprocessor communications simply does not scale well at all past 2 processors. You can just about get away with 4 processors, but after that, you might as well just put space heaters in the box.

    3. Re:What's so bad about x86? by stratjakt · · Score: 1

      No, whats the difference?

      Only a handful of geeks see the low-level shit anymore. Noone deals with registers. Everything is coded in a higher level language.

      So do I really care what the CPU in this box is, or how textbook perfect its architecture is? It's pretty much irrelevant.

      Like people who say "the G5 does more per clock tick than the Pentium 4". Good for it. But the clock ticks on my proc 3.06 billion times a second. Who cares so long as it "just works", isn't that the Apple motto? Sheesh.

      --
      I don't need no instructions to know how to rock!!!!
    4. Re:What's so bad about x86? by Anonymous Coward · · Score: 0

      "Think about how many Intel Xeons you could get, on 9xx chipset mobos, for $30,000. If you built them yourself, probably 15-20. Is one (or four) 1.5 GHz Alphas are more useful than a cluster of 20 Xeons? Hell no!"

      A computer is more than just the cpu. An Alpha based machine can beat 20 Xeon machines for a given application. It is the application that is important. And that is why the Alpha based systems are still a good buy.

    5. Re:What's so bad about x86? by turgid · · Score: 1
      So do I really care what the CPU in this box is, or how textbook perfect its architecture is? It's pretty much irrelevant.

      To the low-end consumer, yes, it is pretty irrlelevant. But to the rest of us, how we got to where we are today is relevant, and especially when we look to the future, and when consumer-grade isn't enough. That is why we need to be aware of our CPU history and need to be aware of the options available to us when a 4-way Dell or HP 32-bit Xeon just doesn't cut the mustard - and why.

    6. Re:What's so bad about x86? by i_r_sensitive · · Score: 1
      Come off it...

      First, you aren't going to put 15-20 Xeons in place of a single Alpha, if only because the majority of your x86 budget is going to be chewed up by redundant costs. Consider: I can stick that Alpha in a small server closet, with a smaller environmental control system, a smaller UPS/backup generator, and a smaller fire supression system. Best of all, only one system to worry about backups and administration for.

      Now, I simply am not going to be able to beat that with 15-20 Xeon boxes, even nice flat 1U rackmounts are going to have higher requirements in all those critical categories. Never mind system/cluster administration, SAN crap, etc. etc.

      The point is there are other criteria than simply cost and processing power. If I made all my decisions based on price vs performance without taking into consideration reliability, ease of administration, etc. etc. etc., well let's just say my employer wouldn't be worried about my /. time, since I wouldn't be employed here.

      Ultimately diversity is a good thing. In fact diversity is the underlying reason for the success of the x86 architecture. The thesis that there is no need for any other architecture, simply rack up the x86s, is irresponsible, short-sighted, and in fact flies in the face of reasonable analysis. Maybe taking pot shots at x86 chips is bullshit, but denying the value of other architectures, approaches and ideas is so much more bullshit.

      --
      "Talk minus action equals nothing" - Joey Shithead, D.O.A.
      "Talk minus action equals /." -
    7. Re:What's so bad about x86? by MoralHazard · · Score: 1

      "Don't even think about multi-processor Xeon systems. The primitive bus architecture and interprocessor communications simply does not scale well at all past 2 processors. You can just about get away with 4 processors, but after that, you might as well just put space heaters in the box."

      I would submit that there aren't too many applications that require more CPU cycles than 4x 3-Ghz Xeons can spin, even with less than perfect efficiency--let's say in the neighborhood of %60-%80, which fits with my own experiences on Quad-Xeon boxes going back about two years.

      If a workload is linear, multiple processors won't help you, at all, because a truly linear process (think of a cyclical function like an MD5 hash computation, with a really long input string) depends on the outputs of previous operations.

      If a workload isn't entirely linear, the degree to which it can be parallelized depends on how much different parts of the process are dependent on each other. If you're talking about running an SSH server for a couple of dozen clients, its perfectly parallelizable because each SSH connection is a separate process! If you're talking about database updates, only the reads and the non-conflicting writes are parallelizable--a lot (for most db apps), but not everything.

      Also, the degree to which multiprocessing can help your problem depends on how fast the CPUs can communicate with each other (main memory, really, but if we're talking about a cluster with multiple "main" memory spaces, it's really the CPU-to-CPU latency that's the issue). Some problems are incredibly latency-sensitive, but others are not--like the SSH server example. If your problem is NOT latency-sensitive, you could potentially use a networked cluster of boxes, each box with a limited number of CPUs.

      So the problems that need lots of CPUs in one box are the problems that are A) very parallellizable, and B) highly sensitive to latency between the CPUs. This is a pretty limited set of problems, though still substantial. I couldn't say exactly what portion of the worldwide computing workload falls into that category, but it ain't much.

      So for 99% of the world's problems, why do you need more than 4-way systems? You might a need a lot of them, and maybe more boxes than if you had an efficient 8-way (or bigger) solution, but being as the price-per-machine scales up faster than processing power when you get past the 2-way point, your more efficient solution will probably be more expensive, too.

    8. Re:What's so bad about x86? by turgid · · Score: 1
      I would submit that there aren't too many applications that require more CPU cycles than 4x 3-Ghz Xeons can spin, even with less than perfect efficiency--let's say in the neighborhood of %60-%80, which fits with my own experiences on Quad-Xeon boxes going back about two years.

      You go on to say:

      So for 99% of the world's problems, why do you need more than 4-way systems?

      You fall into the same old trap as everone before you, namely "one size fits all."

      I am old enough to remember wen 16-bit machines were giving way to 32-bit machines. I also remember when single-processor machines weren't going to be fast enough.

      Well, 64-bit machines have been available (at the workstation level) for a decade now, and I can assure you that large multiprocessor machines are still very much in demand.

      You see, the thing is, as hardware increases in power, peoples' demands of that hardware increases. There is always the demand for more power. That's what fuels competition and development.

      Your 4-way Xeon may be good enough for you and 98 of your buddies, but I still need by 16-way 64-bit RISC SMP server. Yes, cost goes up, but for an awful lot of people, that cost is justified. You low-end people ultimiately win too as these technologies trickle downwards eventually. You just may have to wait 5 or 10 years.

    9. Re:What's so bad about x86? by Anonymous Coward · · Score: 0

      I think they are trying to say, a 4-way (or more) Xeon doesn't replace a fast Alpha. They messed it up and ended up sounding like they don't think people need high-end hardware. Or I am confused.

    10. Re:What's so bad about x86? by burns210 · · Score: 1

      "The biggest advantage of using x86 systems over anything else isn't that they're the fastest chips, cycle-for-cycle, or that they're a particularly elegant solution. It's that they're CHEAP and FAST ENOUGH."

      Because in the highend, world-wide enterprise datacenters, they look for 1. Cheap and 2. Fast Enough. God Bless America.

    11. Re:What's so bad about x86? by MoralHazard · · Score: 1

      Okay--classic slashdot dumbass response, quoting the contradiction to his response IN THE RESPONSE. Follow the bouncing ball:

      I said (which he quoted): 'So for 99% of the world's problems, why do you need more than 4-way systems?'

      To which Bright Boy responds: 'You fall into the same old trap as everone before you, namely "one size fits all."'

      Um, dude, I specifically said that one size DOESN'T fit all. I said that (given that we're pulling statistics out of my ass), 99 out of 100 workloads, roughly, don't need efficient 4-way or 8-way or more-way CPU configurations in one box. WHICH WOULD CATEGORICALLY MEAN THAT WORKLOADS DO EXIST THAT NEED MASSIVELY PARALLEL ARCHITECTURES. It's just that there are very few such cases, overall.

      If you go back and look at the orignal point, that it's silly to go off bad-mouthing the cheaper, less powerful x86 stuff because it's less powerful in singular units, it still stands. For most cases, the fact that it's so commoditized and SO MUCH cheaper means that you can still solve big problems, even with lower efficiencies, because the price drop is bigger than the efficiency drop.

      So yeah, for your 1-in-10^n situation, YOU might need more CPUs in a box. You sure seem like you're proud of that fact, too.

  44. "Do we get thier marketing people?" by bADlOGIN · · Score: 2, Interesting

    This comment from an Engineering conference call from Dec West site to Colorado got the well deserved applause and laughter when the DEC/Compaq merger was announced. I was there when it happened, and this got to the main problem with DEC: couldn't market a whore in a free port. They sat on the Alpha design for years as it was before launch in part because they didn't want to eat into thier mini business the way they ate into mainframe business. History doesn't repeat itself, but it sure rhymes. Sorry, Alpha - guess you live on in IA-64 (the "IA" stands for "Inetl's Alpha").

    --
    *** Sigs are a stupid waste of bandwidth.
    1. Re:"Do we get thier marketing people?" by hughk · · Score: 1
      DEC were happiest selling to a lab (its where they came from), but they made a total CF of selling to major corporates. After a while, acquisition in the 'labs' was corporatised so they coudn't sell there either.

      The problem with the slow release of Alpha, was that Digital weren't ready with their software base (which was vast). If they had concentrated on selling Unix desktops to start off with, thjey could have nicely segmented the market. As it was, they spent too long getting Alpha COBOL to work (it does) and obscure stuff like FMS. A mass release of the Alpha workstation would have wiped the floor with the SPARCs for R&D and the front office of investment banking.

      People held off buying their VAXes whilst waiting for Alpha (we even had some 9000s).

      --
      See my journal, I write things there
  45. just call me the alpha disposal guy by glen604 · · Score: 1

    If anyone's got some of those end-of-line-no-one-wants-them-anymore alpha servers - particulary the really powerful ones- I'll gladly take them :)

    attn digital: I'll take what's leftover of your stock too- you can ship it direct to my address.

    best of all- I'll do it for free- call it a public service, if you will.

    1. Re:just call me the alpha disposal guy by Anonymous Coward · · Score: 0
      If anyone's got some of those end-of-line-no-one-wants-them-anymore alpha servers



      If you had provided a shipping address, I would've sent you one. But I'm pretty sure I'll never check this thread again, so it is too late now...

  46. The whole idea is crazy by armando_wall · · Score: 2, Insightful

    I don't get it.

    Oh, where is ObviousGuy when we need him?

  47. AMD is by Anonymous Coward · · Score: 0

    chopped liver?

  48. Microprocessor Report by glassware · · Score: 4, Insightful

    As a CPU buff, I ordered a back-issue of Microprocessor Report where they discussed the introduction of the Alpha in glowing terms. The radical chip architecture and speed-at-any-price mentality was new at the time, but quickly proved itself to be the superior chip design approach. For most of the 1990s, the Alpha was the fastest chip on the market in both integer and floating point operations.

    Alpha was a Risc chip's risc chip. The IBM Power architecture has dozens of operations and permutations; the Alpha has a handful. This contributed not only to the Alpha's speed, but also to its insatiable demands for memory. DEC introduced a code-translator that allowed the Alpha to run x86-32 binaries at native speeds, but warned that memory requirements would grow substantially. The software never became cost effective.

    But, towards the turn of the millennium, something strange happened: the Pentium Pro architecture (happily renamed PII and PIII) inched towards the lead in integer operations. The P4 actually surpassed the Alpha chips. Intel had, by then, hired away some of the Alpha designers and began to adopt its performance enhancing strategies. How could Intel catch up to the Alpha when Intel was burdened with an architecture as convoluted as x86?

    Strangely, the x86 architecture can also be a benefit to chip design. Because x86 compresses commonly used instructions into tiny, awkward byte codes, the P4 generation of chips requires less memory and fewer cache misses - and the convoluted opcodes can be decoded quickly by the processor prior to dispatch. In the long run, Alpha's simplified instruction set proved to be less useful than machine-code x86 compatibility; and x86 chips are now little more than Alpha chips sitting behind an x86 instruction decoder. The Alpha design lives on in every CPU you buy, whether it be AMD or Intel.

    For further reading, check out CPU performance numbers on http://www.spec.org and read the commentary on Microprocessor Report.

    1. Re:Microprocessor Report by glassware · · Score: 1

      This is a bullshit argument. If your code doesn't spend 99% of its time in loops, it doesn't deserve to run fast.

      Angry much?

      My presumptions are as follows:

      All else being equal, a smaller piece of code will typically generate fewer cache misses than a larger piece of code.

      For identical source code fragments, x86 byte code is typically smaller than Alpha byte code.

      If either of my two assumptions are wrong, I will be happy to learn from you.

    2. Re:Microprocessor Report by raxx7 · · Score: 1

      Alpha was dead at birth.
      DEC was late in their change from CISC to RISC.
      And when they did it, they first moved to MIPS and after MIPS they moved to Alpha.
      Alpha came out with into a market already taken by other RISC cpus, with lots of ressentment towards DEC and had litte (if any) advantage over other RISC CPUs (Alpha is a cleaner ISA than other RISCs, but it doesn't provide that much of an advantage).
      Thus, Alpha was allways a niche in the niche of high end RISC market, dominated by Sun, HP and IBM.
      It was in the late 90's that Alpha built it's reputation for speed.
      The RISC market was shrinking, being taken by Intel, and design costs were going up. Seeing that the situation would become economically unsustainable, most high end RISC's development was slowed down or just put in life support. MIPS and PA-RISC don't have a new core design in over 10 years.
      IBM invested in automated chip design to cut development costs.
      HP tried to figure out an ISA that would perform well on simpler chips. And then they joined to Intel and Itanium was born.
      SGI and Sun just slowed down.
      Alpha didn't. Maybe DEC didn't see the writing on the wall. Or maybe they tried to take advantage of others RISCs slow down.
      Whatever it was, they just kept on developing it. But, despite it's performance, Alpha never gained enough market to be sustainable.
      The merge with HP didn't help either. Alpha may get the headlines, but PA-RISC's customer base is much bigger.

      Strangely, the x86 architecture can also be a benefit to chip design. Because x86 compresses commonly used instructions into tiny, awkward byte codes, the P4 generation of chips requires less memory and fewer cache misses - and the convoluted opcodes can be decoded quickly by the processor prior to dispatch. In the long run, Alpha's simplified instruction set proved to be less useful than machine-code x86 compatibility; and x86 chips are now little more than Alpha chips sitting behind an x86 instruction decoder. The Alpha design lives on in every CPU you buy, whether it be AMD or Intel.
      Now that's crap.
      * Few applications have issues with I-Cache hit rates.
      * Decoding x86 is a major problem. See how many different solutions have been employed to do it since the PPro and K5.
      * x86 chips are designed to the core to run x86. The fact that it breaks x86 into smaller instructions doesn't make it an Alpha beind a x86 decoder. It's like saying PPC970 is an Alpha behind a PowerPC decoder.
      * Why should Alpha claim the influence of RISCs in the design of x86 CPUs? It was neither the first RISC neither the first OoO CPU.

    3. Re:Microprocessor Report by cant_get_a_good_nick · · Score: 1

      Strangely, the x86 architecture can also be a benefit to chip design. Because x86 compresses commonly used instructions into tiny, awkward byte codes, the P4 generation of chips requires less memory and fewer cache misses - and the convoluted opcodes can be decoded quickly by the processor prior to dispatch.

      I doubt if most people agree with that. Pentium and later architectures (like the Cyrix 5x86, Athlon, etc) decode CISC instructions to RISC core. I believe the 5x86 would even let you run these microOps natively, but never really did anything with it, since no one would want to target such a microscopic segment of the market anyway. x86 baggage is not only decoding complicated instructions, with numerous special cases, makes for a lot of extra decode logic. Additionally, with the MHz at any cost mentality at Intel, makes for super long pipelines that cost you dearly on any branch prediction failure. It also makes the chips run damn hot, so much so that Google found their power/performance/electricity cost sweet spot with old PIIIs not P4s.

      Yes, you can get good performance from a bad external Architecture (IA32) but at costs of large amounts of silicon, electricity,. and brainpower. Pentium works decently well (decent depending on your definition) in spite of IA32, definitely not because.

    4. Re:Microprocessor Report by Anonymous Coward · · Score: 0

      Intel had, by then, hired away some of the Alpha designers and began to adopt its performance enhancing strategies.
      Yes!
      Google "alpha director site:intel.com" and you get 6 different web pages for guys who were working on Alpha design, but are now with Intel.
      http://www.intel.com/pressroom/kits/bios/plowney.h tm
      http://www.intel.com/pressroom/kits/bios/rgrove.ht m
      http://www.intel.com/pressroom/kits/bios/jemer.htm
      http://www.intel.com/pressroom/kits/bios/pbannon.h tm
      http://www.intel.com/pressroom/kits/bios/wgrundman n.htm
      http://www.intel.com/pressroom/kits/bios/dbhandark ar.htm
      2 of these guys work specifically on Itanium stuff, the rest seem more generic.

    5. Re:Microprocessor Report by voodoo1man · · Score: 1
      After the RISC non-revolution, it seems that everyone's forgotten that microprogramming is a really old concept. For an insightful read, try to find Ashok and Rauscher's Foundations of Microprogramming (New York : Academic Press, 1976). I did a few months ago, and it's pretty eye opening. You can see where the RISC ideas came from: the book discusses everything up from instruction decode strategies, to the issues posed by caches and pipelines, and even touches on instruction level parallelism! This really puts modern processor engineering in perspective, better than Hennesy and Patterson or for that matter any modern chip textbooks do.

      It would be nice to see a breakdown of exactly how many transistors are spent where on Pentium IVs - I suspect (and have read as much) that most of the silicon space is used up in the parallel ALUs and the FPU, so the instruction decode logic is relatively small. What I'd really like to see though, is how Transmeta's processors handle the decoding and execution, and why their approach isn't microprogramming (everyone claims this but I've yet to hear an explanation).

      --

      In the great CONS chain of life, you can either be the CAR or be in the CDR.

    6. Re:Microprocessor Report by argent · · Score: 1

      How could Intel catch up to the Alpha when Intel was burdened with an architecture as convoluted as x86?

      Because Compaq bought Digital and put the brakes on Alpha development. Even before the formally announced its death they were clearly dragging their feet, the P4 beat a champ that had bean softened up by the boardroom.

      The x86 instruction set may require a slightly smaller cache to get the same hit rate, but the x86 complexity meant less room on the chip FOR that cache. The EV8, if it had come to pass, would have managed four processors on a smaller chip than the two-way x86 and would *still* have had more room for cache if it was built to the same fab standards. Oh, and a shorter pipeline so cache misses would be cheaper.

      If Intel had bought the Alpha as well as the ARM from DEC, instead of treating it as an opportunity to kill a competitor for the Itanium, AMD would be playing catch-up to "Intel Alphas" (or whatever they called them, like they called the followon to the "Intel StrongARM" the XScale) instead of Intel playing catch-up to the AMD Opteron.

    7. Re:Microprocessor Report by javiercero · · Score: 2, Interesting

      They were late? As in offering one of the first lines of RISC workstations on the market is being "late" jeez! (The DECStations came out in '88, which I believe places them almost earlier than the PA-RISC, or even SPARCStations).

      When it came out Alpha was faster than any other CPU period, and not just faster but significantly more powerful than anything else in the market. Obviously you must have a very selective memory if you don't remember the early 90's and everyone lusting after Alpha big time. And that was a clear advantage, however DEC could not market themselves even if they were a free whore in a port.

      " Decoding x86 is a major problem. See how many different solutions have been employed to do it since the PPro and K5.
      * x86 chips are designed to the core to run x86. The fact that it breaks x86 into smaller instructions doesn't make it an Alpha beind a x86 decoder. It's like saying PPC970 is an Alpha behind a PowerPC decoder."

      I have newsflash for you, x86 instructions have never been executed natively (most of them anyways), it is all microcode. This whole shebang of x86 "risc" core is from people who don't get it that all that the P6 is doing is using a leaner microcode that can be pipelined and superscaled.

      The influence of the Alpha in the x86 comes from the fact that Intel did indeed buy out the Alpha technology after they settled their lawsuit with DEC, and a shitload of the Alpha team ended up developing for intel. Thus a lot of the internal pipeline technology ended up in the PIV et al... it doesn't make it an alpha, but some of the design principles are there.

    8. Re:Microprocessor Report by Anonymous Coward · · Score: 0

      Consider a 1000-byte loop on x86 and a 3000-byte loop on a RISC, 200 cycles, GHz machine, #define HZ 1000: both get run for about 5000 rounds before something will come and interrupt things.

      How significant are code cache misses there?

      This was my point. High-performance code tends to spend most of its time in such loops. Unoptimized stuff on the other hand.. well, if you don't want it to run fast, who am I to stop?

    9. Re:Microprocessor Report by javiercero · · Score: 3, Informative

      Well the general idea for RISC according to Paterson came from having to program the microcode in the VAXen, so at some point they figured out that the translation overhead from the CISC instructions was unecesary. CISC came to be as a sort of "compresion" mechanism in which one instruciton could be fetched from memory and then it can be mapped into a sequence of micro-ops inside the CPU. Thus the intruction memory space and bandwidth requirements were substatial (afterall memory was a premium back then). People figured out that memory may get larger, so why not just fetch the microops themselves, so it was a trade off between memory footprint and decoding complexity.

      Of course early designs like the CDC 6600 were pretty RISC, although they didn't know it. And the CISC came out as a solution to the memory footprint problems that such architectures poised (in scaling down from supers to minis where cost was a priority).

      However it is really eye opening to know the actual translation overhead, control related with the translator in the x86 family is significant. And almost half of the dynamic transistor budget (not SRAM) goes into the translation/scheduling portion not the functional. So the overhead is much more significan than...

      And yes their approach is microprogramming, except that RISC-core is more buzzword compliant :).

    10. Re:Microprocessor Report by argent · · Score: 1

      My presumptions are as follows: ... All else being equal...

      Wrong assumption. You have so many square millimeters to spend on a chip. If you spend less on the processor you have more to spend on cache... and that can more than make up for the longer opcodes on the Alpha.

    11. Re:Microprocessor Report by TheLink · · Score: 2, Interesting

      "The x86 instruction set may require a slightly smaller cache to get the same hit rate, but the x86 complexity meant less room on the chip FOR that cache."

      Have you ever seen a modern CPU? The caches are take up the bulk of the chip's area. And then there are the level 3 caches etc.

      The additional complexity and space due to x86 support is overrated. Soon it'll just be like one of those vestigal limbs in whales or large snakes.

      An instruction set that requires 20% more cache space but 20+% less instruction decoder etc space could actually use a lot more silicon overall and be slower.

      The top 3 highest performing CPUs aren't RISC.

      Or are you gonna say IBM's POWER is RISC? Some of the POWER instructions decode to microcode - call that RISC? Sounds like CISC.

      Nowadays it's not a bad idea to have instructions that do lots and then decompress them to lots of micro-ops in the core of the CPU. POWER does that. AMD does that. Compare that with RISC's original concept of having everything in simplified ops/a reduced instruction set.

      When you didn't have enough silicon space to put the equiv of a "gzip" on the chip, RISC was faster. But once there was space for a "gzip" (and bandwidth became an issue), CISC-style designs started to gain an advantage.

      --
    12. Re:Microprocessor Report by argent · · Score: 1

      The additional complexity and space due to x86 support is overrated.

      That's why it needs a 60% faster clock to get the same performance as simpler architectures.

      Or are you gonna say IBM's POWER is RISC? Some of the POWER instructions decode to microcode

      You appear to be confusing implementation and design.

      Nowadays it's not a bad idea to have instructions that do lots and then decompress them

      Of course if you were designing a processor to do that you would start with easily decoded instructions and use an easily decoded compressed format that didn't force the compiler to generate instructions that have so little relationship with the final operation that half the generated code is pure busywork.

      I would call the result RISC.

    13. Re:Microprocessor Report by raxx7 · · Score: 1

      They were late? As in offering one of the first lines of RISC workstations on the market is being "late" jeez! (The DECStations came out in '88, which I believe places them almost earlier than the PA-RISC, or even SPARCStations).

      DECStations were introduced in 1989 and were MIPS based. Alpha wasn't introduced until 1992.
      Regarding to speed, please check the results of SPEC CPU95. Compare PA-RISC and Alpha. You might be surprised.
      And yes, I know x86, like other CISCs, was microcoded. I was just saying it IS a hard to decode it fast.
      Random nitpicks.
      * The 486 was already pipelined.
      * The Pentium was already superscalar.
      * What PPro really added was OoO.
      * Modern x86 decoders are quite different from the old ones. They have custom logic for simpler instructions. Only more complex ones go through the microcode engine. The catch is, the ones that go to the microcode engine are much slower.

    14. Re:Microprocessor Report by TheLink · · Score: 1

      ""Or are you gonna say IBM's POWER is RISC? Some of the POWER instructions decode to microcode""

      "You appear to be confusing implementation and design."

      As you implied, with RISC the code is very like what is executed in CPU. Whereas POWER actually has microcode AND it has 100+ opcodes of _variable_length_ AND it does "instruction cracking" (exactly what AMD's Athlon's do). If that's RISC, then an Athlon x86 is RISC too!

      "That's why it needs a 60% faster clock to get the same performance as simpler architectures."

      Which architectures are you comparing? Opteron vs ?? SPARC? MIPS? Alpha? PowerPC? or POWER?

      If you're using the P4 for comparison, well it needs a 60% faster clock to get the same performance as an AMD64 CPU.

      So far the classic style RISC chips are slower (fixed instruction length, simple instructions etc).

      --
    15. Re:Microprocessor Report by argent · · Score: 1

      You're still confusing implementation and design. There's no RISC Purity Council saying "you're not allowed to take advantage of new techniques that help you adapt to changes in technology that have occurred in the years since the instruction set was designed", except in the minds of Intel apologists.

      There's a huge difference between what needs to be done to implement a RISC instruction set and a mess like the x86.

      Let's look at an x86...

      Compiler: 'let's see, I'm running short on registers, so let's see, I'll copy this here value to memory so I can re-use that register there'

      CPU: "Register-memory move, oh good, I can do that in the background by queing up a completion op in 16 cycles"

      Compiler: "Now put this result here"

      CPU: "Hold on, that register's in use, let's stall the pipeline a cycle or two while we shuffle the invisible register file"

      And something with a sane instruction set:

      Compiler: 'What's next, oh, there's a free register, we'll use that.'

      Compiler: 'Now, put this result here.'

      CPU: "You got it, boss"

    16. Re:Microprocessor Report by TheLink · · Score: 1

      "You're still confusing implementation and design"

      Perhaps, but let's be more specific so that I can be less confused about what you're trying to say.

      You said: "it needs a 60% faster clock to get the same performance as simpler architectures"

      So which architectures are you comparing?

      Which are the top 3 fastest CPUs? Which are RISC in your opinion, and why do you consider them RISC?

      --
    17. Re:Microprocessor Report by Anonymous Coward · · Score: 0

      In that case the Athlon CPUs are RISC - anyone who thinks otherwise is just confusing implementation with design.

    18. Re:Microprocessor Report by argent · · Score: 1

      Right now about the only shipping hardware I'm aware of that I would not consider to be based on a RISC design (including Itanium, sorry Intel) are the x86 and the PDP-11. I don't know enough about the AS400 and the IBM mainframes to speculate on them.

      It's not really CISC, either, since it was designed as a kind of an emulation platform at the assembly language level for the 8080 family of processors rather than a "high level assembly" like the CISCs or a "vertical microcode" like the RISCs.

  49. End of the Line for HP too? by turgid · · Score: 2, Informative

    Their plan to move everyone to itanic appears to have backfired. Has itanic finally sunk?

  50. B-2 Memories, Management by Embedded+Geek · · Score: 4, Interesting
    I worked with about 400 other developers on the embedded software for the B-2 Bomber. As our groups grew, the VAX clusters we used began to suffer. We complained to management but there was never any money for better mainframes.

    Then we switched over to a trouble report tracking program instead of doing everything on paper. The thing was implemented in house and made to run on the VAX'es. Suddenly everything slowed to a crawl, both development and trouble tracking. Since managers were the primary users of the tracking software, we knew it would have visibility. There was much rejoicing when the company bought a DEC Alpha...

    ...and put only the tracking software on it. No development work was allowed at all on teh new machine.

    SIGH. The salad days of youth...

    --

    "Prepare for the worst - hope for the best."

  51. Deadness by essreenim · · Score: 1

    Yeah found the quote on main page hidden at bottom:
    SDF uses DEC (hp) Alphas running NetBSD, TOPS-20 and Symbolics GENERA
    Yes, shall we die together : )
    At least we will be less prone to receiving virii in the future. Who writes a virus for a dead OS??

  52. ebay by 5m477m4n · · Score: 1

    Does this mean they'll be uber-cheap on ebay? I for one would love to get my hands on an Alpha box.

    --

    ---
    Those who can, do
    Those who can't, teach
    Those who don't know how, supervise
  53. last use of the digital logo by koehn · · Score: 1

    Any bets on whether we'll ever see the Digital logo on the front page of /.?

  54. Noo! by AvoidTheNoid · · Score: 1, Funny

    Alpha...dead? Zordon must be pissed...

  55. first==last? by Janek+Kozicki · · Score: 1

    so... we got a new category here, "digital" and the first article in that category is about the end of The_Beg^W Alpha.

    --
    #
    #\ @ ? Colonize Mars
    #
  56. You fool! by boffy_b · · Score: 1

    That quote has been hidden for five years, and now you'v blown their cover! I hope you'r happy mister....

    --
    Windows is only $500 if your time is worthless.
    1. Re:You fool! by essreenim · · Score: 1

      Dont tell anyone. The security of your country depends on it!

  57. Re:Bah! Back in the good old days... by Aardpig · · Score: 1

    We didn't have any of this fancy-pants CPU-on-a-chip stuff. We built our computers by hand. 74xx TTL IC chips wirewrapped together. And by god we LIKED it.

    Wirewrap? Luxury. We used to round up a brace of kids from t'orphanage, and build our prototypes by telling 'em to lick their fingers and touch t'pins of the vacuum tubes. And back then, there weren't no fancy '1's -- our binary were all '0's!

    --
    Tubal-Cain smokes the white owl.
  58. PowerPC is niche? by raider_red · · Score: 1

    We're selling a whole lot of them.

    --
    It's good to use your head, but not as a battering ram.
    1. Re:PowerPC is niche? by MikeBabcock · · Score: 1

      "Whole lot" being millions?

      From an AMD press release ... "Computation Products Group (CPG) sales were $554 million in the second quarter of 2004. This is an increase of 36 percent from $406 million in the second quarter of 2003 and is a three percent decrease from $571 million in the first quarter of 2004. CPG generated operating income of $58 million in the second quarter, a decrease from $67 million in the first quarter of 2004."

      --
      - Michael T. Babcock (Yes, I blog)
    2. Re:PowerPC is niche? by raider_red · · Score: 1

      Actually, yes. About half of them are going into the embedded market, and the rest go into Apples.

      --
      It's good to use your head, but not as a battering ram.
  59. Alpha Boot by straybullets · · Score: 2, Funny

    On the alpha box i worked with, at boot time an image of a cowboy on a horse was displayed. That rocked.

    --
    With that aggravating beauty, Lulu Walls.
    1. Re:Alpha Boot by Kourino · · Score: 1

      Even better, the SGI Indys I have play a neat little song when you turn them on.

    2. Re:Alpha Boot by sharkey · · Score: 1

      "The Raider's March", right?

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
  60. Cost of the OS!! by thewalled · · Score: 1

    HP quoted close to 5K each for an OS upgrade for a few alphaservers left with my company.. looks like they really want the alpha / tru64 platform to die..

    1. Re:Cost of the OS!! by Kourino · · Score: 1

      Of course they do. They were Intel's partner in designing IA-64, after all, and they put a lot of research time and money into it.

  61. WOW talk about Shortsited. by eadint · · Score: 1

    Alpha-based servers will continue to be sold through 2006, and supported through 2011. Farewell, Alpha; the world's line of chips seems to have declined to Intel and a handful of niche guys. Im not sure about you but Proccesors it looks like there are alot more players in the game other than alpha, and power 4 beats the crap outa alpha, dont even get me started on the RS series.

  62. I love my alpha 1000 5/400, by Archfeld · · Score: 1

    it is running Deb 64 and still does circles around my intel boxes. Looking back I'd have to say the mis-management of the century results in the world running MS on x86, when we should be os/2 on aplha. OS/2 did windows better than windows did windows in the beginning and the Aplha arch is simply awesome. Oh well the technically correct solution usually loses to the cheap and dirty solution....

    --
    errr....umm...*whooosh* *whoosh* Is this thing on ?
  63. Nonsense, if you have an Alpha, move fast by alexhmit01 · · Score: 3, Informative

    If you have a system on the Alpha that is say, 3 years old, and you were expecting to upgrade in 2 years, then this forces a decision: go through a PAINFUL migration expense now, or make a capital investment to push it off.

    Remember, buying equipment is easily depreciated over 3 years for PCs, probably longer is reasonable for Big Iron (I don't mean for tax purposes, I mean for their financials). If it costs me $0.5m in capital costs spread out over 5 years to upgrade a LOT of Alpha machines, even if it only costs me $200k to migrate off the platform, I may prefer to buy the Alphas that will only hit earnings by $100k...

    It also depends, what is IT's budget for new hardware vs. budget for software migration expenses.

    Also, if you were planning to buy a new Alpha to replace your old one, this is a smart time to buy it, because you can avoid dealing with the software migration now. Let's say you need to upgrade within 12 months, would you rather rush a migration job, or buy the gear and deal with the migration in 3-4 years, when you have time to plan.

  64. Re:Bah! Back in the good old days... by Anonymous Coward · · Score: 0

    Well WE didn't have any of this artsy-fartsy integrated circuit stuff. WE had to solder individual transistors on to circuit boards. It was a hard life, but we LIKED it.

  65. MOD PARENT UP by Anonymous Coward · · Score: 0

    Valid point, if the person who modded that flamebait had ever priced Alpha, MIPS, SPARC or POWER machines against x86 they would realize it's bang on the money.

  66. great googley-moogley, the prices! by Tumbleweed · · Score: 1

    Okay, for a lot less than those prices, I'll take me a multiprocessor Opteron machine, thankyouverymuch.

  67. Still useful, though! by Just+Some+Guy · · Score: 1
    I have an inherited Cabriolet with a single EV4/275MHz CPU and 256MB of memory. It's not a screamer when compared to the various soulless Athlons and Pentiums around here, but FreeBSD and three NICs turned it into an outstanding router / firewall / traffic shaper / IPv6 gateway / intrusion detector.

    The biggest advantage is that the odds of the latest 1337 h4xx0r scripting their way into a BSD OS on a non-Intel architecture is roughly zero. I still keep current on the latest security patches, of course, but the relative obscurity is a nice extra layer of defense.

    Best of all, though, is seeing kernel messages like "Preloaded elf kernel "kernel" at 0xfffffc00006bc000.". All of those 'f's in front are a sure sign that we're not in IA32 anymore.

    --
    Dewey, what part of this looks like authorities should be involved?
  68. Re:Bah! Back in the good old days... by Anonymous Coward · · Score: 0

    Transistors? Count yerself lucky, young man! We never had anything like solid-state electronics. We had to use vacuum tubes. The damn things would break down all the time, you counted seconds per cycle instead of cycles per second, debugging involved flashlights, ladders and hard hats, but god damn it, we LIKED it.

  69. Death of Alpha Predicted, news at 11! by Greyfox · · Score: 2

    Every so often we see this story pop up in Slashdot. "Oh, that's sad," we think, reminiscing nostalgically about the VMS workstations of the 80's. We go on about our business and a year or so passes, then we get another story predicting the death of the Alpha. So to all you "Death of Alpha" submitters, I have one thing to say. "It's not dead. It's restin'."

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

    1. Re:Death of Alpha Predicted, news at 11! by stud9920 · · Score: 1

      It's "FILM at 11". Obviously the news is already there.

      Also, that was a fun line back in 1998.

  70. Alpha owner by Anonymous Coward · · Score: 0

    I have an UP2000+ with 2x833Mhz 21264 4MB cache each. Every single cpu beats my 2.4GHz intel box in a simple "openssl speed" test, now considering it's a dual, it'll probably kick every single intel chip for the years to come. Considering that these chips were manufactured in 2000, you now realize how the x86 chips are such a bad design.

  71. big handful by Anonymous Coward · · Score: 0

    Somehow I don't see IBM/Motorola, AMD and Sun as being members of a 'handful of niche guys' when it comes to chip manufacturing.

    But then again, what do I know.

  72. Re:Bah! Back in the good old days... by Anonymous Coward · · Score: 0

    Vacuum tubes? Well, in my day we had it tough. We used mechanical gears. And most of them didn't even fit right. Seconds per cycle? We were happy even just to get an answer without having to re-oil the damn thing. And you were lucky not to lose a limb while debugging. And you know what, we LIKED more than any kind of new-fangled VACUUM TUBES.

  73. And don't forget... by callipygian-showsyst · · Score: 2, Interesting
    Years before Apple "invented" it, Microsoft had 64-bit operating system on PCs on the Alpha platform.

    Maybe that's why some contries banned Apple's misleading advertising!

    1. Re:And don't forget... by Detritus · · Score: 2, Informative

      NT on the Alpha was a crippled operating system. It was a 32-bit operating system with 64-bit hacks to allow it to run on the Alpha.

      --
      Mea navis aericumbens anguillis abundat
    2. Re:And don't forget... by Anonymous Coward · · Score: 0
      I forgot! It wasn't designed from the ground up to be a 64-bit operating system like MacOS-X was! What a bunch of bullshit! Did you hear that line at last week's Apple Club meeting?

      Pull that iPod out of your ass and get a life!

    3. Re:And don't forget... by Anonymous Coward · · Score: 0

      Except for the hardware abstraction layer, NT is not at all tied to any particular platform. Rewrite the HAL, recompile, and in theory, you have a fully functional OS on any hardware platform. NT for Alpha was no more a "hack" than, say, Linux on PPC - it was a port.

      There was some software included with NT-based Alpha workstations that allowed you to run 32bit x86 windows apps through emulation, but the OS itself wasn't run in such a way.

    4. Re:And don't forget... by Anonymous Coward · · Score: 0

      Of course that's true. NT was designed that way from the ground up! It was a major effort, and Microsoft did it well. I can't think of any other company that managed to re-write a complicated operating system from the ground up and did as good a job. (Remember TALIGENT, PINK, MacOS 9)?

    5. Re:And don't forget... by argent · · Score: 1

      Long before Microsoft had NT on the Alpha, Digital had OSF/1... and it was a real 64-bit OS instead of Microsoft's hybrid 32-bit model. Oh, and OSF/1's Mach+BSD design is so close to the Mach+BSD core of Mac OS X that they're practically twins. And there were more native applications, including (since this was supposed to be a PC) games for OSF/1 than Alpha/NT.

      So if you want to call Microsoft's worthless Alpha NT a "64 bit operating system", then let's call the G5 "the first 64-bit personal computer you can actually get native applications for".

    6. Re:And don't forget... by Anonymous Coward · · Score: 0
      and it was a real 64-bit OS instead of Microsoft's hybrid 32-bit model.

      I'm very sorry you have AIDS-related Dementia. It's a serious problem and I hope they find a cure, soon.

      If you weren't sick, you'd know that there's nothing "hybrid" about Microsoft's Windows NT for 64-bit platforms. A good example of a "Hybrid" is Carbon and Cocoa.

    7. Re:And don't forget... by argent · · Score: 1

      If you weren't sick, you'd know that there's nothing "hybrid" about Microsoft's Windows NT for 64-bit platforms

      Tru64 is 64-bit across the board, 64-bit ints, 64-bit pointers. Alpha/NT used 32-bit ints, because it was still basically Win32 with a long-pointer mode.

      Microsoft has improved their 64-bit product since, but back then it wasn't so good.

      I never said that OS X was a 64-bit OS, so I don't know what you're beabling on about that for.

    8. Re:And don't forget... by RzUpAnmsCwrds · · Score: 1

      You mean like Mac OS X?

      You don't actually think that Mac OS X is a true 64-bit OS, do you?

    9. Re:And don't forget... by Detritus · · Score: 1
      It was still Win32 with a 4GB address space.

      You could have more than 4GB of RAM, but it wasn't usable as normal memory. See A Programmer's Perspective on New System DLL Features in Windows NT 5.0, Part I:

      ...From a purely techie point of view, my favorite addition to KERNEL32 is something that the vast majority of Windows NT users (myself included) won't be able to take advantage of. The feature is limited support for 64-bit memory addressing...
      --
      Mea navis aericumbens anguillis abundat
    10. Re:And don't forget... by e40 · · Score: 1

      My company ported a compiler to NT on the Alpha. It was 32-bit all the way, dude.

  74. Re:Bah! Back in the good old days... by Anonymous Coward · · Score: 0

    Gears? Well, in MY day, we had to use BEADS on a STICK. I would have LOVED to have oiled my sticks, I still have scars from all the splinters. And you know what? We LIKED it.

  75. Re:Bah! Back in the good old days... by Anonymous Coward · · Score: 0

    mechanical gears? oil?
    That would be luxury, my good man. We had to find twigs and straw that were in the general shape of computing bits and then we had to whip oxen to provide the needed lubrication to just multiply two numbers together.

  76. repeat? by SpootFinallyRegister · · Score: 1
    hey, what about AMD! AMD has their own architecture! AMD isnt intel!

    oh wait... you mean someone already posted this? you say 50 people already posted this? gee, i just im just contributing noise to the signal. at least im sure nobody else will make the same mistake.

  77. Re:Niche guys.... [Clarification] by drgonzo59 · · Score: 1

    I see your point. AMD is RISCy inside and Intel-ish (x86-ish) outside. It doesn't matter how the x86 is implemented in the core, the fact remains that an x86 instruction set is exposed and AMD processors are designed to be compatible with a patched, broken and outdated instruction set. That is what I meant by Intel Architecture, I should have made that more clear. Otherwise you could argue that even Intel processors are not "Intel Architecture" anymore since they too emulate x86 with microinstructions. Heck Intel is the one who wanted to run away from x86 with its Itanium line, that hasn't gone well so far. Alpha on the other side was a "beautiful" architecture, well thought, scalable, good design. Well, maybe that is just my oppinion.

  78. Just started our last lease VMS on Alpha's by abcxyz · · Score: 3, Insightful

    We're about 6 months into our 4 year lease of the OpenVMS cluster, 4 ES47's with 7Tb of storage. Built like a tank, runs forever, and is an excellent Oracle DB server. Problem is the OS isn't a commody operating system, and not much runs on it any more (that we need). Our vendors are dropping support for the platform as well, so the move is on to start a migration plan, probably to linux.

    Have run alpha's for a long time, and they are still screamers. Problem is, you'll scream, then have a heart attack at the HP prices. Our current environment mentioned about was around $1.5M.

  79. eieio by Kourino · · Score: 1

    From the #kernelnewbies fortune file:

    I would suggest re-naming "rmbdd()". I _assume_ that "dd" stands for "data
    dependent", but quite frankly, "rmbdd" looks like the standard IBM "we
    lost every vowel ever invented" kind of assembly lanaguage to me.

    I'm sure that having programmed PPC assembly language, you find it very
    natural (IBM motto: "We found five vowels hiding in a corner, and we used
    them _all_ for the 'eieio' instruction so that we wouldn't have to use
    them anywhere else").

    - Linus Torvalds on linux-kernel

  80. Its not dead untill noone uses it. by Anonymous Coward · · Score: 0

    At the lab I work at we have 3 alpha workstations and an alpha server. The server still runs d|i|g|i|t|a|l VMS, which was last updated some time ago. The alpha workstations are running BSD. Of course, this is coming from a lab that has a 6 cabinent VAX 11/750 running BSD. Which, by my definition means the VAX isn't dead, and its still useful for things like telemetry data recorded on 1970's balloon campaings. If anyone wants to know the lab's field its expiramental study of the global electic field. I'm working as a programer for data conversions, getting stuff off the VAX so we can retire it.

  81. Re:Bah! Back in the good old days... by Anonymous Coward · · Score: 0

    Beads on a stick? In my day, we had to SACRIFICE GOATS and study the entrails. And you know what, WE LIKED IT.

  82. Re:Niche guys.... [Clarification] by drinkypoo · · Score: 1

    The K6 is a craptacular 386 but an excellent processor. I always forget which is which between -mcpu and -march but if you optimize your 386 code for K6 you don't get great results, but if you optimize your code for the K6 itself you do get great results. These old machines are therefore a great argument for gentoo :)

    By definition intel processors are intel architecture, but the fact that the architecture is so varied is the very reason that we now refer to processors by their assorted code names, like banias, prescott, hammer, et cetera.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  83. Re:Bah! Back in the good old days... by Anonymous Coward · · Score: 0

    Ogg attempts reply,
    Lameness filter interferes.

    ME OOG NEVER USE NO STICK. ME BEAT THINGS ON HEAD WITH ROCK.

    --Oog the open source caveman

  84. it wasn't management that failed, it was marketing by lophophore · · Score: 4, Insightful

    Digital could not market for shit.

    And that was on a good day.

    Yes, there were certainly some engineering and management blunders (mostly management) but Marketing was completely inept.

    During the 70s the PDPs practically sold themselves, and during the 80s VAX literally sold itself; it was the hottest thing you could hope to get. So when the big Unix wave came, with its cheap-ass Sun hardware, and so-called software compatibility, the Marketing droids could not cope, and the former #2 computer manufacturer is now just a zit on HPs ass.

    Do I sound bitter? nooooooo.......

    --
    there are 3 kinds of people:
    * those who can count
    * those who can't
  85. Slight correction... by SlashdotTroll · · Score: 1, Informative

    Microsoft Windows NT 3.5 was ported to Alpha platform by programmers from Digital Equipment Corporation (hereinafter DEC) and it was not true 64bit processing. It didn't allow a long int, and that is the easiest example I can give you. It also didn't support as much RAM as it would have in 64bit mode. DEC's programmers also caused a small intellectual property dispute by actually using much of DEC's VMS code to compliment porting Microsoft Windows NT 3.5 unto Alpha, to much blessings and praise from Microsoft's high-end customers for its verry quick GUI performance complimentary to the excellent floating-point performance known of Alpha, and for this Microsoft was verry angered. NT version 4.0 had the VMS inclusions removed and that port was governed more-so by Microsoft. DEC was one of the first external porting groups to see Microsoft's code. Although WikiPedia says there is not a port of Microsoft Windows 2000 to the Alpha; that is a half-lie; it was not officialy released for Windows 2000 to be ported, and some of our friendly geek Microsoft employees leaked the Alpha platform version of Windows 2000 to the public. Even Microsoft knows that merit of its software existing on a high-end architecture improves its portfolio for contracts on super-computers.

    Sincerily,

    --

    I am the nightmare of nightmares.

  86. Huge Niche Markets by lcsjk · · Score: 1

    Since the early 80's it has been Intel's chips and a niche market. Sometimes the niche share was larger than Intel's share and based on the usage (auto, military, embedded, appliance) was and is significantly larger. Although some other chips were better and most had better initial architecture than the X86, the "Intel Inside" slogan really carried them through the initial PC years. I think Motoroly and MicroChip still sell a larger volume of Microcontrollers than Intel's PC line, but that little bit of information was not shown during my search for volumes.

  87. Im not dead yet by eadint · · Score: 2, Funny

    A customer enters a pet shop.
    Customer: 'Ello, I wish to register a complaint.
    (The owner does not respond.)
    C: 'Ello, Miss?
    Owner: What do you mean "miss"?
    C: I'm sorry, I have a cold. I wish to make a complaint!
    O: We're closin' for lunch.
    C: Never mind that, my lad. I wish to complain about this ALPHA what I purchased not half an hour ago from this very boutique.
    O: Oh yes, the, uh, the DEC ALPHA...What's,uh...What's wrong with it?
    C: I'll tell you what's wrong with it, my lad. 'E's dead, that's what's wrong with it!
    O: No, no, 'e's uh,...he's resting.
    C: Look, matey, I know a ARCHITECTURE when I see one, and I'm looking at one right now.
    O: No no he's not dead, he's, he's restin'! Remarkable CPU, the DEC ALPHA, idn'it, ay? Beautiful FP PERFORMANCE!
    C: The FP PERFORMANCE don't enter into it. It's stone dead.
    O: Nononono, no, no! 'E's resting!
    C: All right then, if he's restin', I'll wake him up! (shouting at the cage) '#include
    #include
    #define X 128
    #define Y 128
    #define Z 128
    #define T 120
    double A[X][Y][Z][T]; int x, y, z, t;
    main() { printf("\nprogram uses %g MBytes\n",X*(float)Y*Z*T*8.0/1.0e6);
    for (x=0;xX;++x) { for (y=0;yY;++y) {
    for (z=0;zZ;++z) { for (t=0;tT;++t) {
    A[x][y][z][t]=(x+1)*(y+1)*(z+1)*(t+1); /* - faster run time */ /* A[x][y][z][t]=sin(x+1)*sin(y+1)*sin(z+1)*sin(t+1); - takes more time */
    } } } } } ...(owner types an answer)
    O: There, it worked!
    C: No, he didn't, that was you Typing!
    O: I never!!
    C: Yes, you did!
    O: I never, never did anything...
    C: (yelling and hitting CPU) 'EHELO POLLY!!!!! Testing! Testing! Testing! Testing! This is your nine o'clock alarm call! (Takes CPU OUT OF CASE and thumps it on the counter. Throws it up in the air and watches it plummet to the floor.)
    C: Now that's what I call a DEAD ALPHA.
    O: No, no.....No, 'e's stunned!
    C: STUNNED?!?

  88. Re: and I just bought my own a few weeks ago by cblguy · · Score: 1
    I've been using OpenVMS on Alphas for a while at work... so I decided to pick up a Personal Workstation 500a off of ebay for playing around at home. Have it fully loaded now, running OpenVMS (yes, it's not an au machine, it's an a - that was fun :-P ), and have under $400 in the whole lot (including external Storageworks pedistal, over 50gb of hard disk, 640MB of memory, TLZ07 tape, full graphics video). :)

    Long live the (dirt cheap) Alphas! ;)

  89. A lot will be using this! by WebCowboy · · Score: 2, Interesting

    Those with critical VMS-based systems are breathing a sigh of relief that there will be support and replacement hardware for their old-but-reliable servers that have been running VMS non-stop, 24/7/365 for the past DECADE. If you are used to that kind of reliability you are obviously the type that would be advers to changing the entire hardware architecture until the last possible moment. Many of them are the type of folks who wailed and gnashed teeth when they had to migrate from the old VAX hardware to theie "new fangled" 200 MHz Alpha-based hardware--and it still ran the same OS!

    Anyways, I haven't seen a lot of discussion on what happens to the IP (Intellectual Property) once HP puts the Alpha out to pasture for good. I'd like to see it released to the public domain or made "open source" so royalty-free implementations can continue to be made by a large number of third parties. It would be very cool if any Joe Blow could download the VHDL or Verilog files to synthisize their very own Alpha-core-based FPGAs!

    1. Re:A lot will be using this! by Macka · · Score: 1


      Unfortunately HP don't own the Alpha IP, they never did. Compaq sold (virtually gave it away) to Intel (along with the Alpha design team) before it sacrificed itself on HP's altar.

      The fruits of that union haven't made it into the Itanium line yet, but it's coming, in a generation or two.

    2. Re:A lot will be using this! by Anonymous Coward · · Score: 0

      As I understand it, when Intel got the Alpha IP, it wasn't even able to get the registers working correctly. DEC had that stuff working like 10-12 years before.

      Seperately, anyone who wants reliable clustering and performance out of something other than Sun/Veritas would probably choose these. I work with 10 alpha clusters and we have damn near 100% uptime for the application and database. Having used MS clustering and Sun/Veritas clustering and HP clustering, you can have my Alpha's when you pry them from my cold, dead hands. (They will probably still be running too.)

      Seperately again, Compaq (before the sale of Alpha IP), when discussing the viability of the Alpha line, told us that even Intel used Alpha/OpenVMS to control the Intel Processor assembly line. Kind of poetic, isn't it.

    3. Re:A lot will be using this! by Artooman · · Score: 1

      First of all, Intel owns the IP for the Alpha design. Second, it might be difficult to release a design that may be in a proprietary language that uses proprietary tools. The deisgn may not be in a Verilog or VHDL format.

      Alpha is a fairly simple architecture. You can design a fairly modern Alpha (EV6-style) in a matter of months with two graduate students. I have seen it. If you are interested in designing an FPGA, it wouldn't be that hard.

  90. "Niche guys"? by ScottGant · · Score: 5, Insightful

    the world's line of chips seems to have declined to Intel and a handful of niche guys

    Didn't know that AMD is out of the game now. Guess they don't sell 64bit CPU's anymore...but we got those 64bit Intel chips in everything now don't we? Whoa...look-at-em go!

    I also didn't hear that the PowerPC architecture was all gone too...guess they're just selling what little inventory they have to the "niche" Apple market...but everyone know's that Apple's dying....any...day...now....

    Pfft...the submitter should remove head from rectum...

    --

    "Music is everybody's possession. It's only publishers who think that people own it." - John Lennon.
    1. Re:"Niche guys"? by SirTalon42 · · Score: 1

      I think by "Intel" he meant the Intel architecture (x86). And x86_64 isn't really all that big (yet), so it would easy to consider it a 'niche' market.

    2. Re:"Niche guys"? by Tassach · · Score: 5, Insightful
      By "Intel" the article should have said "x86". The x86 architecture, as fundimentally flawed as it is, has driven virtually everything else out of the market. Alpha's gone, PA-RISC is going, SPARC is on it's way out. The Power/PowerPC a architecture is hanging in there, so there's still some choice left for main-line computing.

      Of course the power of the various embedded processors (Dragonball,StrongARM) and single-chip computers are rising to the point that they could be meet most user's computing needs. We've reached the point where average users don't need any more power; they need the same power with less heat & noise and more reliability & stability.

      --
      Why is it that the proponents of "one nation under God" are so eager to get rid of "liberty and justice for all"?
    3. Re:"Niche guys"? by RzUpAnmsCwrds · · Score: 2, Insightful

      "The x86 architecture, as fundimentally flawed as it is, has driven virtually everything else out of the market."

      So fundamentally flawed, in fact, that x86 CPUs are the highest-performing, most compatible CPUs in the world.

      Seriously, who cares what the hell your code compiles to anymore? What's wrong with x86?

    4. Re:"Niche guys"? by Anonymous Coward · · Score: 0

      best performer?

      POWER, IPF, CRAY, NEC, ....
      best cheap performer perhaps.

    5. Re:"Niche guys"? by SewersOfRivendell · · Score: 1

      Note that ARM in various permutations is still going very strong, largely integrated into embedded controllers. Don't make the mistake of thinking that the only thing that counts is the computer market -- embedded is huge.

    6. Re:"Niche guys"? by Tassach · · Score: 4, Insightful
      What's wrong with x86?
      In Two words: Little Endian

      In Three words: Variable Length Instructions

      The RISC guys had it right. So right in fact that even current x86 chips are RISC on the inside, and then waste close to half their transistor count on circutry that does nothing besides transform the x86 instruction set into something that isn't brainfucked. That Athlon-64 would cost half as much, draw half as much power, and generate half the heat if you ripped out the x86 emulation layer.

      --
      Why is it that the proponents of "one nation under God" are so eager to get rid of "liberty and justice for all"?
    7. Re:"Niche guys"? by fm6 · · Score: 2, Insightful
      Didn't know that AMD is out of the game now.
      They're not (thank God! Imagine Intel with no real competition). But we're talking architecture here, and in that area AMD is more Intel than Intel.
    8. Re:"Niche guys"? by dleifelohcs · · Score: 0, Offtopic
      speaking of brainfucked, have you ever programmed in brainfuck?
      > Increment the pointer.
      < Decrement the pointer.
      + Increment the byte at the pointer.
      - Decrement the byte at the pointer.
      . Output the byte at the pointer.
      , Input a byte and store it in the byte at the pointer.
      [ Jump forward past the matching ] if the byte at the pointer is zero.
      ] Jump backward to the matching [ unless the byte at the pointer is zero.
      And of course, the Game of Life as implemented in Brainfuck. Complete with ASCII art sourcecode.
    9. Re:"Niche guys"? by RzUpAnmsCwrds · · Score: 1

      "best performer?

      POWER, IPF, CRAY, NEC, ...."

      SPECint is dominated by Xeon and Opteron. The fastest P4 is around 1700; the fastest non-x86 CPU is an Itanium2 at around 1400.

      SPECfp is not dominated by x86. If you want fp performance, you want to look at Itanium2 or POWER5.

      I never said that Xeon or Opteron scales well (Opteron scales pretty well actually), or that the fastest supercomputers in the world were x86. However, the 3.4GHz P4 and Opteron 250 are the fastest integer CPUs available today.*

      *Results may vary. Integer performance is based on SPEC data and may not reflect real-world applications.

    10. Re:"Niche guys"? by javiercero · · Score: 1

      Not really, endianess has nothing to do really... the only thing wrong with x86 is just one thing: REGISTERS!!!!

      And if by RISC you meant microcode...

    11. Re:"Niche guys"? by RzUpAnmsCwrds · · Score: 4, Informative

      "The RISC guys had it right. So right in fact that even current x86 chips are RISC on the inside, and then waste close to half their transistor count on circutry that does nothing besides transform the x86 instruction set into something that isn't brainfucked. That Athlon-64 would cost half as much, draw half as much power, and generate half the heat if you ripped out the x86 emulation layer."

      According to AMD and Intel comments, the translation circuitry is less than 5% of the total CPU. In fact, over half of the transistor count comes from L2 cache.

    12. Re:"Niche guys"? by DAldredge · · Score: 1

      Then why are UltraSPARC CPU's so expensive?

    13. Re:"Niche guys"? by vrai · · Score: 3, Insightful
      Because ...
      1. Sun sell them, and everything that Sun sells costs far more than it should. A 1Gb memory upgrade from Sun would bankrupt many small countries.
      2. The UltraSparc cost a lot to develop, but compared to IA-32 chips has a tiny market. Thus it doesn't benefit from the economies of scale that Intel/AMD have.
    14. Re:"Niche guys"? by akuma(x86) · · Score: 3, Informative

      1) The Alpha is also little endian.

      2) Complicated instruction decode can be removed from the critical circuit paths with pre-decoded caches. On one extreme, AMD uses predecode bits to mark where instructions begin in the i-cache. On the other extreme, Intel caches the fully decoded micro-ops in their trace-cache. When the variable length decode is out of the critical path, it can be made slower and therefore smaller.

      I don't know where you get your "half" numbers from, but I can assure you that the x86 overhead is nowhere close to "half". There is MAYBE 5-10% overhead in power/area. Most of the non-cache transistors in modern x86 CPUs go towards the out-of-order control logic (re-order buffers, schedulers, highly-ported register files, memory ordering buffers etc...) which attempt to extract instruction level parallelism from the program. High performance CPUs need this logic whether they are RISC or not.

      Another note -- Variable length instructions more efficiently encode your program so you don't need as big of an i-cache or as much bandwidth to the i-cache as a RISC processor. It's not all bad. Compile something on x86 and then cross compile it to some RISC processor and tell me how much bigger your binary is...

      Instruction sets are not where performance comes from. Circuit technology and underlying microarchitecture are FAR bigger components to performance and how much power your chip burns.

    15. Re:"Niche guys"? by Anonymous Coward · · Score: 0

      What's wrong with x86?

      In Two words: Little Endian

      In Three words: Variable Length Instructions


      I am afraid that takes many more words than that. Little endian is not any worse than big endian, actually, in a lot of cases (like when casting a long to a short) it is better. And variable length instructions are just a compression mechanism wich is very efficiently handled by the assembler and the CPU hardware. There is no sane reason why a
      add eax, 0xabcdabcd
      should be of the same length as
      mov ax, bx
      What is really bad about the x86 ISA is its unorthogonality (e.g. not all registers are equal, some instructions work only with certain registers), the shortage of general pupose registers, the FP register stack etc.

      -- Artur
    16. Re:"Niche guys"? by Anonymous Coward · · Score: 0

      Seems neat! I gotta try this.

    17. Re:"Niche guys"? by Anonymous Coward · · Score: 0

      Yeah, and don't forget that "niche" ARM has carved itself in the mobile phone and PDA market. They're only selling hundreds of millions of cores a year, and of course it's such a niche that there's no mainstream software support - you won't find ARM mentioned in the Linux or Windows CE porting guides. Unless you look.

      And your comments about the PowerPC are well received. We should perhaps be mourning the death of the MIPS architecture, since all the next-gen consoles are PPC based, which is another few hundreds of millions of cores over the next five years.

      When the submitter does remove his head from his rectum, perhaps he'll realize that in the broader microprocessor market, it's Intel and AMD that are operating in a "niche" - and it's a shrinking niche at that.

    18. Re:"Niche guys"? by grepistan · · Score: 2, Funny

      You're right. I'm stuck with this useless 2 dimensional desktop and dull, flat icons. It's just not pretty enough, dammit!

      --
      Real stupidity beats artificial intelligence every time.
      -- Terry Pratchett, Hogfather
    19. Re:"Niche guys"? by nhorman · · Score: 2, Informative

      Uh, I don't really know if I'd call eighty-some-odd percent of the procesor market a "niche". PowerPC family processors power almost all of the worlds large embedded systems (cars, planes, networking equipment, industiral robots, etc.). Mips, StrongARM, and dragonball processors are a growth market in the pocketPC space, and lets not forget the 8 and 16 bit processors that run all the little electronic components in your life that you don't ever think about (thermostats, gas and water meters, microwaves, etc.). Don't forget: Just because its not sitting on your desk, doesn't make it not a computer.

    20. Re:"Niche guys"? by julesh · · Score: 1

      In Two words: Little Endian

      And what's so bad about little endian? It allows for more efficient casting of pointers to integers, which can be handy. I don't see any benefits to big endian, other than it being the standard used for communication in most Internet related protocols.

      In Three words: Variable Length Instructions

      Without variable length instructions, it would have been impossible to extend the x86 as far as it has been extended without breaking backward compatibility. I understand the performance problems associated with them, and the fact that something like half of the power that goes into the chip is compensating for it, but this doesn't seem to have held up Intel or AMD from producing very fast chips using this architecture.

      The extra energy and cooling problems are the price we pay for backward compatibility. Unfortunately, backward compatibility has proved itself to be absolutely essential.

    21. Re:"Niche guys"? by cotyx · · Score: 1

      Memory isnt a problem its cheap and you have a lot of it. Alpha processor were designed to be fast, fastest of the world in computation. So the point of size of binary isnt important on calculus server like alpha.

    22. Re:"Niche guys"? by LurkerXXX · · Score: 1
      "That Athlon-64 would cost half as much, draw half as much power, and generate half the heat if you ripped out the x86 emulation layer"

      I dont' know about hlaf, but yes, you are right, it would be less. It would also loose the ability to run 99.99% of the applications that are currently run on it.

      There is a price to be paid for backward compatability, but sometimes its best just to pony up the money, because the other option is just more expensive/painful.

    23. Re:"Niche guys"? by akuma(x86) · · Score: 1

      Memory isnt a problem its cheap and you have a lot of it. Alpha processor were designed to be fast, fastest of the world in computation. So the point of size of binary isnt important on calculus server like alpha.

      Memory size (as in DRAM) isn't as important since DRAM is cheap, but the working set that fits in the caches is extremely important because cache real-estate on processor silicon is very expensive. Go price out the Intel extreme edition P4 w/ a 2M cache and the regular Prescott P4 with a 1M cache. Cost is exponential with die size.

      Bandwidth is also very expensive - You can see this with the premium being charged for 800MHz bus systems vs 533MHz bus systems.

      If your code does not fit in your caches, you're going to take more cache misses which will degrade performance. With a more efficient encoding of the program, this is less likely.

    24. Re:"Niche guys"? by Artooman · · Score: 1

      This is part of an age old debate between RISC and CISC.

      I would argue that variable length instructions have a very distinct advantage: They enable a very dense encoding of instructions (for x86, between 1 and 2 bytes per complex instruction) while in Alpha simple instructions are 4 bytes each. This not only decreases code size considerably, but it increases the hit rate per instruction in the instruction caches. This can be a large PERFORMANCE and POWER advantage. This is clearly a trade-off between extra decoding in the pipeline and a more efficient encoding in memory.

      Furthermore, if the instruction cache is a trace cache like many modern x86 processors, the instructions are stored in an decoded RISC-like format which requires no decoding. So under the hood, the advantages of fixed format instructions can be realized in x86 processors as well.

      What is wrong with little endian? This is just a preference. Does it really matter?

      x86's biggest problem IMHO is that it has too many extensions that must be supported (MMX, classic stack FP) and it has many architectural artifacts that must be supported (undefined flags actually being "defined" by an earlier processor).

    25. Re:"Niche guys"? by Anonymous Coward · · Score: 0

      1. Bi-endian CPU's.
      2. Why not make the assembler do some of the decoding before the CPU even gets to the code? The FRISC 3 did this, but 0-operand, multiple-stack architectures will have to make inroads before this becomes commonplace.
      3. The IGNITE I/II ISA eats the x86's lunch in instruction density. On the IGNITE 1, most instructions are 1 byte.
      4. Both the FRISC 3 and IGNITE 1 can execute most of their instructions in a single cycle. Subroutine returns on the FRISC 3 take up 0 additional cycles.
      5. The x86 begs for mercy compared to the FRISC 3 in interrupt latency. FRISC 3's do not need to save registers to create a working set for the interrupt handler or worry about interruptible instructions. Register-based RISC's don't fare much better than the x86 either. Many of them perform a delicate and lenghy pipeline-save when they receive an interrupt. There is a technique that I devised that moves this pipeline overhead to the interrupt return. It involves treating hardware interrupts like the Alpha's replay traps. But, AFAIK, no RISC chips that I know of use this.
      6. Just to top it off, neither the FRISC 3 nor the IGNITE 1 need an i-cache to perform decently.
      These are some reasons why 0-operand, multiple-stack architectures need to be considered.
    26. Re:"Niche guys"? by Anonymous Coward · · Score: 0
      the world's line of chips seems to have declined to Intel and a handful of niche guys

      Technically the Alpha was sold to Intel several years ago by Compaq shortly before they were bought by HP

    27. Re:"Niche guys"? by Lost+Race · · Score: 1
      Most of the non- cache transistors in modern x86 CPUs go towards the out-of-order control logic (re-order buffers, schedulers, highly-ported register files, memory ordering buffers etc...) which attempt to extract instruction level parallelism from the program. High performance CPUs need this logic whether they are RISC or not.
      Itanium doesn't. Look how much power and die space they saved by getting rid of all that stuff! :)
    28. Re:"Niche guys"? by cotyx · · Score: 1

      Thats right, that what branch predictor are for, and alpha's one has 99% success rate, it use 3 methods (local prediction, global prediction, and a statistical one which choose between the two previous result). Anyway, alpha's cache is fucking fast, and its not only about cache, its also between register. Alpha owns 2*80 internal registers with 64 publicly available. And it also owns a register rewrite systeme wich is common in superscalaire architecture (multi-pipeline). Dont mess with Alpha, its a fucking daemon !@# and i love it

  91. My Alpha by nooch · · Score: 1


    I have a Compaq Alpha Workstation that originally ran NT. It's currently running debian, and it does so pretty well. I made the mistake of doing a dist-upgrade, which on the alphas tends to break things. Bah. I was wanting to put gentoo on it anyways. They are special machines. Took me a while to even get the boot loader down, but when you do... nice.

    -J

    --
    Fire in the sky
  92. Re:Alpha lives! - on the itanic project by Anonymous Coward · · Score: 0

    Actually most of Intel's Itanic (itanium for your wonkies) engineers are former DEC Alpha engineers.

  93. Re:ebay - sadly no by Splork · · Score: 1

    i have never been able to find a cheap 21264 (ev6) based system. i'm still stuck with my wonderful but dated 666mhz 164lx.

  94. Ah the Alpha by CdnZero · · Score: 1

    In '96 I was in college taking my IT program and my greatest dream was to scrape up the money to build a multi-processor Alpha box... yes, I was pathetic...but just think of all those CPU cycles going unused!!

  95. Sad.. by guacamole · · Score: 1

    this is sad as Alpha never failed technically and was basically killed by the management at Compaq/HP. Once the first mass produced 64-bit CPU and for a long time the fastest processor in existence, even right now, Alpha still remains one of the fastestest CPUs on the market :-

    I heard MIPS is going the same way. The only non-x86 guys that remain standing are IBM/Power and Sun/UltraSPARC and I am not so sure about Sun's ability to compete with Intel in future given their recent record..

  96. just buy an athlon64 by Anonymous Coward · · Score: 0

    ...I like to think of it as the new Alpha, but with a fancy bytecode compressor (called x86-64) which doubles as a compatibility layer. :)

    1. Re:just buy an athlon64 by vincecate · · Score: 1
      I like to think of it as the new Alpha, but with a fancy bytecode compressor (called x86-64) which doubles as a compatibility layer. :)
      True. An Athlon-64 with a 1 MB cache does well alongside an Itanium with a far larger cache. Costs and price will always be less for the AMD64 than the Itanium. There is some goodness in getting small code size.

      Because of its NUMA ability, the Opteron is almost as lovable as the Alpha. With time I think it will win people's hearts the way Alpha did.

  97. Marketing (or the lack of) killed it. by Anonymous Coward · · Score: 2, Insightful

    DEC killed the alpha, and no one else. Heck, you simply couldn't *buy* the chip, unless (maybe) you really worked at it. I remember trying to get one in the mid-90's. You had to really struggle to find out exactly where to get it, *if* anyone would return your calls. Then the web took off, but even that was just a rehash.

    I really wanted some of these babys.

    I suppose my problem was that I wasn't a huge OEM. Let that be a lesson to those marketing folks: kill the hacker market, and your technology isn't going to prosper as much as it should.

  98. Hey d00d can you help me please?! by Ayanami+Rei · · Score: 0, Offtopic

    Help me please hack my registry to turn on quadalphabilinair mappng support so I can get shadows on my Nvidia TNT2!!!1

    thanx.

    --
    THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
  99. Every week since 1990? by Ayanami+Rei · · Score: 1

    Wow, the Alpha was dead before DEC even got it into production!

    --
    THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
  100. Death of anAlpha by JhohannaVH · · Score: 1

    Wow... man. I knew that with the death of DEC would eventually see the death of the Alpha. I worked on these babies when they first debuted in 94/95, and again at MCI in 97. I worked on both the NT4 platform and the Digital Unix platform, and they were some of the sweetest machines I've ever had the privelege of working with. I wish I had stuck around with them, but I made the right decision leaving the day Worldcom bought 'em. Wonder what ever happened to that server farm.. we had 8 Alpha-servers round-robinned to do call routing and billing. Fastest things on microchips at the time. The speed at which they could process a call from start to finish was insane! Especially given that this was 7 years ago now. Ahhhhh... the good ole days! :P

    --
    Sorry man... the Internet pooped on me.
  101. You can get x86 +4 way from Unisys... by Ayanami+Rei · · Score: 1

    (not that I recommend it).

    --
    THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
    1. Re:You can get x86 +4 way from Unisys... by turgid · · Score: 1
      Not the dreaded "Windows Mainframe?" Is that the 32-way box that no one at all bought? The one that they only managed to get installed in one site (Abbey National)? Wasn't it an unmittigated disaster?

      We all know that physically, x86 (intel to be specific) processors can be made to work together in greather that 4-way configurations (just roll your own glue logic), but the actual performance of such systems does not scale even remotely linearly with the number of processors. Programming the damned things for SMP isn't straight-forward at all past 4 or 8 processors (I forget the precise number).

    2. Re:You can get x86 +4 way from Unisys... by javiercero · · Score: 1

      Actually Sequent (now part of IBM) has been offering large SMP x86 machines from the mid 80's. I remember seeing a 16 processor 386 based machine in the late 80s. Also their new NUMA-Q architecture used Xeon's and scaled up to 64 processors. Also Data General moved their Aviion line from motorola 88K's to Xeons and could also scale up to 32 processors using their own NUMA architecture. Compaq has also offered 8-way x86 machines for a long time too...

  102. Alpha will nerer die . . . by Anonymous Coward · · Score: 0

    . . . until GCC stops supporting it.

  103. glassware is a troll. please mod down. by Anonymous Coward · · Score: 0

    As a CPU buff, I ordered a back-issue of Microprocessor Report where they discussed the introduction of the Alpha in glowing terms.

    You described Microprocessor Report's old paper as "glowing"? I have that same pamphlet in front of me and it is nothing glowing about it! It's just an infomercial with some tidbits on who will be selling the workstations and advertising it is 64bit.

    Moderators, this "glassware" user has been jumping into all the forums at wired.com to spread his propoganda. Says so many thing and it is obvious only supports Intel and goes as far as mentioning old dates of articles in near unknown journalism editorials to uninformed forum users to "uphold" his statments.. Some of his other trolls at wired.com were such fanatical that they seemed funny in the "epileptic monkey" sort of way, but that does NOT excuse him from the heavy cursing you've done to hurt the feelings of the wired.com forum participants. And your Slashdot posting is almost exposed, you jerk.

    glassware, please stop spreading lies and stay out of the wire.com and slashdot forums. Moderators, for the sake of the history behind his userID, please appropriatly mod him down; for the good of the slashdot experience.

  104. killed by OS/2 ? by wardk · · Score: 1

    the Alpha had it's death warrant signed when DEC allowed themselves to be played by MS in the NT vs OS/2 wars of the early 90's.

    As soon as NT got real traction on Intel, they tossed DEC aside like the cheap whore they were.

    but then again, maybe I am just being ornery

    1. Re:killed by OS/2 ? by Anonymous Coward · · Score: 0

      but then again, maybe I am just being ornery

      Nope that's exactly what happened.

  105. Re:And don't forget... nidgiot by Anonymous Coward · · Score: 0

    I'm not the poster you were responding to, yet I happened to have my hand shoved up my ass this moment.

    When I pulled my hand out of my ass, it was clenched around an ipod. Then as I walked out of the Apple store in the Mission Viejo Mall at California, I reached into my wallet to see the receipt of how many hundreds of dollars I shit for this Ipod and noticed that I used your Driver's License and your American Express card to purchase it!

    <Arnold Schwarzenigger mask>
    Hey, I am you and you are me!
    </Arnold Schwarzenigger mask>

    Just to make sure I wasn't dreaming, I took this picture out of your wallet that looks like your second cousin I think, and I shoved that picture back up my ass and walked back into the Apple store to see if maybe a black cat would walk by thrice as like in the movie Matrix. I didn't see a cat, so I left.

  106. Thanks. (moderate parent please) by Anonymous Coward · · Score: 0

    Quoth {

    "DEC's programmers also caused a small intellectual property dispute by actually using much of DEC's VMS code to compliment porting Microsoft Windows NT 3.5 unto Alpha, to much blessings and praise from Microsoft's high-end customers for its verry quick GUI performance"
    } Quoth

    I have Windows NT 3.5 and VMS on my Alpha XP1000. My friends always wondered why the Windows GDI functions were faster in Windows NT 3.5 as opposed to Windows NT 4.0. Thanks for revealing that ol' history of VMS in NT 3.5. Hope someone mods you up. It's posters like you that improves the quality of slashdot.

  107. Whooo hoooo Netcraft confirms.... by ckaminski · · Score: 1

    Alpha is dying...

  108. Wait... Intel *is* a niche guy. by Anonymous Coward · · Score: 0

    Farewell, Alpha; the world's line of chips seems to have declined to Intel and a handful of niche guys.

    Wait a minute, Alpha was a niche processor (workstations).
    And Intel's x86 architecture *IS* a niche processor, if you are referring to PCs. PCs are a niche product, representing a *SMALL* portion of the microprocessor marketplace.

    If you mean Intel, as in xScale, Alpha, x86 and IA-64... how's that a reduction, since Intel is still around?

  109. Mmmm by mlk · · Score: 1
    arewell, Alpha; the world's line of chips seems to have declined to Intel and a handful of niche guys."

    Mmmm, should that not be "the world's line of chips seems to have declined to ARM and a handful of niche guys."
    Or "the world's line of desktop chips seems to have declined to Intel and a handful of niche guys."
    --
    Wow, I should not post when knackered.
  110. Revisionist crap !! by Macka · · Score: 4, Informative

    But, towards the turn of the millennium, something strange happened: the Pentium Pro architecture (happily renamed PII and PIII) inched towards the lead in integer operations. The P4 actually surpassed the Alpha chips. Intel had, by then, hired away some of the Alpha designers and began to adopt its performance enhancing strategies. How could Intel catch up to the Alpha when Intel was burdened with an architecture as convoluted as x86?

    Not by your interpretations of events, and certainly not because Intel hired a bunch of Alpha engineers (that came much later). Unfortunately it's so old now that I can't find a reference to it in google, but you seem to be blissfully unaware of the law suit that DEC brought against Intel over the theft of Alpha IP that mysteriously found its way into the Pentium architecture. I was working for DEC at the time as a Tru64/Alpha support engineer, so I do.

    Some time prior to that there had been a quiet attempt at collaberation between DEC and Intel over the Alpha chip. I believe it was in a vain attempt to try and get Intel to adopt the Alpha architecture for future designs. Whatever the purpose, Intel were given extensive Alpha design docs to look at. Eventually they turned down the offer and went their own way.
    I remember eyebrows being raised inside DEC sometime after when the Pentium architecture started to make some very surprising, unexpected and unforecast performance leaps.

    It took some time to gather the evidence, but eventually Bob Palmer launched a law suit against Intel for theft of Alpha IP. For a while DEC were threatening to halt all Pentium shipments and demand large unspecified damages. Bob P should have stuck to his guns and screwed Intel for all he could get, but instead (being the bean counter he was and not a technologist) he saw this as an opportunity to unburden DEC of the escalating costs of constantly refitting the FAB production plants. Work that was needed to meet the next chip shrink goals and keep Alpha ahead of the game.

    In the end a deal was done. Intel brought all the Alpha fabrication and production plants off DEC, including StrongARM, and agreed to guarantee to produce Alphas for DEC for a number of years (I forget how many).

    DEC still kept control of the Alpha design & development, and it wasn't until much later after the Compaq buy out, in one last act of Corporate infanticide from a cadre of incompetent senior managers that lntel finally got their hands on the full set of Alpha technologies.

    But then that's what you get when Accountants run computer companies, not technologists and visionaries.

    Make no mistake about it, if DEC management had believed in Alpha technology as much as the rest of the people in the company, and DEC had kept the FAB plants and invested in them as they had originally planned to do, and there had been no Comaq buy out, you would today be looking at SMT Alpha EV8 chips running somewhere around the speeds of todays Pentium chips .. and NOTHING Intel, IBM or anyone else could product would have even come close to touching it. It wasn't any technology shortcoming that killed Alpha, just bad management heaped on bad management heaped on even more bad management.

    Macka

    1. Re:Revisionist crap !! by Anonymous Coward · · Score: 0
      Thank you. A friend of mine worked at a DEC-fab back in the days and he is still angry.

    2. Re:Revisionist crap !! by akuma(x86) · · Score: 1

      Make no mistake about it, if DEC management had believed in Alpha technology as much as the rest of the people in the company, and DEC had kept the FAB plants and invested in them as they had originally planned to do, and there had been no Comaq buy out, you would today be looking at SMT Alpha EV8 chips running somewhere around the speeds of todays Pentium chips .. and NOTHING Intel, IBM or anyone else could product would have even come close to touching it. It wasn't any technology shortcoming that killed Alpha, just bad management heaped on bad management heaped on even more bad management.

      Do you hear what you are saying? If all of these miraculous and EXPENSIVE events occurred, you'd have your SMT EV8 running "at the speed of today's Pentiums" So you'd have a super expensive chip running at the same speed as a cheap commodity chip?

      Oh right -- this is DEC with their brilliant innovation.

      They created a high-frequency, low-ipc design which is quite inefficient - why, AMD can do better by doing more per clock! And this "virtual processor" SMT thing is only a hack that they were forced to include because their pipeline was so inefficient. Why would they have such a high frequency? It must be marketing...

      I wish the EV8 did come out so that it would silence all of the clueless Pentium 4 critics :)

    3. Re:Revisionist crap !! by Macka · · Score: 1

      Do you hear what you are saying? If all of these miraculous and EXPENSIVE events occurred ...

      Miraculous, hardly! Expensive yes, but DEC had a huge cash surplus with Billions in the bank at the time, and Alpha sales were generating a couple of Billion a year even then. This is one thing I never did understand. Alpha was hugely profitable, even after Compaq brought the farm. But Compaq couldn't get themselves out of their small box mass market mentality and just didn't know what to do with Alpha. In any case the real reason for Bob P jumping out of the manufacturing business popped out of the woodwork after the Compaq buy out. Seems he'd been talking to Compaq about buying the company for at least two years before it was actually agreed. Compaq weren't interested because DEC had their fingers in pies that Compaq didn't want. DEC's networking products were one of them ... so Bob P sold that off, and the last hurdle was the FAB plants. Compaq did not want to be in the business of making processors. Basicly, Bob was shaping DEC ready for acquisition.

      As he made his exit from the company during the 'merger' we can only assume that his motives were short term gain for the shareholders, a 'glowing' paragraph on his CV for overseeing the demise of DEC, and a big fat wad of cash in his back pocket.

      ... you'd have your SMT EV8 running "at the speed of today's Pentiums" So you'd have a super expensive chip running at the same speed as a cheap commodity chip?

      When I said speed, I meant clock speed not performance. Take a look at the performance of the 1.5 GHz EV7 today, and use a little imagination to speculate the kind of performance a next generation chip would deliver at 2.5 GHz with multiple cores, and a memory bandwidth Intel can only dream about.

      To close with I'd like to quote from the "conclusions" drawn from this extensive review of EV8s design & technology wins from Real World Technologies ( http://www.realworldtech.com/page.cfm?ArticleID=RW T011601000000 ):
      The Alpha EV8 is an exciting new design for several reasons. It is by far the most aggressive speculative out-of-order execution superscalar RISC processor yet proposed. It will exploit SMT, arguably the most important new development in computer architecture in the last ten years, to double its sustained throughput to 8 to 10 billion instructions per second. When the EV8 first ships (2002?) it should drop easily into Compaq's then existing high performance computing platforms built around the EV7 and its on-chip dual 4 channel direct Rambus memory controllers and four 6.4 GB/s interprocessor communication link channels. It is hard to imagine what other architecture or platform could come close to challenging single or multiple processor EV8 systems in raw performance. But the onus is on Compaq to execute their high-end product strategy much more effectively then they have since acquiring DEC and Alpha in order for this technology to have the impact in the marketplace that it deserves


      Good day.

    4. Re:Revisionist crap !! by akuma(x86) · · Score: 1

      Having billions in the bank does not guarantee the your investment in the future is secure. Take a look at what happened to Sun. Investing billions into a low-volume server market would have made DEC look like Sun which is hurting from competition from Xeons and Opterons. Sorry, but even in the enterprise, hardware components are becoming commodities. It's all about the services and software.

      Paul Demone (from realworldtech) does not get paid to design CPUs. He gets paid to speculate about "paper" machines.

      By the way, I have been paid to design CPUs for the last 8 years and I continue to do so. Taking a design from concept to reality involves MUCH more than a paragraph of speculation by armchair-website architects like Paul.

      To counter your assertions...

      2.5 GHz is about what AMD is running today. It's not some magically high frequency. It's what traditional process scaling would get you.

      Multiple cores are something everybody is doing.

      Intel brought SMT to the world before EV8 even would have taped out.

      Memory bandwidth is NOT a CPU design problem, it's a system design problem which is just solved with money - More pins and wires...duh! There is no innovation there. Hell NVIDIA sells a mass market 40GB/sec memory bandwidth solution which is almost 2x the bandwidth of this EV8 system.

      So what you're saying is that EV8 would be a wider out-of-order core with SMT. Hmm...sounds like every other commodity x86 CPU out there (Opteron/Xeon). Tell me again how DEC would have made billions?

    5. Re:Revisionist crap !! by Anonymous Coward · · Score: 0

      That's because bobbie 'I don't fucking know, they just pay me to wear Italian suits' palmjob is a worthless, boner biting bunshole.

    6. Re:Revisionist crap !! by Macka · · Score: 1

      Having billions in the bank goes not guarantee your future is insecure either. And comparing DEC to Sun as some kind of predictor of how things would have turned out is stupid. DEC had lots of other divisions besides servers, including shock-horror, Intel Servers, Workstations and Laptops. You also don't seem to get that low-volume doesn't always mean low-profit. But maybe that mindset is a reflection of the end of the industry you're in.

      Paul Demone may not get paid to design CPU's but with the EV8 he did a a very thorough job of covering it over the 3 seperate articles he published on the subject. But then you wouldn't know that because you didn't read any of it did you :-)
      2.5 GHz is about what AMD is running today. It's not some magically high frequency. It's what traditional process scaling would get you.
      Thankyou, that's my point exactly. The Alpha chip was designed to be running at those speeds today, with the benefit of traditional process scaling, but that never happened because Compaq put the breaks on further development.
      Multiple cores are something everybody is doing.
      Not back then they weren't.
      Intel brought SMT to the world before EV8 even would have taped out.
      Bollocks, EV8 was supposed to go FCS in 2002, about the same time as Intel's pathetic attempt at delivering an excuse for SMT. Hardly been a raging success has it?
      Memory bandwidth is NOT a CPU design problem, it's a system design problem which is just solved with money - More pins and wires...duh! There is no innovation there. Hell NVIDIA sells a mass market 40GB/sec memory bandwidth solution which is almost 2x the bandwidth of this EV8 system.
      Apples vs. Oranges, NVIDIA don't make general purpose cpus. And besides, if memory bandwidth is not a cpu design problem, as you're trying to suggest, then how come Intel are so crap at delivering half decent memory bandwith on Xeons. They control the designs of both the chip & the motherboard, and they still can't get it right.
      Tell me again how DEC would have made billions?
      DEC were already making billions on Alpha, it's called profit margin. Something you're probably not very familiar with in the Pee-Cee world.

  111. Instruction sets have lost importance by erice · · Score: 2

    In the late 80's RISC was an immensely poweful concept. Fabrication technology had advanced to the point where it was just barely practical to dispense with slow microcode and hardcode and entire useful instruction set. But you had to be very selective in what you implimented. Spending gates on performance rather than high level instruction handling is what allowed 12Mhz Sparc and MIPS processors to stomp on 25MHz 68K's.

    In the 90's, Alpha's "RISC at any cost" allowed clock frequencies that CISC chips could only dream of.

    But today's CPU are huge and obcenely complex. Instruction decoding is a tiny part of that these monster chips do. In almost doesn't matter what the user visable instruction set is. It always gets chopped up and re-ordered anyway. What does matter is market share. Huge chips require a small army of font end designers to design all the resource allocation and instruction re-ordering. They require a large army of back end engineers to create a vast array of custom cells, layout the chip, and tune the process. That means you must you must sell a very large number of parts if you want to keep those armies on staff. A superior instruction set helps only a little. Inadequately funded physical design hurts a lot. With the possible exception of PowerPC, RISC architectures just don't generate enough revenue to keep up.

  112. Re:it wasn't management that failed, it was market by Anonymous Coward · · Score: 0

    you've got that right.
    ex-dec emp

  113. Half right. by argent · · Score: 3, Insightful

    It was definitely marketing, but it was more than that.

    Compaq dragged their heels on following Digital's development plan, and then pronounced its doom suspiciously close to the HP acquisition. Compaq *could* market, and if Compaq had understood what they'd got from DEC and really worked on expanding the Alpha business instead of going toe to toe against Dell's lower margins they and the Alpha would probably still be in business.

    Mentec, who *did* understand what *they* got from DEC, is still selling PDP-11s.

  114. But Itanic isn't going away for a while either by beakburke · · Score: 1

    since it is now replacing SGI's MIPS and HP/CPQ's PA/RISC and maybe ALPHA chips. I agree though that it isn't going to gain any market share wrt x86 or x86-64 (or even POWER). It might kill SPARC though.

    --
    ----- Question authority, but not ours. Hate the man, but we're not him.
  115. Sun doesn't have a FAB though by beakburke · · Score: 1

    I believe that TI does SUN's chip fabbing for them, SUN only does the design part. I'm actually surprised that Sun hasn't bought AMD and designed their future on x86-64 and linux/solaris, and sold SPARC to Fujitsu.

    --
    ----- Question authority, but not ours. Hate the man, but we're not him.
  116. You sound really drunk. by Anonymous Coward · · Score: 0

    You sound very very drunk. Funny how drunk people are pretty good at telling it how it is, though.

  117. the Alpha team by beakburke · · Score: 1

    I believe that the alpha team was moved to Intel as part of the HP/Itanium deal. But this only happened after many members of the team were laid off/left. I think the lead Alpha designer actually works/ed for AMD now. The K8 and some of the K7 was primarily designed by that group.

    --
    ----- Question authority, but not ours. Hate the man, but we're not him.
  118. Instruction sets have been marchitechted out. by argent · · Score: 4, Insightful

    doesn't matter what the user visable instruction set is.

    Sure it does. The further the instruction set is from what the processor's doing internally, the more time it takes for the front end to feed reordered instructions or recompiled instructions to the real ALU. The more time it takes, even if it all happens in parallel, the more latency there is between instruction fetch and useful work. When you combine that with a small register file that requires extra copies in and out of cache, even if that's simulated by a top-of-stack cache, you end up with huge pipelines and lots of instructions (real instructions hitting the internal ALU) that are just doing busywork.

    The longer pipelines you need to implement these inappropriate instruction sets means that cache misses and branch mispredictions are more expensive, because they cause huge bubbles in the pipeline and lots of wasted instruction cycles.

    Which means that your processors are running faster and hotter than RISC processors that do the same work ... the ones that were once thought outrageously hot but now seem merely tepid, and heat is turning into the next bottleneck in processor design.

    And that's why *despite* having a fraction of the resources directed to it than Intel or AMD have spent on their monster chips, and despite real neglect even before its doom was pronounced, the Alpha was still the fastest kid on the block right up until the day when, shortly before HP bought them, Compaq announced they were shutting down the EV8 development and terminating the Alpha line.

    No, a superior instruction set helps a lot. Not enough to satisfy Compaq, clearly, but more than enough that if Compaq had understood what they'd got from DEC and stuck to their original plans... instead of trying to outslug Dell on its own turf... EV8 would be the fastest chip on the market today.

    1. Re:Instruction sets have been marchitechted out. by Anonymous Coward · · Score: 0

      Wrong.

      The complicated translations can be cached therefore vastly reducing decode latency. Look up Trace-Cache (Intel) or Predecoded I-cache (Intel/AMD)

      The small register set is not a problem. Fast store forwarding takes care of the latency of the extra spills/fills.

      Do you think that there is a reason that x86 chips are the best performing chips on SPEC? (I discount the IBM and Itanium numbers because they just slap a silly amount of cache on chip - you could have done the same to an x86 and gotten more performance).

      Do an extrapolation of Alpha SPEC scores to today given previous performance growth trends and they still fall short.

      EV8 would not be the fastest chip today. Countless academic processor simulators are available and based on Alpha and model an EV8-style architecture. They do not perform to the level of Intel/AMD.

  119. Re:Sad - but the Alpha's children live on by stiggle · · Score: 1

    The chief CPU architect at AMD helped design the Alpha. A lot of Digital people also ended up there.

    When Compaq got rid of its Alpha stuff when it merged with HP - it sold it all off to Intel, which is using the technology in the new Pentium-M processors.

    So while the Alpha as a chip might be about to die, its children live on.

  120. love my alphas and will run them till they die by DeprecatedFeature · · Score: 1

    Most of the few machines we still have left at work are Alphas. All the rest of the systems migrated to our German headquarters when we were bought and are running, poorly on a system I can't name or I will be hunted down and killed. The Alphas which remain include machines dating to 1994 that are still running, and running well. My only problem over the years has been getting OpenSource software to compile and run on these OSF/now Tru64 machines. Tru64 is one the finest Unix implementations I've ever used and the Alpha chip and machines made by DEC were built for the long haul. The heat and power issues aside, if you ever get the opportunity to get a DS10 for home use, buy it. The small Dec stations are pretty awesome, too. The older machines like the 2100 and 2000, unfortunately, don't support very large hard drives but they are the perfect size if you need an end table by your couch.

    --
    maybe one day i'll be smart enough to come up with a cool sig, too.
  121. Garbage? You are mistaken. by Anonymous Coward · · Score: 0

    You are confusing architecture and CPU cores. AMD cores are not particularly like intels, they are however x86 and x86-64 architecture CPUs. I don't quite get why you seem to think having a different core (which is true even between different releases of a single series of chips, there are 3? different p4s?) equals being a different arch.

  122. humanity by Anonymous Coward · · Score: 0

    This is the same thing that happens to humanity. We live in an environment where the strong no longer are the ones that are surviving. We are in a world where the weak are encuraged and helped to survive.

    blablablablabla

    Guess the same thing happend to the Alpha.

    The good thing about this is that i will have a good processor which i can raise hell with in hell.

  123. R.I.P. by arsine · · Score: 3, Insightful

    As a former dec flag waver, this is a sad day. From the company that brought us the first 32-bit and 64-bit cpus, helped develop X-Windows, helped Microsoft with NT and provide a server platform with some credibilty, and whose platforms were among the first to run UNIX I'm sorry to see the demise of one of the best lines of cpus to bite the dust

  124. Yes, AltaVista was Alpha's Child by n9fzx · · Score: 2, Interesting
    DEC had the world's fastest, most reliable hardware, a flavor of Unix that was rock solid, a heritage on the Internet that went back to the mid 70s (Ethernet, firewalls, VPNs, wireless LANs, even Dave Mill's Fuzzball router ran on PDPs). What it didn't have were marketing people who could find their way out of a wet paper bag -- Ken Olsen saw to that.

    Enter the Internet Boom, DEC's last chance at a comeback. How do you market a capable platform around DEC's chimp-loving marketeers? Why, do something that Sun, IBM etc. cannot. Three researchers at DEC did just that, in the summer of 1995.

    Yes, we know about AltaVista's bellyflop as a portal. It was painful. But AV sold "more than 1000" AlphaServer 8400s, at an average MSRP over $1M a pop. It succeeded as intended, in spite of the lukewarm financial support from DEC's unimaginitive senior management.

    --
    ...-.-
  125. A Show of hands here.. by Dolemite_the_Wiz · · Score: 1

    How many people have installed the following operating systems on an Alpha Based server?

    - NT 4.0
    - Apple Operating Systems
    - AT LEAST two different flavors of Unix?

    (Dolemite Raises his hand!)

    Dolemite
    ___________________

    --
    Save the World! Use a Quote!
  126. OpenSource Alpha! by Anonymous Coward · · Score: 2, Interesting

    Seriously. Wouldn't this be a great time for HP to OpenSource the Alpha VHDL/Verilog Design? There is a project for open silicon. This would be a great investment and a hell of a tax writeoff to charity.

    Let's say, conservatively, that DEC/CompaQ/HP sank $1B into Alpha design and it's current value in the market is (?) $500 million. Some tax guy do the calculations. 1/3 of $500 million might create a blip on HP's radar for a while.

    OpenSource Alpha!

    Check out...

    www.opencores.com

    1. Re:OpenSource Alpha! by arsine · · Score: 1

      sounds like a pretty cool idea. there once was a time where alpha performance couldnt be beat ...

  127. Spot on !! by Macka · · Score: 1


    You hit the nail on the head there mate.

    It will be interesting to see what happens to Itanium performance when the Alpha IP that Intel 'acquired' starts to kick in. Hopefully HP will get their finger out of their arse and finish the Tru64/TruCluster technology migration in a similar time frame, and we might actually have a class Unix product to go along with the hardware -- again. HP-UX today doesn't even come close.

    1. Re:Spot on !! by argent · · Score: 1

      Well, the HP itanium is faster than the Intel itanium. I don't know that it's up to where Alpha would have been, and the compiler is seriously scary, but it doesn't seem as awful as the first generation.

  128. doh! by arsine · · Score: 1

    i forgot to add the following: my only question who would produce an open source, next generation alpha, its not exactly like burning a prom?

    1. Re:doh! by GreatBallsOfFire · · Score: 1

      The best bet would be to initially target it at FPGAs like the Xilinx devices. There are already a number of SoC and 8 bit processors on these devices.

      Unfortunately, 64 bits is a killer because of internal bus widths and, of course, internal registers will take up many cells, limiting what you can do on a single device. Still, it would be interesting to try.

  129. M6890E by PotatoHead · · Score: 3, Interesting

    The most powerful 8 bitter ever made. Powered Williams arcade games. Featured user stack, full indexing including program counter relative.

    Was possible to write reentrant and recursive code fairly easily directly in assembler.

    Compared to the more popular (and brain dead, but somewhat fast 6502) the 6809 was the shit. --Glad I learned assembler on one. Learning that chip, and later the 68000, biased my view of CPUs forever. Intel looked like a sad, slow kludge in comparison.

    Intel chips basically play the lotto. The faster you sift through the instructions, the more you will get done. Shove the bits in and let the cooling engineers sort 'em out. Blech.

    1. Re:M6890E by thogard · · Score: 1

      The 6809E was more of a 16 bit CPU than the 8088 was. It was the 1st MPU designed to run programs written by a compiler. It was a true work of art. The os-9 operating system (which was co-designed by one of the chip designers) was also very clean with loadable modules that were checksumed.

      I would love to see someone take the 6809 design and come up with a 64 bit version. Too bad Motorola dumped the 09 and never looked back. All the rest of the 6800 family seems primitve compared to the 09. Even the 68000 seemed to be a step backwards in some cases.

    2. Re:M6890E by grahamlee · · Score: 1
      The 6809E was more of a 16 bit CPU than the 8088 was.

      I find that to be true of a few of the supposed "8-bit" processors from the micro days. For instance, as well as the 6809E, the Z80 from Zilog had a couple of 16-bit registers and a 16-bit ALU, but was an 8-bit processor? Then of course the MC68k was called a "16-bit" processor by some people, despite its 32-bit registers and 32-bit ALU. The data bus was 16 bits wide, but that doesn't make the processor; consider the MC68008 :-)

  130. End Of The Line For Alpha by Anonymous Coward · · Score: 0

    So when will HP start production on the Beta chip?

  131. Ah, the 'cost benefits' of x86 ... by Macka · · Score: 1


    You're forgetting to factor in the additional costs of the extra Air Conditioning you're going to need for all those extra Xeons (installation and running costs). Boy do those things kick out some heat. Plus the electrical cost of running the Xeons, all that extra power they suck. Plus of the cost of extra sound insulation if your computer room is near any offices.

    Think I'm joking on that last point? I helped install a 64 node Linux Xeon cluster last year in a room opposite a large office. One poor woman put up with the racket for about a week before moving her desk to the other end of the office ... right opposite another computer room with 12 x Alpha ES45's (each with 4 cpus) . You couldn't hear a peep out of the Alpha room, but you could still hear the cluster of wailing Xeons from the other end of the corridor.

    Oh, and BTW, a cluster of 20 Xeons is not necessarily more useful than 4 x 1.5 GHz Alphas in one box. It very much depend son the application you're using. Not to mention per cpu licensing costs on your layered products (I'm talking closed source here of cause).

    Personally I'd rather have the Alphas .. they probably work out cheaper in the long run.

    Macka

  132. Like losing a friend. by Anonymous Coward · · Score: 1

    Politics killed it.

    I can never forgive the non-tech managers that did it.

    A robust hardware platform that excepts anything I throw at it. gone.

    Thanks, jerks.

    Retep Vosnul

  133. CoCo (6809, not 6890) by ce25254 · · Score: 1
    6809E => TRS-80 Color Computer I + II!
    Ah, that brings back sweet memories.
    (CoCo3 was 68B09e.)

    http://www.fact-index.com/t/tr/trs_80_color_comput er.html

  134. Re:Sad - but the Alpha's children live on by hughk · · Score: 1

    I seem to remeber that a few former Alpha engineers ended up at AMD. But you are right that the IP was sold off to Intel.

    --
    See my journal, I write things there
  135. Re:Niche guys.... [Clarification] by Anonymous Coward · · Score: 0

    These old machines are therefore a great argument for gentoo :)

    Too bad that these machines are so old that it exacerbates the already atrocious times necessary to get a system up and running.

    I'll get back to you in a few....months.

  136. X86 costs. by JollyFinn · · Score: 5, Informative

    The x86 pain in the ASS is more than just a die area for translation circuitry!
    A) Legacy instructions, legacy exceptions legacy... Pain in the ass, self modifying code detection.
    B) Strong memory model. Reduces freedom in reordering stuff, or simply increases amount of time.
    C) Amount of programmer visible registers, and lack of triadic operations.
    D1)
    In P4 the trace cache holds quite little number of instructions, because they are MUCH bigger than RISC instructions, and there is more of them for equivalent code.
    D2)
    Athlon line has extra predecode bits in its Icache and 3 large decoders. That consume POWER!
    E) Amount of parallerism available trough the ISA, is limited.
    F) Cost of adding parallerism is a LOT bigger in X86 because of
    Decoders or tracecache parallerism costs more. POWER, and latency/clockspeed.
    All the myriadic exception models have to be compatible.
    More memory renaming required and all pain in there.
    FLAGS! Renaming, and all trickery making that work so that it won't hurt parellerism,
    and accessed by most execution units!
    G) Clock speed is hurt because of the issue. Remember than IBM and SUN ran 1/3 of clock speed of alpha all the time, because of their design methology, until alpha lost their fab. The clock speed is more function of design methology, but ISA adds more complexity on some structures, complexity increase the distance travelled so that hurts clock speed, but intel has superiour fabbing and design methology for doing full custom designs.
    Now A, and D brings to a nice little point. LEAKAGE POWER which is growing component. Logic transistors leak 30 times the cache transistors. Besides even for inorder RISC:s CPU:s decode and fetch consume most of power so, that is where the X86 complexity hurts, most.

    Now the scale of economics, is the reason why X86 is as fast as it is. When you do full custom circuit design there is no way a semiasic design methology will catch you in performance or performance/watt, if goals are same. If you wan't to compare RISC vs X86 go for similar design methology use VIA for X86 candidate, and G4+ for risc. Intel and AMD and Alpha are compareble, up until 0.35u EV6. Yes thats a 600mhz OO 4 inst/cycle risc design made in similar process as under 300mhz PII:s , and that trounced everything. Too bad it came late for Digital. After that there is no highperformance targetting RISC with full custom designmethology available. Power is highly limited by its design methology in terms of clockspeed and instruction latencies, and having different design methology would simply increase the fixed costs for IBM so much that the scale of economics is not there. And for embedded market they prefere ability to customize the processor for customers so design methology choise is obvious for them.

    One small point, in power comsumption execution units are CHEAP, its fetch, reorder, and decode that costs power. Cache too is cheap in power comsumption based. So lots of cache and execution units is cheap in powercomsumption and the rest is where the power comsumption lies mostly. Exceptions, decode, fetch, and reorder. Now in ALL things in the list X86 ISA makes things more complex than equivalent RISC, and spends more transistors in there.

    --
    Emacs is good operating system, but it has one flaw: Its text editor could be better.
    1. Re:X86 costs. by akuma(x86) · · Score: 1

      A) Pain in the ass legacy doesn't cost much power/area - it's just mostly microcode and lots of time in validation which impacts time-to-market which I guess impacts speed since the longer you wait, the more mature the process becomes which translates into lost opportunity.

      B) The strong ordering model is used in most software - even the RISCs. For example, the most widely used memory model in SPARC is TSO (total-store-order) as opposed to RMO (relaxed memory order). Nothing is stopping Intel/AMD from defining an RMO-like memory consistency model. Good luck convincing software people to program it!

      C) Lack of registers is partially addressed by 2 things. X86-64 makes the jump from 8->16 which is quite good. Spill/Fill loads and stores can be removed from the critical path with memory renaming and fast-store forwarding. You still need to decode and rename the loads and stores which is overhead. The lack of triadic operations is also troublesome, but extending the ISA is not impossible.

      D1) The trace cache holds fewer micro-ops compared to RISC -- BUT! You get to go past taken-branches which increases your front-end bandwidth as well as reduces your latency. High-bandwidth and low latency are the key benefits.

      D2) Yes the 3 decoders burn power. This is a cost of x86. You can remove the high power by caching decoded ops through a trace cache or a less heavy-weight method like a small loop cache. There are various degrees of caching that can reduce decode power significantly. By your admission, caches are a low power item -- they are used extensively.

      E) Parallelism through the ISA is difficult for a compiler to expose. It's the dynamic hardware scheduler that gets you most of the performance. Things like load-latency are not predictable at compile-time so the compiler has no idea how to schedule instructions for that irrespective of the ISA. That's why everybody builds out-of-order machines for high-performance. That's why Itanium sucks for non-predictable load latency code (ie - just about all of SPECint).

      F) Trace-cache is low power - it's a cache. The decode only happens infrequently on trace-cache-miss so it's power impact is low (the bandwidth is also lower since it does not need to be fast -- only trace cache hit needs to be fast).
      Exception models are a pain in the ass but do not cost power or area in any significant way. Just more validation and design time.
      Memory renaming isn't even that big of a win when compared to competent store forwarding.
      All RISCs except for Alpha have flags. Big deal, we just rename them like everybody else. What's the big deal? It's just another really small source operand (it's not like 64 bits wide or anything).

      G) Clock speed is hurt? Excuse me, but x86 processors have the highest clock speeds around. You can't use economy of scale arguments because AMD has 2.4+ GHz CPUs out on the market in 130 nm tech. and they are hardly a giant.

      Leakage power is a problem for RISC and CISC processors. This is a problem for which solutions exist at the circuit and process level.

      You CAN'T compare a G4 to a VIA. The G4 is an out-of-order machine designed by a team of hundreds. The VIA was designed by Centuar in Austin by some 30+ engineers and is a simple IN-ORDER core. If you want to normalize on design effort (full custom vs. standard-cell vs. asic), compare and normalize engineering man-years.

      In conclusion - x86 is a PAIN IN THE ASS to design and validate, but the end product overhead in terms of die area and power are not that high. Maybe 5-10% on both count.

    2. Re:X86 costs. by JollyFinn · · Score: 1

      A) Fetch,Decoding is where the most power comsumption lays, because its the most complex part most instructions go through. And you say that X86 decoding is NOT more complex than risc? An you say Flags computation per instruction takes no power either? A hint, every transistor STAGE change costs power.
      B) I was speaking of high performance risc, not the one that gets less than half performance compared to alpha. And yes the X86 legacy prevents relaxed memory ordering.
      C) Extending ISA beyond extended ISA...
      D1) Its main purpose is keep X86 decoders away from main pipeline.
      D2) They are low power item, only thing that those loop caches are not used, trace cache has MORE than just a cache. The fetch part takes some power too. Cache doesn't consume huge amounts of power since most of it is not active, and its designed avoid leakage. But if you have small cache that is all the time active you consume power because of activating it all the time.
      E) Programmer visible registers, Flags dependencies, lack of triadic operations make more stops in the pipeline. Or the heroics.
      F) Trace cache simply hurts instruction hit rate. And there is more to trace cache than simple cache logic. Well those transistors, need to take care of ALL corner cases near critical path. Besides validation problem it hurts but not too much, but its still part of the crud...
      All riscs flags are handled differently, than X86 and hmm. OKay I'll admit. Alpha is in my ideas the RISC, and most others are simply something between risc and cisc, power for instance is only partially risc with all its Enchantchements, sparc has its complex register file that holds its down, ARM has its own problems with shift unit trick it made in early days, and while MIPS is cleaner it still has its cruft from 80's. Those riscy things have bits that turn off the flags for an instruction so those flags don't hurt IPC only clock speed. FLAGS PROBLEM IS REORDERING AND DEPENDENCY CHECK! It increases the number of imput operands for instruction by 50% so that much more reordering dependency checking increases..
      G) Yes it is. AMD is heavily competing intel in its own territory so AMD has to go with full custom design too. Its design methology and process that counts in clock speed. None of the surviving riscs use full custom design methology. There is plenty of difference from putting ASIC designers and ASIC design methology with slight tweaks for MPU developement like power does, than having engineers putting rectangles and tweaking for clock speed. Something to think why G5 has 2 cycle ALU latency at its clock speed, its mostly because of design methology used. AMD sells 20-30M processors per year, and thats order of magnitude bigger volume than ANY high performance risc. That gives them ability to tweak their process specifically for high performance MPU manufacturing, have multiple revisions on already made processor. [For comparable risc they don't made such revision.] And speed binning is more agressive definitely.

      RISC has less LOGIC transistors, for given execution width.
      The clock speed is more or less function of design methology, not just amount of engineers.
      EV5 was designed by engineering team whose size was 10% from Ppro team... Simplicity of ISA gave it advantage.
      Last but not least, the high performance risc volume is so small that it won't warrant as big fixed costs improvement by design team. AMD even as a smaller x86 player has order of magnitude bigger volume than biggest highperformance risc volume. [I won't count embedded uses for power as their volume as they are not using same parts as low end.] That volume improves amount of bin splits, and thats something that gives immediately 200 to 400mhz clock speed advantage for AMD over PPC. And for SPARC, well that is limited by ONE legacy design decision made in 80's. Alpha was the purest form of RISC and everything that survived in risc arena was not

      http://www.realworldtech.com/page.cfm?ArticleID= RW T060503232439&p=3

      --
      Emacs is good operating system, but it has one flaw: Its text editor could be better.
    3. Re:X86 costs. by akuma(x86) · · Score: 1

      I guess we'll have to disagree :)

      I work for Intel and get paid to design these x86 CPUs. I also know the Alpha designers because they too now work for Intel. In the past, I have worked on SPARC CPUs and MIPS CPUs. Therefore I know more than realworldtech.com

      I can assure you that X86 is complicated and needs a lot more design/validaiton effort, but this does not translate into more than 5-10% area and power compared to a RISC. It DOES translate into far greater design effort.

      Life would be easier if we had to design an Alpha. But remember that most prior Alphas were also full custom designs. AMD and Intel can't afford to be totally full custom anymore - the CPUs are just too complex now.

    4. Re:X86 costs. by JollyFinn · · Score: 1

      Well... [So I'd better stop treating you just another, apologist x86 software writer who is in love its own tools.]
      The extra design effort on X86 and work arounds in everyplace, do cost something, if you have simpler ISA you don't need cludges to work around it so much. And every single cludge will take power, some cludges will either add latencies, or increase cycle time. Think where you need to put the extra transistors! Especially how do you deal with 8 and 16 and 32 bit operations, with subword dependencies and hunting them. There are dozens of things and dozens of places where things get complicated. There is not a single place where x86 crufts
      Anyway perhaps we just look things from completely different perspective. The simpler ISA makes easier to do great things. I'm personally a EE guy who has enough software background to know what I can throw away from MPU, and what kind of software interface is needed, to be real general purpose CPU, And I've been spoiled by that freedom, by trowing out things that any sane assembler coder would object, but I don't design for assembler coders anyway, I'm designing ISA, and compiler, and first implementation by myself, there is certain optimizations available, when I look at everycorner how I could make it do more in parallel put less hw doing things, and everything, that affects in the performance. This freedom is... Hmm tainting my opinions towards anything that limits options for optimization. I'll balance the ease of programming vs performance equation just like old seymour, only difference is that these days things can be abstracted in software so that others won't have to deal with it.
      Well my opinions towards X86 is mainly tainted by fact that everything looks so cludgy...

      --
      Emacs is good operating system, but it has one flaw: Its text editor could be better.
    5. Re:X86 costs. by JollyFinn · · Score: 1

      One small point. The complexity simply reduces your chances of creating something truly spectacular, by forcing you to design around those complexities. Intel probably is 2 generations ahead of supposed EV8 introduction in a two years. And we see what kind of single threaded performance intel is going to bring desktop by then, since a full die shrink to 0.65u EV8 would of been 100mm (based on papers) Oh wait, you don't do such huge complex complex microarchitectures because you keep bumping on limits of manageable complexity and validation tasks for even something much smaller. The complexity the designers face always creeps in end product. Either for lack of features that could be desined, or lack of something else. You can trow lots of engineers to the problem, but simply increasing team size won't bring more novel microarchitecture, but makes you capable of working around big layouts, and low level design points. But overall high level design is still going to be something that single thread couldn't even come close to what certain other architecture could bring...

      --
      Emacs is good operating system, but it has one flaw: Its text editor could be better.
  137. Spirit of HP lives on in Agilent by joib · · Score: 1

    ... at least that's what I've heard. My admittedly limited experience with a few Agilent instruments confirm this. Solid quality.

  138. No by Anonymous Coward · · Score: 0

    You're so wrong it's funny, but nice try.

    By the way, anything other than theoretical differences between CISC and RISC are totally meaningless in todays CPU's anyway. The most CISC'y CPU's available such as the Hammer are really RISC cores. They're RISC/CISC hybrids. Even POWER CPU's have a lot of CISC features in them, and I don't think anyone could argue that POWER or PowerPC are "Reduced Instruction Sets".

  139. The sky is falling! by maximilln · · Score: 1

    I knew that the world was coming to an end when my favorite pub ran out of my favorite beer and my favorite sandwich. It's only logical that the Alpha would be sent to the chopping block.

    --
    +++ATHZ 99:5:80
  140. Just a tought by quies.net · · Score: 1

    If HP releases the architecture under a nice licence the Alpha architecture could be the first CPU with a open development cycle: the community develops and any company is free to produce the monster.

    I don't know if there are any legal obstacles?

  141. Re:Sad - but the Alpha's children live on by bhtooefr · · Score: 1

    WHAT?!?!? The Pentium M is based upon Intel's old P6 (Pentium Pro/II/III), with major modifications.

    It uses the Pentium 4's quad pumped bus and SSE2. What DEC tech does it use?

    Now, in the AMD corner, it's another story. The K7's bus was Alpha's double pumped EV6 bus, and I've heard that HyperTransport is the latest version of the EV67 bus, but I haven't seen anything to prove that.

  142. Re:Niche guys.... [Clarification] by drinkypoo · · Score: 1

    I have one "word" for you: distcc

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  143. Totally by PotatoHead · · Score: 1

    Writing assembler on that thing was pretty damn easy, and all the nice addressing modes!

    A 64 bit version would be interesting today. Heck a 32 bitter given the core design philosophies would punch well above its weight!

    1. Re:Totally by plover · · Score: 1
      I wrote an assembler for that chip for a class back in the early '80s. Just for the challenge, I hand wrote it in assembler, then hand assembled the opcodes into hex.

      That was a sweet little architecture that all made sense, no surprises.

      Ahh, the good old days.

      --
      John
  144. Not just x86 by yakovlev · · Score: 1

    IBM's System/390 is still very much around, so x86 isn't the only CISC holdout. I had a professor in college who firmly believed that in 20 years, two instruction set architectures would rule the world, modern variants of x86 and System/360. Still doesn't seem too far fetched.

    His conclusion was based on a single principle: backwards compatibility is INCREDIBLY important, and those are the two architectures with the least movable installed base.

    ARM and POWER seem to be the two RISC instruction set architectures settling in for the long term, so I'd probably call the RISC/CISC battle a draw.

    As for internal design, the RISC processors came up with good microarchitectures that CISC processors then copied. This didn't make them have non-CISC instruction sets, it was just a different implementation underneath.

    1. Re:Not just x86 by dutky · · Score: 1
      yakovlev wrote:

      ARM and POWER seem to be the two RISC instruction set architectures settling in for the long term, so I'd probably call the RISC/CISC battle a draw.

      I wouldn't call it much of a draw, at least not based on mortality: At the start of the RISC/CISC transition there were somehting like twice as many CISC architectures (~18) in the field than RISCs (~9). At the end of the transition, according to your figures, only two members remain from either camp. That translates to about a 90% mortality rate for the CISCs and only an 80% mortality rate for the RISCs. I'm really not sure how to declare a winning architectural philosophy with those kinds of losses.

      yakovlev continues:

      As for internal design, the RISC processors came up with good microarchitectures that CISC processors then copied. This didn't make them have non-CISC instruction sets, it was just a different implementation underneath.

      I agree entirely that architecture and implementation should not be confused (as the RISC/CISC convergence camp routinely does), but my point was not that the CISCs have become RISCs, but that the use of translation layers is a tacit admission of defeat for the CISC camp.

      In support of your draw hypothesis, however, is the fact that the high performance RISCs have had to resort to exactly the same tricks as the CISC crowd, implying that there neither side really won.