Slashdot Mirror


In The Works: Windows For Supercomputers

Robert Accettura writes "According to ZDNet, Microsoft may be feeling threatened by Linux gaining ground in the High Performance Computing (HPC) arena. As a result, they have formed a HPC group to bring windows to these systems. It makes a mention of how clustered computing may be a target. I guess the only thing better than crashing 1 computer at a time is crashing an entire room full at once."

38 of 705 comments (clear)

  1. I guess Bill thinks it's time... by Mike+Buddha · · Score: 4, Funny

    I guess Bill thinks it's time to slow the worlds fastest computers to a crawl. Apparently they aren't crashing enough, too.

    --
    by Mike Buddha -- Someday the mountain might get him, but the law never will.
    1. Re:I guess Bill thinks it's time... by AKnightCowboy · · Score: 5, Interesting
      I guess Bill thinks it's time to slow the worlds fastest computers to a crawl. Apparently they aren't crashing enough, too.

      Well, unless Bill's going to introduce a version of Windows that doesn't have a Windows interface, WTF is the point? How many Beowulf nodes have you seen even plugged into a KVM? Windows is a stupid choice for a headless compute node just as Linux is a stupid choice for a home desktop.

    2. Re:I guess Bill thinks it's time... by jarich · · Score: 4, Insightful
      Remote Desktop works fine for this type of application. You log into the box as needed, do what needs doing and then log out or disconnect.

      Windows has come a long way since you knew you'd see the blue screen of death twice before lunch. On decent hardware it's very stable.

      Denying the current stability of Windows is no different than Bill and Co. denying the stability and power of Linux. It's pointless and it makes you look out of touch.

    3. Re:I guess Bill thinks it's time... by Yorrike · · Score: 4, Insightful
      "just as Linux is a stupid choice for a home desktop."

      Works for me, and hundreds of thousands of others.

      --

      Looks can be deceiving. Or CAN they?

    4. Re:I guess Bill thinks it's time... by cbiltcliffe · · Score: 4, Interesting
      Windows has come a long way since you knew you'd see the blue screen of death twice before lunch. On decent hardware it's very stable.
      I run six Linux machines, and one Windows one at home. The Linux machines are running on a mixed bag of mongrel hardware, from an old Compaq Deskpro Pentium 166, to a 466 Celeron. (Old stuff, I know...)
      One is just a motherboard, processor and hard drive sitting in and around a motherboard box. This is the database server for my website.
      They run with virtually no maintenance, and only ever need to reboot if I do a kernel upgrade (rarely, on a server machine) or get a power failure. (I know....I'm an idiot for not having UPS's on my servers. Well, it's a home network....sue me.)
      My Windows machine just got a fresh install of Windows XP on a brand new 120GB drive for a LAN party this past weekend. The install was done the Wednesday before. Three days old.
      When I got to the LAN party, it wouldn't boot, as the entire registry was corrupted. One piece of it was actually completely missing.
      After an hour and a half of screwing around, doing a recovery install of Windows from my CD, and generally wanting to take the Flak Gun from UT2004 to my system, I finally got it to the point where I could actually play something.
      This is on hardware that runs Linux just as well as the rest of my machines.
      And don't even get me started about what happens to XP when you install SP1.......

      --
      "City hall" in German is "Rathaus" Kinda explains a few things......
  2. Field day for the worms by troon · · Score: 4, Funny

    I hope those guys have good firewalls.

    --
    Ydco co ,df C erb-y go. a Ekrpat t.fxrapev
  3. Obligatory clippy comment by foidulus · · Score: 5, Funny

    "It looks like you are building a cluster, would you like me to tell you how Microsoft can bring it to it's knees?"

  4. hijack ware by wpiman · · Score: 5, Funny

    Great- when the cluster gets hijacked by spyware and the like- it can send out 3 millions spam emails a hour as opposed to the 5000 a Dell does now.

  5. Windows on HPC? by ifoxtrot · · Score: 4, Insightful

    Is it just me or does the notion of a GUI on high performance computers sound at bit pointless. I thought the point of HPC was to crunch masses of numbers - not something joe average will want to do any time soon. So what's the point of a pretty (and resource hungry) windows interface?

    1. Re:Windows on HPC? by beacher · · Score: 5, Insightful

      One thing alone will kill this idea... Licensing costs per proc. Linux really shines when you want to keep the TCO down due to the fact that you can get away with doing it and have zero licensing costs. (Note the get away with - I know that most HPC/Grids are installed and supported and there is support costs but that's another arguement.....

      Imagine if Google had to pay Microsoft a recurring license for their server farm and be forced to keep in lockstep with Microsoft's Licensing costs. Think there'd be a higher push for advertising and more intrusive ads? I do.

    2. Re:Windows on HPC? by Anonymous Coward · · Score: 5, Insightful

      Insightful?? Narrow minded and uninformed more like it! This is slash dot, news for nerds not lets poke fun at windows for everything they do even if it is useful.

      Now for the insight - Windows XP embedded has a mode to run headless (that is without a monitor or screen - the thing above the keyboard that looks like a TV and where the pictures change or for you "windows" haters the black screen with the green writing on it!)
      Also look at the Windows Storage Server no support for a graphic display on the box it runs on.

      Windows may not be your cup of tea but lets look at the good points and bad points when things like this are posted and use facts if we want to make fun.

      Bye Bye...

      P.S. sorry to jump on you Mr Trot but you were the first poster to make a dumb statement that got moded insightful but I'm sure there are more deserving victims of my rant. Guess I had a s#$% day!

    3. Re:Windows on HPC? by Lonewolf666 · · Score: 5, Interesting

      Actually, they have done this with XP Embedded. We have tried this in a project for a windows-controlled device, and you *can* build a rather small Windows XP that has your program as "shell" instead of the usual Explorer. Maybe not quite as small as Linux in text mode, but it will do.
      The claims about Internet Exploder being inextricably connected to the OS were pure FUD for the antitrust suit.

      --
      C - the footgun of programming languages
    4. Re:Windows on HPC? by tymbow · · Score: 4, Interesting

      I'm a Windows dood at times, but I can't see this working. The only way it might work is if the nodes are not traditional Windows installs, but rather are the core kernel and support only - ie: they have no GUI or any of the fluff and just enough to get on with doing what they have the do. The management or user land machines (or whatever the correct term is in HPC land) of course would have some GUI components. Mind you, I've wished to see a stripped down version of Windows without the GUI (or being able to start the GUI as an option ala STARTX) for ages. Maybe this is the beginning... Good luck is all I can say. They ahve a lot of work to do if it is ever to be credible.

    5. Re:Windows on HPC? by BlowChunx · · Score: 4, Insightful

      The real problem is that the Windows OS is largely inseparable from its GUI and, as it currently stands, is way too bloated to run individual HPC nodes efficiently and effectively.

      I do CFD for a living. When I started my new position a couple of years back, I convinced my boss to move to Linux because (Linux + ifc) was 50% faster than (Win2k + visual fortran) for the single processor codes we were running.

      I can see Microsoft trying to pare that difference down, but it will still be prohibitive when coupled with licensing costs.

  6. Windows HPC by LittleBigLui · · Score: 5, Funny

    Because every Node needs a Windowing System in Ring 0.

    --
    Free as in mason.
  7. BSOD by Mr_Silver · · Score: 4, Insightful
    I guess the only thing better than crashing 1 computer at a time is crashing an entire room full at once

    All we need now is a BSOD joke and I'd swear that everytime I read Slashdot it induces a timewarp back to 1998.

    --
    Avantslash - View Slashdot cleanly on your mobile phone.
  8. Proof by WordODD · · Score: 5, Insightful

    This action from Microsoft is proof positive that they are taking notice of the recent accomplishments of Linux and are trying to counter them with strides of their own in areas that are not their specialty. If nothing else then this is positive for everyone because not only will Linux continue to improve and develop on its own but now both MS and Linux will develop to compete with one another making the overall user computer using experience better for everyone involved. I know everything MS does is looked down upon by the /. majority but this really should be seen as "a good thing".

    --
    Please do not let scientific accuracy interfere with the intended humourous/interesting/insightful value of this comment
  9. Here we go again... by allanj · · Score: 4, Insightful

    The same as ever - whenever Windows is mentioned, lots of wisecracks about crashing is posted. Did you imagine they'd port Win95 or Win3.11 to HPC? Duh. They'll port something like WinXP or W2K3, and guess what - those are quite stable OS'es. Of course you CAN make them unstable, but that goes for PenguinWare as well...


    Ah well, I better put on my flamesafe suit - I forgot to criticize Microsoft...

    --
    Black holes are where God divided by zero
  10. What the fsck by drizst+'n+drat · · Score: 4, Insightful

    Why in the world would someone want to run a bloated GUI based operating system on hardwared designed specifically to provide services (servers) to it's customers? Unix is great in this aspect as (at least for the most part) running xdm and serving up a graphical interface was intended primarily for end users requiring execution of applications in multiple windows. Unix servers used to NOT run xdm (or any graphical engine) for the purpose of streamlining and providing efficiency and better utilization of system resources. Windows (even in the current Win2003) is far too large for use in a high performance computing environment. Bill my man ... get a clue ... windows isn't for everything!

  11. WIndows for clusters by miquels · · Score: 5, Funny

    .. codename "domino" ?

    --
    Living is a horizontal fall
  12. nah, just a PR move. by twitter · · Score: 5, Interesting
    This is a PR move. Clustering is just another thing that Windows can't do. All the Linux clusters popping up everywhere, especially at universities, demonstrate this to PHB and "influential" types. It tends to tarnish the wizz-bang image M$'s has carefully built among the clueless. Microsoft knows that PHBs will never run a cluster, a Hotmail or anything other than Word. By making one or two announcements, they can convince the clueless that M$ is all they will ever need.

    --

    Friends don't help friends install M$ junk.

    1. Re:nah, just a PR move. by Anonymous Coward · · Score: 5, Funny
      What do you mean, Windows doesn't cluster? Of course it clusters! In fact, Microsoft go to great lengths to tell you how to cluster your Microsoft Windows Server to achieve the best performance. There's the:

      • Primary Domain Controller
      • Secondary Domain Controller
      • A backup Secondary Domain Controller (In case the first one fails)
      • The Exchange Server
      • The second Exchange Server (Because the first can't handle the load
      • The backup Exchange Server (In case one of the two primary Exchange Servers fails)
      • The IIS Server..
      • The fallover IIS Server..
      • The fallover fallover IIS Server
      • The MS SQL Server
      • The MS SQL Server backup
      • Two or more file servers
      • The Backup server, running Arcserve or similiar (Because even an MCSE can tell you NT Backup is utter turd)
      • The Active Directory Server
      • The backup Active Directory Server

      • See? All those computers in multiple clusters. Microsoft are always ahead of the game!
  13. 'Windows' does not necessitate a GUI by ethnocidal · · Score: 4, Informative
    I'm amazed that people confuse the two. Can there really be zealots with their vocal organs sufficiently inserted into their nether regions who believe that Windows and the GUI used by Windows are one and the same?

    I'd invite you to look at Xbox as an example, and the operating system which that runs. There is no requirement for Windows to include a friendly GUI, animated characters, BSODs or any of these other 'hilarious' /. stalwarts.

    1. Re:'Windows' does not necessitate a GUI by Alioth · · Score: 4, Insightful

      The kernel doesn't necessarily need a GUI. However, as it stands, there's an awful lot on Windows that cannot be done on the command line and must be done on the GUI. For example, with the standard Windows install, it is not possible to change the computer name from the command line without downloading a utility to allow you to do it. It is not possible to kill a process from the command line without getting a Resource Kit utility from Microsoft. It is not possible to add or remove a network service (not a system service - I'm talking about the services you add in the network connection control panel, things like file and print sharing services) and after days of Googling I've still not found a way of installing or uninstalling one of these services using the command line.

      Windows is fine as a desktop OS (even if issues like this make automated rollouts a bear) but is inappropriate for the server since there are so many things that can only be done trivially through the GUI.

    2. Re:'Windows' does not necessitate a GUI by tasinet · · Score: 4, Interesting

      " For example, with the standard Windows install"
      Uhm.. *Which* standard Windows install? Xp pro? 2K sp35? 2K3 sp69?

      "It is not possible to kill a process from the command line without getting a Resource Kit utility from Microsoft."
      Not true. XP PRO ships with tasklist.exe and taskkill.exe.
      The first lists your processes and the second kills them. The second is quite useful, too, as you can mass-exterminate processes by username or other filters. Entirelly useful if you want to delete all the spyware & other-useless-crap your computer boots up with.

    3. Re:'Windows' does not necessitate a GUI by Alioth · · Score: 4, Insightful

      OK, I stand corrected on the tasklist.exe/taskkill.exe utilities. The main thrust of my point still stands - there are many things that are trivial to do on an SSH session on many non-Windows operating systems that can only be done via the GUI on Windows, such as the aforementioned network service installation/configuration (netsh won't do it, unfortunately - I thought I was onto a solution by using netsh dump to save the settings in a text file, but it's about the only part of the configuration it seems *unable* to be able to manipulate).

      For changing the computer name you must either write your own program to do it in C or VB, or download a utility to do it. Same goes for adding things like new network adapters - you need to use separate tools that come with a Microsoft resource kit. These are things that should be trivially possible from the command line in a default install, but they don't even come with Windows Server 2003 let alone XP Pro.

      Then, another issue for servers. If you're writing a program that takes input from multiple sources - let's say, a socket, a named pipe, and a serial port, and some weird USB device. To process data on these three streams you must have different code to handle and dispatch input on each one - select() for sockets, PeekNamedPipe for named pipes, WaitCommEvent for serial ports, and probably some vendor specific thingy if you've got some custom USB device. On proper server operating systems, the API is consistent enough that all this input is presented in the same way and you can use select() for all four streams, reducing the complexity of your server program and therefore the possibility of bugs, and cutting out the need for four threads (and the potential race conditions if you make a programming error) and only needing a single thread to look for stuff happening. It's as if the people writing different parts of Windows didn't talk to each other when doing it, and each had to independently come up with a new way of doing it. There are other examples where the API could have been made much simpler and more consistent.

      Since the original version of NT was incompatible with DOS anyway, and DOS had to be emulated, Microsoft could have swept away all the cruft when they made NT - but instead they insisted on making something even more kludgy. Don't even get me started on the NT GINA (I had to write one) and the appalling lack of documentation. We had a very expensive (ca. $40,000 US) support contract with Microsoft so we could get support when writing our GINA (we had to write a total replacement due to the nature of the system we were contracted to build). We ended up talking one to one with NT developers - but guess what, the person who'd written this stuff had since left and it was more or less undocumented even inside Microsoft. We ended up having to almost reverse-engineer the MS GINA to find out what was going on to make our GINA set the right stuff on login.

      I'm sorry, but when faced with stuff like this, all I can conclude is Windows isn't designed or meant to be a server OS, regardless of how Microsoft markets it. It's fine as a desktop OS (I use it on the desktop daily) but that's where it should stay. A Macintosh, the quintessential desktop system, has an OS more suitable for servers these days.

    4. Re:'Windows' does not necessitate a GUI by GamerGeek · · Score: 4, Interesting

      I have a feeling that the Microsoft approach to HPC will be significantly different then traditional systems. It is entirely possible that they could create a stripped down operating system, like something you would find in the embedded market, to create drone computers. These drone computers would not have a gui, not have any programs on them and do nothing but be a slave to some proprietary remote execution protocol. Then they would release a "Windows HPC server" which would administer all the drone computers with a GUI interface. They might even be able to get the drones to PXE boot from the server. To integrate with this product there would be HPC.NET with which you could write programs to harness the power of the grid/cluster. It might even be that the HPC system itself is distributed a .NET runtime. Microsoft's approach to HPC will not be what we know as clustering/grid computing today. It will be an integrated Microsoft proprietary system that will be simple to get into and hard to move away from.

  14. Crashing by Andy+Smith · · Score: 4, Funny
    I guess the only thing better than crashing 1 computer at a time is crashing an entire room full at once
    Yeah because Windows crashes all the time for me. Oh yes, every day. Every hour!

    Oh no, hang on, it doesn't. Ever. I boot up in the morning, switch between video and photo editing software hundreds of times throughout the day with regular use of MSIE and Eudora as well, and then I shut it down at night without it having crashed once. Every day. For years.

    Old versions of Windows crashed a lot. Current versions don't. Fact.

    This is part of the reason why Linux isn't gaining mainstream acceptance fast enough. Linux advocates talk about all these imaginary flaws in Windows and people out here in the real world think "well that isn't my experience at all". The effect is to create a distance between regular people and Linux advocates, which in turn pushes the mainstream acceptance of Linux further and further away. Linux needs to be seen as "the other big operating system", not some niche software used by a minority who seem to have a totally different experience of Windows than the rest of us.
    1. Re:Crashing by ViolentGreen · · Score: 5, Insightful

      The problem is this. Some people, like yourself, have no problems with Windows, and it works great. Some people, like my girlfriend, have Windows installations that crash all the time. So yes, Windows can be perfectly stable, if you're lucky. (I should also point out that shutting the machine down at night shouldn't count; decent computers have sleep modes and never have to be rebooted just to make them stop using electricity.)

      With Linux or OS X or whatever, you don't have this kind of inconsistency. Basically everybody who uses them, ignoring people who run experimental kernels or unsupported drivers, never has them crash, even when the computers are up for months at a time. You don't have to be lucky or do anything special. Yes, Windows is better, but it still has a long way to go. When my girlfriend's PC stops crashing a couple of times a week (running XP) then I'll reconsider.



      I think it has more to do with the quality of the hardware than windows itself. On my old compaq computer, windows crashed all the time. On the machine that I built, windows is very stable. The difference is that I know what hardware is in the case and I trusted the hardware before I put it in.

      Both XFree86 and KDE were unstable on my old compaq machine as well. I had no problems with the kernal though.

      OS X is built to run on Apple's hardware so they don't have to worry as much about 3rd party hardware. Most all Linux users that I know build their own machines and know what hardware is supported by linux and what is not.

      I may be off here but that is my take on it.

      --
      Not everything is analogous to cars. Car analogies rarely work.
  15. A little vaporous? by RetiredMidn · · Score: 4, Insightful
    Do I detect a pattern here (emphasis mine)?

    Although Microsoft is a comparative newcomer to the market, the company could bring several advantages:

    Machines running Windows HPC Edition could seamlessly connect to desktop computers...

    Microsoft could create a specialized version of its widely praised programming tools...

    Microsoft could also adapt its popular SQL Server database software to run on high-performance systems...

    And Microsoft could build software into its desktop version of Windows to harness the power of PCs...

    Well, I guess it's time for everybody else to abandon this space, because Microsoft has it all covered.

  16. Windows Clusters available now..... by stiggle · · Score: 5, Informative
    Windows doesn't cluster? So what about those that have ranked in the Top 500 list then that run Windows?

    In the November 2003 list....
    At 68 - a Windows based system at Cornell from Dell with 640 processors (it originally started out at 320 on the list with 252 processors).
    At 128 - a Windows based system in Korea with 400 processors.

    So Windows doesn't cluster?

  17. Branding it as Windows by jesterzog · · Score: 4, Insightful

    Well I agree with you. I do think it more likely that Microsoft would at the very least turn off the graphical part of Windows, remove it completely, or possibly re-write it from scratch.

    What I really don't understand is why it would be necessary or smart to brand such a product as Windows at all. Windows means graphical user interface, and the way it's presented ties quite closely to desktop use. It definitely doesn't mean the remote administration that's likely to be required for an HPC, and trying to remotely administer a Windows box is usually quite clumsy compared with a unix box unless you drop a lot of the traditional Windows UI stuff that's often so tied into its operation.

    When I think of Windows, and I don't think I'm alone, one of the first impressions that comes to mind is a relatively klunky monolithic GUI-dependant operating system that spends a lot of time drawing pretty front-end pictures. This almost certainly isn't an accurate picture of what's actually happening all the time and it's not to say that Windows couldn't be adjusted to work in other ways. But it's a first impression.

    You can at least argue that the graphical side of things is good for usability on the desktop (even though usability realistically takes a lot more than pretty pictures), but why on earth would Microsoft want to continue that image into an HPC market? Surely they have completely different customers in that market with different goals that likely don't include chewing processor time on pretty pictures for the UI.

    To me at least, it'd make much more sense for Microsoft to simply create a new operating system here from scratch (or buy a company or whatever they do), and call it something that's not Windows. It could be Microsoft HPC Server, for instance, and be completely independent from Windows. Microsoft can then claim that their new OS specialises in HPC tasks, and it'll also give them an independent OS product to push in the future if either it or MS Windows collapses.

  18. The real problems with this... by Vellmont · · Score: 4, Insightful

    A lot of people seem to be concentrating on the "windows crashes a lot" idea. That's not quite a fair judgement of windows anymore. The only time I've had problems with Windows 2000 and above is poorly written drivers, or anti-virus software. As long as you choose hardware with proven drivers and don't run anti-virus software (firewall it and run minimal services and no IE) Windows should be very stable.

    With that said, I think there's other problems with windows as a supercomputing cluster. The first I can think of is lack of a low-bandwidth interface. Linux you can ssh into and get results, control processes, etc. Windows requires a high bandwidth terminal services. In other words it's harder to control remotely.

    Other people have brought up the licensing costs, but I'm sure MS would offer huge deals just to get their foot in the door.

    I think the biggest problem is just historical and cultural though. The scientific community has a 30 year history with Unix, is familiar with programming in that environment, and has a lot of legacy code that's written for it. They just aren't going to take to a windows environment easily at all.

    --
    AccountKiller
  19. Processor Architectures by Ianoo · · Score: 4, Insightful

    Sure, there are x86 clusters. But there are also an awful lot of IBM supercomputers using Power chips, HP supercomputers using PA-RISC, heck even Apple clusters using PowerPC, SGI machines, Sun supercomputer nodes, and so on. There are a large number of strange and mysterious chips built explicitly for supercomputing that would never be seen in any other kind of use. There are also a large number o different interconnect technologies.

    Since Windows is a closed source operating system, are Microsoft volunteering to port Windows HPC to whatever architecture you happen to come up with? What about the bugs that occur when they write this port? How long is it going to take to get Windows stable on an unusual architecture if only Microsoft can change the source but only you can do the testing?

    At least with a custom kernel or Linux you can work on the system yourself until it's up and running, and if you're in the business of installing and running clusters/supercomputer, you can probably afford to pay programmers to write an operating system for nodes in that cluster/supercomputer.

    Last I heard, the Windows NT 5.x kernel (2000, XP, 2003) was not even endian-clean any more, let alone portable to RISC or VLIW architectures. Why do you think it's has taken Microsoft so long to port to x86-64 and Itanium?

    Or are Microsoft going to "mandate" that we use x86 processors for all our cluster needs in the future?

  20. Stability by swerk · · Score: 4, Insightful

    Not to fan the flames, but get real. I run a homebrew GNU/Linux box (still a 2.4 kernel, I'm lazy) at home, and XP at work. At work I can get almost a week out of a boot before Windows chokes on itself and needs to restart. At home, the local power grid and my lack of a UPS determines how often I restart.

    Sure, Win2000 and XP are more stable than 95/98 or the travesty that was ME. So it has "come a long way". But let's not be silly and try to call it as stable as GNU/Linux. One crash a week, hell, even if it were once every six months, still seems pretty unstable to me. If that's an "out of touch" point of view, so be it. An OS shouldn't just decide it's had enough and flake out; I don't care how long it's been running.

    Anywho, clustering something even the tiniest bit unstable just seems like a funny idea to me. We've all seen Windows behavior when too much stuff is open or a flaky driver has impaired its ability to operate, things gradually failing, the cursor suddenly trapped in just a portion of the screen, swap thrashing as though it were a sign of the apocolypse... The mental picture of racks and racks full of convulsing, imploding Windows boxen when somebody fires up the wrong version of Quicktime is just priceless.

  21. Windows on a Supercomputer/Mainframe by BigBlockMopar · · Score: 5, Funny

    I love this whole idea of Windows on a supercomputer! Just think of how fast a spam drone it would make!

    Windows only technical asset is a (relatively) good GUI.

    And, as we all know, *ALL* mainframes, supercomputers and servers absolutely must have GUIs!

    After all,

    • GUIs are less resource-intensive than a CLI (but why would you care, having invested millions to get a couple of teraflops, about squeezing every last little drop of power out of it?)
    • GUIs save you time and effort! Rather than a simple shell, Perl, $whatever script to do things, have an operator point-and-click for that human touch!
    • GUIs, by virtue of being based on less code and with less features than a CLI, are inherently more secure. Microsoft, as we know, is the field's foremost expert in security and reliability.

    Memo at Los Alamos Nuclear Laboratory:

    "Please be advised that Deep Blue will be rebooted this afternoon at 5:PM in order to complete the installation of Service Pack 11. All jobs currently running and queued will be lost, even those which have already accumulated several years of processor time. We expect Deep Blue to resume normal operation sometime in early August. Thank you for your cooperation, LANL Informatics Department"

    --
    Fire and Meat. Yummy.
  22. Re:Why are you... by stiggle · · Score: 4, Informative

    More info (for the Google-less) and Links....

    Top 500 - http://www.top500.org/
    Cornell - http://www.tc.cornell.edu/
    NEC Earth Simulator -
    http://www.es.jamstec.go.jp/esc/eng/ESC/index.h tml

    The fastest is the Earth Simulator in Japan (35860/40960 Rmax/Rpeak)
    Virginia Tech as the fastest Apple cluster (as mentioned on /. previously) (10280/17600)
    Cornell has the fastest Windows cluster (1503/3073)

    As for the other questions - Google is your friend and the database on www.top500.org is searchable so should be able to answer anything else.

  23. Re:Linux crashes, too. by ameoba · · Score: 4, Insightful

    a) Why bother building a cluster out of "old & weird" hardware? If you're going to build a cluster you're going to make damned sure that your hardware is suppored and compatable.

    b) WTF would you put a sound card in a cluster?

    --
    my sig's at the bottom of the page.