Apple Releases Xgrid Technology Preview 2
dark_lotus writes "Apple has announced the availability of Xgrid Technology Preview 2. This version improves on Xgrid's breakthrough ease-of-use by adding the most requested features, including an 'xgrid' command-line utility, support for MPI jobs, and a comprehensive Xgrid User's Guide, as well as numerous bug fixes. Groovy!"
I hope apple does to grid computing what they did to local subnet computing. Rendezvous is an awesome technology for finding people nearby, or doing any simple/quick home networking.
- tristan
When you can use xgrid and enable any type of grid enabled program that might use Rendevous and some simple plug in of some kind to use however many Macs there are on a given network to crunch away at something is the day Apple will start making serious inroads again. Imagine a Photoshop Mac pool at a Ad agency using Xgrid, or the same thing at the movie making place with Final Cut Pro 5 or whatever.
I really do like the directions that Apple is going in these days. Stock market does not seem to mind either. :)
That's been doable in 3ds Max for almost eight years now. The same for Lightwave, even back to the days when it was Amiga only. The software license for 3ds Max allows you to install it in a render-only mode on an unlimited # of machines. One machine acts as the queue manager and people can submit jobs all day long for submission to the renderfarm. The queue manager can maintain a time/date access list for individual machines and add/remove them from the pool as necessary.
XGrid is an extremely interesting project, but it's not designed to take on a dedicated, custom-designed cluster like VT's Big Mac.
Some calculations can be split into pieces that don't require much "talk" with other pieces. For example, Apple's Mandelbrot demo--you don't need to know what's running on other processors.
OTOH, many problems require quite a bit of cross-talk with other processors. For example, most of the quantum chemistry calculations I run require calculating big integrals. These are run across multi-proc boxes or clusters, but the speedup depends a *lot* on the latency of the network. So XGrid won't really help here--most of the ad-hoc networks serviced by XGrid would have something like 100MBs Ethernet, which is slow.
I'm willing to put up $$ to use supercomputing centers like VT's Big Mac because they're *designed* to handle hard-core parallel number-crunching. Right now, I'm running jobs on a 24-proc POWER3 cluster with 4GB RAM per processor. (Yes, the extra RAM really helps too since I don't hit the hard drive much.)
I think XGrid will see a lot of use for academic or corporate environments to allow adhoc clustering. As an example, I can run some calcs on an XGrid "cluster" at night on all of the desktop Macs in a lab or across an office. These won't be anywhere near as fast as a well-designed cluster. But it will give me access to "untapped" CPU cycles.