Slashdot Mirror


All 500 of the World's Top 500 Supercomputers Are Running Linux (zdnet.com)

Freshly Exhumed shares a report from ZDnet: Linux rules supercomputing. This day has been coming since 1998, when Linux first appeared on the TOP500 Supercomputer list. Today, it finally happened: All 500 of the world's fastest supercomputers are running Linux. The last two non-Linux systems, a pair of Chinese IBM POWER computers running AIX, dropped off the November 2017 TOP500 Supercomputer list. When the first TOP500 supercomputer list was compiled in June 1993, Linux was barely more than a toy. It hadn't even adopted Tux as its mascot yet. It didn't take long for Linux to start its march on supercomputing.

From when it first appeared on the TOP500 in 1998, Linux was on its way to the top. Before Linux took the lead, Unix was supercomputing's top operating system. Since 2003, the TOP500 was on its way to Linux domination. By 2004, Linux had taken the lead for good. This happened for two reasons: First, since most of the world's top supercomputers are research machines built for specialized tasks, each machine is a standalone project with unique characteristics and optimization requirements. To save costs, no one wants to develop a custom operating system for each of these systems. With Linux, however, research teams can easily modify and optimize Linux's open-source code to their one-off designs.
The semiannual TOP500 Supercomputer List was released yesterday. It also shows that China now claims 202 systems within the TOP500, while the United States claims 143 systems.

49 of 288 comments (clear)

  1. This is the year by Anonymous Coward · · Score: 2, Funny

    Linux makes it to the desktop, of a supercomputer.

    1. Re:This is the year by Anonymous Coward · · Score: 3, Interesting

      There is a logical reason for this, and it has nothing to do with Linux.

      The Supercomputers level of OSS use is primarily a concern with science. It compiles on multiple platforms, and is well maintained on most of them. Windows and MacOS are only available for the x86-64, ARM, and PPC platforms, and even then, not all of them. That only leaves FreeBSD as an option, and FreeBSD isn't as virtualization friendly, and drivers aren't readily available for GPU systems.

      So it's quite literately the only logical choice, owing to that the other choices would have required engineering resources.

      That said, Linux does not belong in safety systems, and I hope it never ends up in car automotive systems, power plants, or spacecraft. Everything else is fair game. These systems need real time operating systems that are highly threaded and can respond to events instantly, not be scheduled, or deferred due to eating all the swap space (one of Linux's worst default features, and what makes it woefully awful for web servers by default.)

    2. Re:This is the year by Tough+Love · · Score: 4, Insightful

      ...it's quite literately the only logical choice

      Oh I know, right? But the big fact you danced around is, Linux is just better than the others. It's faster and more reliable. Otherwise top 500 would not use it. Like, they tried to use Windows, they really did. Microsoft was paying academic institutions to install it and providing teams of free engineers. Still didn't do it. Why? Windows can't handle the load, it can't run continuously under load. It just gets more and more unstable then it falls over. Even when it does stay up, it can't touch the storage, scheduling or memory management efficiency of Linux.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    3. Re:This is the year by Anonymous Coward · · Score: 5, Informative

      > The Supercomputers level of OSS use is primarily a concern with science. It compiles on multiple platforms, and is well maintained on most of them. Windows and MacOS are only available for the x86-64, ARM, and PPC platforms, and even then, not all of them.

      This makes no sense. Almost all supercomputers are x86-64 based (+/- GPUs).

      > That only leaves FreeBSD as an option, and FreeBSD isn't as virtualization friendly, and drivers aren't readily available for GPU systems.

      Lol. Supercomputers don't use virtualization.

      > So it's quite literately the only logical choice, owing to that the other choices would have required engineering resources.

      That's not true, supercomputers within the past 5 years on the top500 list have used Windows, AIX, BSD, Linux. It's just that Linux is better for the job than the others.

      > That said, Linux does not belong in safety systems, and I hope it never ends up in car automotive systems, power plants, or spacecraft.

      I hope nobody who thinks supercomputers use virtualization ever have their opinion on a computing matter taken by the designer of a safety critical system.

      Linux is in safety critical systems already. But it depends on the level and capabilities you're talking about. Processing doppler radar data and sending it to ATC systems in a timely manner is one thing. Running tight control loops in automotive engine and control systems is completely different and just isn't appropriate for Linux.

      > Everything else is fair game. These systems need real time operating systems that are highly threaded and can respond to events instantly, not be scheduled, or deferred due to eating all the swap space (one of Linux's worst default features, and what makes it woefully awful for web servers by default.)

      You're mixing up all sorts of things here. Nothing responds to interrupts "instantly", what you want is guaranteed hard upper limits. It doesn't even have to be all that fast often times, it just has to be an upper limit so you can design the system to meet response time requirements. Linux can respond "immediately" to interrupts, by the way. It does not have to be "scheduled". Work can be done in interrupt context.

      "Highly threaded" what? That's nothing to do with real time.

      "Deferred due to eating all swap space" What is this meaningless drivel? Automotive and aircraft control systems don't use swap space. They don't even use virtual memory for god's sake lol.

      > (one of Linux's worst default features, and what makes it woefully awful for web servers by default.)

      Apparently better than all the others at that too. Windows, OSX, and BSD must *really* be shit if Linux is so bad yet it still beat them all there too.

    4. Re:This is the year by PeeAitchPee · · Score: 3, Insightful

      The other big logical reason is licensing. No one is ever going to pay for the required Windows or MacOS server licenses for installations of this size when there is free (as in beer) software available. They'd rather put that money into other parts of the project (more cores etc.) to eek out even more performance.

    5. Re:This is the year by The+Cynical+Critic · · Score: 5, Interesting

      That said, Linux does not belong in safety systems

      Dedicated real time operating systems obviously have their uses, but due to advances in embedded level hardware they're becoming less and less relevant. Even with the overheads of an "almost real time" OS like Linux with some compile switches most modern day embedded hardware is capable of making the dealines in all except some special super low latency use cases. Only place where a real time OS is even necessary these days are rare super low latency and super low power cases (as in under 0.25W).

      Serious, 6502s and Z80s are no longer the standard embedded hardware out there anymore.

      --
      "Why should I want to make anything up? Life's bad enough as it is without wanting to invent any more of it."
    6. Re:This is the year by Junta · · Score: 2

      You are right it's not about ability to take on load (though there is a matter of how self-reliant shops can be when trying to analyze failures, which is unlimited with Linux and inherently limited in Windows). However:

      the lack of tools and tracking down a couple numerical inconsistencies

      Those are pretty huge things. It all stems from the origin of supercomputing as a Unix thing, and as such similarity to Unix allowed seamless porting. Windows however is very different and requires more work to port all of the technical computing ecosystem that no one wants to do (except for a brief period Microsoft themselves, before they figured out just how *much* work they would need to do, how uphill a battle it was philosophically, and how utterly thankless a market win it would be even if they pulled it off).

      One could say if the situation were reversed, *maybe* the technical challenges would have been worth solving to get some cost savings, but even if Windows were 100% free, it still wouldn't make inroads into Top500 class systems, because it's a lot of work with no upside to be on Windows.

      It's the opposite challenge as Linux on the desktop. Linux on the desktop is perfectly capable and usable now, but there's so much stuff that is Windows only and not enough upside to address all that. We have an entrenched market in both cases and as such you either have to act*exactly* like what you are trying to replace or have to have something *really* worthwhile to convince the market to move.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    7. Re:This is the year by Ol+Olsoc · · Score: 5, Insightful

      It has nothing to do with not being able to handle the load. It has everything to do with costs. Linux is free. Windows isn't.

      If I get you right, You spend all this money on a Supercomputer, so you logically use the cheapest OS out there instead of paid ones that should work better?

      Sounds legit.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
  2. Re:'This happened for two reasons.' by Anonymous Coward · · Score: 2, Insightful

    There is no second reason.

    Linux is not used because it's better, it's used because it is cheaper.

    In the end, cheaper almost always wins over better.

  3. Doesn't guarantee success on the desktop by Anonymous Coward · · Score: 3, Insightful

    Unix never made inroads on the desktop.
     
      This might actually be harmful if people think Linux is complicated or designed for heavy hardware they may not consider it for desktops and use cases involving desktop apps.
     
      Linux has been ready for the desktop since about 1999, before that there were dependency issues and hardware wasn't always supported. Now hardware is more likely to be better supported on Linux than on Windows. I'm writing this on Windows but that's only because Windows came on this machine, I'll be installing Linux when I have a week of downtime.
     
      Enlightenment is probably the best looking desktop software anywhere, it's customizability makes it hard to include with distros but it should be considered as evidence that it's not user-friendliness or beauty holding Linux back.
     
      I think it's a bit sad to see Linux software becoming overly simplified in the wake of Apple's success the way other software is.
     
      Linux needs to remain the enthusiast and expert operating system more than it needs broad acceptance. Look what happened with the internet, Linux is great without ads, malware and other problems I associate with popularity.
     
      That said Linux skills are still hugely undervalued and not taught in schools which needs to change. A Linux machine is still your best bet that your machine will still be runnning with data and apps updated but not broken after 10-15 years.

    1. Re:Doesn't guarantee success on the desktop by Kjella · · Score: 4, Informative

      Eh, no, not really. You're talking about a KDE 1.0, pre-Gnome desktop... I used it, but I wouldn't have inflicted it on anyone I needed to support. Five years later it was certainly reasonable, at least where the average non-technical user was concerned.

      KDE was '96, GNOME '97.. in 1999 you'd already have KDE 2.0, didn't use that but I remember trying RHL 6.2 that came out in April 2000 which looks pretty much like a normal desktop to me. Remember that it was going head to head with Windows ME as the consumer desktop, using either was a major PITA. Granted, XP was a big step up but then you had Vista... you can make a lot of excuses for YotLD not happening but that Microsoft brought their A-game is not one of them.

      The cornerstone for Microsoft's dominance is Office and Excel in particular, all those people who had to use Windows at work of course took what little knowledge and training they had and bought a Windows machine for home too. When Outlook kicked Lotus Notes to the curb they locked that market up good.

      --
      Live today, because you never know what tomorrow brings
    2. Re:Doesn't guarantee success on the desktop by argumentsockpuppet · · Score: 4, Interesting

      On a scale of LFS to Mandrake, how bad was your experience?

      I'll be installing Linux when I have a week of downtime.

      It takes me a couple months to transition a new workstation to Windows. Each time, I try to learn what the native software options are and whether they can meet my current needs. Where it doesn't, I install or use recommended software in most cases to see if it does what I need (WSL) though I do have exceptions for my personal favorite software in a few instances where I'm just unwilling to learn something new. (EditPlus, GIMP, VLC, Sysinternals, Putty.)

      A new install of Linux takes the same process, but it has apt or yum or whatever which speeds things up pretty dramatically. With a new Linux desktop install, I just rarely have to learn too many new things... usually. (Eyeballing you hard here systemd!)

      If I have to support any significant sized network, and if it's possible, I'd do Linux desktops everywhere. I'd rather use those admin systems than admin Windows... but I work in a job where I have to support Windows because that's all the core software runs on. As an admin, I can do about anything I need to on Microsoft servers and workstations. It'd be false modesty to say I'm not good at admin on Microsoft system. On the other hand, I have used Linux and various BSDs at home and work (on servers) since the late 90's. I could eliminate Microsoft in our workplace and cut our IT departmental work by maybe 30% if only our primary system ran on Linux. I'd miss some of the AD/DHCP/DNS/DFS stack. I'd miss Excel (running native) and Exchange/Outlook, but honestly, running the alternatives in the cloud or Libre would probably reduce our helpdesk workload after a year or two.

      I'm good at my jobs, and whatever systems I admin, I'll learn to be good at. Given the ideal scenario, I could run several thousand workstations with the same effort I'd use for a couple hundred Windows workstations. The scenarios I have been hired to handle haven't been ideal, so I've learned to take advantage of the environments I'm in. I'm good at my jobs because I like to learn. I like tinkering, trying new things, scripting and writing real code. That makes me useful, maybe even it helps toward making me valuable.

      On the other hand, my varied experiences and experimenting have made me aware that my own weakness is a desire to try new things. If I were designing the systems for a company responsible for my income, it wouldn't be Linux or Windows or Mac. It'd be PC-BSD on the workstations and AIX on the servers. They're boring. Boring is what I look for in a business network. Ideally, the network will be so stable that IT doesn't spend any time working on the backend systems, and that means boring is the goal. I like Linux because I'm always learning new stuff and I like Windows.. sorta, because I'm always being forced to learn new things. That's why I'm sorry to see AIX take a dip off the top 500, but I can see it; Linux is fun.

    3. Re:Doesn't guarantee success on the desktop by PixetaledPikachu · · Score: 4, Informative

      Linux still isn't ready for any desktop it isn't installed on. It IS installed on lots of desktops in places like research labs, mine included. But if it's going to make it to anybody else's desk it needs some basic things fixed. I don't know if it's possible to do something as simple as configure a graphics driver in Ubuntu's GUI, but it's certainly not easy.

      Everything else works perfectly fine, but none of the GUI systems seem to offer a user friendly way for command line averse users to fiddle with their system settings.

      Both AMD and Nvidia have their config UI packaged to their binary blob driver on linux.

    4. Re: Doesn't guarantee success on the desktop by Anonymous Coward · · Score: 2, Insightful

      How the hell would you know? Ever tried a new software before? Everything has a learning curve. OS change is much more complicated, because you need to replace programs and actions you already know.

      Try switching to OSX (or Windows, if you already are using OSX primarily), it's different and i bet it'll take you more than a week to get used to it and find alternative programs

      You are nothing but a Windows' (or OSX's) bitch and your comment could have not been more idiotic.

    5. Re: Doesn't guarantee success on the desktop by stooo · · Score: 4, Funny

      >> "I'll be installing Linux when I have a week of downtime."
      If you need a week of downtime from MS to convince you to switch to Linux, you should rather stay with MS until having a month long downtime. Then you'll be really convinced :)

      --
      aaaaaaa
    6. Re: Doesn't guarantee success on the desktop by Interfacer · · Score: 2

      If you need a week downtime to install an OS which you already know -which the GP implies-, something is not right.

    7. Re: Doesn't guarantee success on the desktop by Zero__Kelvin · · Score: 2

      Maybe he isn't an idiot and wants to make sure he has time to handle any unanticipated issues. Migrating your working environment isn't just installing Linux, which can be done in an hour or three. A complete backup of the system needs to be done, and you need time to verify all the data has been restored and you can still do all the things you need to get done. Then, unlike with Windows, you have the ability to customize and tweak to your hearts content.

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  4. Re:That's because... by Tough+Love · · Score: 4, Informative

    Linux was originally made in Finland.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  5. Not surprising by jwhyche · · Score: 3, Interesting

    From what I know about the windows kernel it couldn't scale upwards well enough to run in this league. And If I remember correctly one of the key goals of Linux was to make sure it could scale well on big iron systems.

    We still don't know if you can successfully beowolf cluster a bunch of the old Microsoft Barnies though.

    --
    I read at +2. If your post doesn't reach that level I will not see or respond to it.
    1. Re:Not surprising by Anonymous Coward · · Score: 5, Insightful

      And these piece of shit Linux nodes fail all the time.

      That must be why all 500 are running Linux - for the great failure rate. Or maybe you're wrong.

    2. Re:Not surprising by Zaelath · · Score: 2

      So they're a $5-6 million in electricity to run, $100-200 million to design/assemble, but what really decides the OS to run is the cost.

      OK.

  6. Re:That's because... by anon+mouse-cow-aard · · Score: 4, Funny

    oblig: other OS's are Finnished?

  7. What a pathetic bunch of comments so far by GerryGilmore · · Score: 3, Insightful

    How far has the discussion quality fallen? Apparently this low, even without a political bent.

    1. Re:What a pathetic bunch of comments so far by Freshly+Exhumed · · Score: 2

      I signed up here almost from the very beginning of Slashdot time. A few days earlier and I might have had ID#100000. From what people have been saying here in all those 19+ years, Slashdot was dying, has always been dying, is still dying, and will always be dying. I just ignore the irritating cruft, and I'd advise everyone to do that.

      So, moving right along... how about those TOP500 scores!

      --
      I deny that I have not avoided attaining the opposite of that which I do not want.
    2. Re:What a pathetic bunch of comments so far by Steve72 · · Score: 2

      Imagine a Beowulf cluster of these?

    3. Re:What a pathetic bunch of comments so far by CBravo · · Score: 2

      In Russia, Beowulf cluster imagines you.

      --
      nosig today
    4. Re:What a pathetic bunch of comments so far by AmiMoJo · · Score: 2

      Slashdot has definitely changed. I remember when it was more of a marketplace of ideas, where interesting comments were actually modded "interesting" instead of "flamebait" or "troll". I remember when everything wasn't a conspiracy of some kind.

      Back on topic, imagine a Beowulf cluster of the top 500 supercomputers!

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
  8. Re:Obligatory xkcd by Freshly+Exhumed · · Score: 2

    That time when Linus's wife could not be Rickrolled because her Linux box had no Flash capability was a searing tragedy in the annals of computer history.

    --
    I deny that I have not avoided attaining the opposite of that which I do not want.
  9. So, Linux turned the Top500 into a Monoculture by williamyf · · Score: 2

    So, the Top 500 list of computers was dominated by many Variants of Unix, with a little sprinkle of other weird stuff (among those, VMS). Which is not a monoculture

    Then, as the other weird stuff waned, Windows took it's place (for a short while). Not directly as a replacement of course, but rather as a percentage of Top500 systems.

    On the other side of the fence, Linux began to take increasign market share of the Top500 because of low cost, shallow learning curve from *nix, and posibility to modify source code, in an accelerated path to become a monoculture (at least where the Top500 is concerned).

    And now, finally, we are on a monoculture in the Top500, with Linux all the way in the Top500... No *BSD, no AIX, HP-UX, or Solaris. Just Linux all the way.

    Better not catch anyone complaining about Chrome Monoculture, Windows Monoculture, or Android monoculture! M'kay? ;-)

    --
    *** Suerte a todos y Feliz dia!
    1. Re:So, Linux turned the Top500 into a Monoculture by quantaman · · Score: 2, Insightful

      So, the Top 500 list of computers was dominated by many Variants of Unix, with a little sprinkle of other weird stuff (among those, VMS). Which is not a monoculture

      Then, as the other weird stuff waned, Windows took it's place (for a short while). Not directly as a replacement of course, but rather as a percentage of Top500 systems.

      On the other side of the fence, Linux began to take increasign market share of the Top500 because of low cost, shallow learning curve from *nix, and posibility to modify source code, in an accelerated path to become a monoculture (at least where the Top500 is concerned).

      And now, finally, we are on a monoculture in the Top500, with Linux all the way in the Top500... No *BSD, no AIX, HP-UX, or Solaris. Just Linux all the way.

      Better not catch anyone complaining about Chrome Monoculture, Windows Monoculture, or Android monoculture! M'kay? ;-)

      I think the reason it's become a Linux "monoculture" is that it isn't really a monoculture.

      Top-500 should be an area that's amendable to variety. Any one project is big enough that some serious customization is going to occur, so traditionallyany one OS could focus on a specific feature set and nab themselves a bit of the market. That's why the big Unixes co-existed for so long, if your problem was a round hole you'd grab the Unix that looked the most like a round peg, and if you had a square hold you'd grab one that looked like a square peg.

      But Linux is modifiable, so if you need a round peg you can make it a round peg. If you really need a specific feature or optimization you can write a kernel patch. That doesn't matter for the consumer market but it matters for the top-500 list.

      I wonder what the future of the BSDs is, they have cool communities but I'm not really sure where their niche is.

      --
      I stole this Sig
  10. Yeah. And? by thedarb · · Score: 2

    What'd you expect it to run? Windows?

    --
    This sig intentionally left blank.
  11. Re:Yeah. And? by iggymanz · · Score: 3, Informative

    five years ago, 3 of the top 500 did run windows, and in 2011 4 did.

  12. Re: 'This happened for two reasons.' by qwerty+shrdlu · · Score: 4, Funny

    Odd statement, considering Microsoft mantra declares Linux is far more expensive than Linux.

    I think you got that backwards

  13. Re: 'This happened for two reasons.' by repka · · Score: 2

    I think he got it just right.

  14. Re:Microsoft's supercomputing efforts by Bert64 · · Score: 3, Interesting

    There was an "HPC" edition of windows 2003, and microsoft managed to sponsor a few places to build clusters using it that made it into the top500 list...
    I don't recall anyone ever using it of their own volition tho, only if microsoft were paying, and at least one of those clusters was a dual boot experiment which climbed 50 places in the ranking when booted to linux.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  15. Re:Where's the source? by rgbatduke · · Score: 5, Informative

    I'm not even sure what you are asking here. Do you truly have no idea how a GPL works?

    Anyway, you have this exactly backwards. The reason Linux became popular during the parallel supercomputing "revolution" (and I say this as a modest expert, at least at that time) is because it IS an open source operating system, so you could hack the kernel, write your own kernel drivers, fix things like networking bugs or system balance issues, and handle memory at a very primitive level. You got then, and can easily get now, the complete source of the OS and all of its device drivers, although the latter has been a constant source of contention between hardware mfrs who think that a device driver that makes their hardware run is some sort of "trade secret" and the keepers of the Linux kernel. Over decades (at this point) the mfrs have largely given up and actively help with kernel drivers instead of insisting on binary-only distributions. This played a critical role in the development of early parallel supercomputers once Linux had its first kernel capable of symmetric multiprocessing with two (and rapidly more) CPUs or (later) cores, or both. That would be roughly kernel 2.0, although there were still serious issues with race conditions, (network) driver interrupts and lockups, memory management, and so on, through 2.0.4+ -- really they went on forever as the 2.0 kernel wasn't truly symmetric, handled interrupt locking "badly", and took a lot of revision and some new paradigms to smooth out and stabilize. Ah, those were the days...

    Microsoft, on the other hand, made you sign away your firstborn child in order to get a copy of the OS source -- even as a research institution. If (say) your network drivers were slow, or locked up while multiprocessing, you were SOL. You COULDN'T fix it. You couldn't even find the bug. And it wasn't worth the effort -- even if you sacrificed a goat and got the source -- to learn to work with the source because it changed at MS's whim and all your work could go down the tubes at any moment and if you DID develop anything that ran on their system in some "custom" fashion, you ran into serious issues if you wanted to share it. You COULDN'T share your work with anybody else, not unless they had a surplus of goats or firstborn children too.

    "Anybody" (with a need and decent programming chops) could join the linux kernel list and communicate directly with the main kernel developers and report bugs, contribute fixes or drivers, etc. There was a lot of healthy debate about what needed to be fixed, or improved, first, second, third etc, as well as just how to go about fixing them -- sometimes it required substantial redesign and had to wait for a major bump (and a lot of testing). You could of course hack/fix your own kernels or add your own device drivers, or fix broken drivers, or mess with internal "tuning", and I and many others did, but behind the public scenes the actual kernel developers -- the heart of linux, as it were -- made steady, inexorable progress.

    By the year 2000, Linux had made serious inroads into not only the top 500, but there were literally uncounted small clusters that weren't fast enough (or weren't architected correctly) to crack the top 500, which relied on things like the Linpack benchmark to determine who to include. There were lots of folks who didn't USE linear algebra in their computations who built massively parallel compute farms with many different architectures and purposes who didn't even have the benchmark software installed (or give a shit) about their "ranking". Both PVM and MPI were fully ported onto Linux and most of their ongoing development was taking place on Linux boxes. Additional tools for management and job distribution and much more were developed -- on mostly Linux boxes, but yeah, there were still SGIs and Sun Microsystems clusters and much more out there. They suffered -- badly suffered, terminally badly suffered in pretty much all cases -- from being much, much more expensive than over the counter Intel or AMD box

    --
    Even when the experts all agree, they may well be mistaken. --- Bertrand Russell.
  16. BSD by ArchieBunker · · Score: 2

    The *BSDs will keep on doing what they have always done. Run well with minimal upkeep and not beta test features on production releases. Under Linux the mentality is if something compiles then ship it. I ran Linux in the 2.0.x kernel days. What they call Linux today is so far removed it might as well be a different operating system. Some distros don't even include tools like nslookup or traceroute anymore. Good luck installing that package if your default route isn't set. Oh and "route" has been changed to something else now for no good reason. What exactly was wrong with the old program and syntax?

    --
    Only the State obtains its revenue by coercion. - Murray Rothbard
  17. Re:'This happened for two reasons.' by jrumney · · Score: 2

    I think the cliffhanger ending is the editors attempt to bring back slashdotting. There was once a time, when sites would be brought to their knees by a front page story on Slashdot. These days noone reads TFA, so the concept of slashdotting has faded from memory.

  18. Re:That's because... by 93+Escort+Wagon · · Score: 4, Funny

    Actually he abandoned his homeland in search of warmth.

    --
    #DeleteChrome
  19. Of course it requires a supercomputer by 93+Escort+Wagon · · Score: 3, Funny

    ... to fully appreciate all the features of the latest Enlightenment desktop.

    --
    #DeleteChrome
  20. Limitation of a single computer by Prien715 · · Score: 2

    For most parallel problems, it's possible to divide them and send each piece to different computers, rather than a different core on the same computer. For even more highly parallel problems, using a GPUs to do the computation is even faster.

    With 100 gig ethernet, we're starting to see networking speeds closer to bus speeds on motherboards themselves and it's cheaper, faster to scale (especially dynamically), and probably more fault tolerant (node fail? Send the job to a different node) to use more computer nodes rather than using more processors in a single computer.

    Distributed computing has almost made supercomputers irrelevant -- except for people with a hole in their pocket. Folding@home is more powerful than anything on their list while we have no idea what monster of a compute clusters work inside Google or Facebook -- but given the open source software they have released (e.g. Facebook's 360 degree video stitcher) and how slow they are on a single machine -- the only way they'd be usable on their site is if you have a massive cluster.

    --
    -- Political fascism requires a Fuhrer.
    1. Re:Limitation of a single computer by serviscope_minor · · Score: 2

      Distributed computing has almost made supercomputers irrelevant

      Not really, no. supercomputers are distributed computers with good interconnects. For many calculations, the interconnect is really, really REALLY imortant which is why a good number have the interconnect right there on die with the CPU.

      --
      SJW n. One who posts facts.
  21. Re:That's because... by YukariHirai · · Score: 4, Insightful

    Anybody still believe Linus Torvalds about how Linux was just for fun?

    Of course. Linux was just for fun; now he makes a living out of it. A person's motivations for doing something don't have to remain exactly the same for the whole time they do it.

  22. Re:Any cluster scales by Anne+Thwacks · · Score: 5, Funny
    plenty of Windows clusters doing stuff.

    The technical term for this is "botnets".

    --
    Sent from my ASR33 using ASCII
  23. Re:That's because... by invictusvoyd · · Score: 4, Funny

    shhh.. No one knows that all the TOP 500 supercomputers run on EMACS..

  24. Re:'This happened for two reasons.' by Anonymous Coward · · Score: 3, Informative

    Bullshit.

    Linux is used because it's far, far, FAR more flexible, less resource intensive and more efficient than Windows, while supporting and making good use of vastly larger amounts of RAM and CPUs.

    If you baseline is one of the proprietary Unices, it's still more flexible, less archaic and more familiar to users while supporting a wider range of hardware while being infinitely cheaper.

  25. Re:That's because... by bruce_the_loon · · Score: 2

    After optimizing his computer to the point the CPU couldn't produce enough heat to warm his house anymore.

    --
    Trying to become famous by taking photos. Visit my homepage please.
  26. Re:Where's the source? by Tough+Love · · Score: 2

    I'm rather sure that means since the super computer builders are building their own OS out of Linux, they don't have to supply anybody the source as their not sharing it. However I may be mistaken...

    You are mistaken. Top 500 shops are regular contributors to mainline Linux development, with test cases, patches and more than a few core developers. They do it because they benefit from it, and they save money that way, they don't need to carry patches. And they aren't "competing" in the commercial sense, they just want the best system they can have, and that means, play with the community.

    anybody here that knows the contract of Linux that can verify this?

    Contract??? You really don't get it, good luck with that.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  27. Re:'This happened for two reasons.' by Megol · · Score: 2

    Price is a positive thing of course but not why it is used - the cost for OS software in a supercomputer would be a fraction of the hardware and infrastructure costs anyway.

    The thing is that Linux have excellent scalability when it comes to I/O throughput, this is something that many companies and individuals have worked hard to achieve. So it is possible to adapt an OS installation to be suitable for extreme throughput.

    The compute nodes themselves doesn't really need a proper operating system (and many supercomputers/clusters in the past had extremely limited systems) and in fact any OS overhead is processing power wasted. Userspace programs using the MPI to communicate is the norm. And again the adaptability of Linux is an advantage, customizing a small efficient kernel with the necessities and nothing else is easy.

    But the most important thing is that people already have done the adaptions and that those are available for others to use. Sure there are system specific things that have to be changed anyway but that would be the case for any large cluster machine. The closest to plug and play one can come.