Xgrid Agent for Unix
mac-diddy writes "Someone on Apple's mailing list for Xgrid, Apple's clustering software, just announced an 'Xgrid agent for Linux and other Unix platforms' available for download. There are still some issues being worked on like large file support, but it does allow you to simply add a Unix node to your existing Xgrid cluster. Just goes to show that when companies embrace open standards and code, the world doesn't fall apart."
My company has had experience using XGRID on our G4 notebooks. We always leave XGRID running and when we are at the office it is like having 20-30CPUs available at any given time. Now with Linux, we can have about 300 CPUs available, I just wonder how efficient it really is in the non-osx atmosphere.
Time to find the download.
GroupShares Inc. - A Free Online Investment Community
-------
artlu.net
actually have hetergenous hardware platforms? It would be interesting to see a G5/Xeon/Athlon cluster make the top 10 in speed.
imagine a beo...oh...
Somewhat silly, but wouldn't you incur a bit of overhead mixing machines of different endian-ness? I suppose for non-communication intense algorithms this wouldn't be a big deal.
http://www.masturbateforpeace.com/
This is really great news as it's becoming more popular to add CPU clusters to improve performance. Google is probably not the originator of this type of computing, but they have definately pushed it into the mainstream. Anyone living in NC might want to check out this new cluster going into RTP NC. I wonder if this will be the biggest cluser ever
w s_item&id=159
http://www.rtp.org/index.cfm?fuseaction=in_the_ne
--
9 Gmail invitations availiable
Everything is better clustered...
I have my G4 powerbook, 866 and my 800mHz iMac on my LAN at home.
If I use XGrid on the two, what kind of performace could I use it for day to day?
Faster compiles of applications would be the first thought. Any usefulness, say running photoshop? How about Quake? MAME?
Karma: Chameleon (mostly due to the fact that you come and go).
[iMac] GOOD MORNING
.. That's... nice. So how about some Doom 3 then?
[Me] Good morning, computer. How are you?
[iMac] PRETTY GOOD. I SOLVED A VEXING SCIENTIFIC PROBLEM LAST NIGHT.
[Me] Oh is that so.
[iMac] YEAH. I FOUND A SOLUTION TO THE HEISENBERG-BERTELLSMAN PROTEIN FOLDING DELIMMA.
[Me] Huh.
[iMac] THE ANSWER TURNED OUT TO BE 42.
[Me]
[iMac] OK
How the developers actually benefit from OSS. The way I see it is that these people put the time and effort in to make a great product - which they give away for free.
In this case, Apple, the developer of XGrid, is benefiting because in order to use XGrid you have to buy hardware. Apple sells hardware.
Just goes to show that when companies embrace open standards and code, the world doesn't fall apart.
Don't get me wrong, I support open standards/code, but it doesn't show any such thing if this linux client has only just been released. I bet Apple, and others for that matter, will be watching sales of Mac machines for use in clusters. If they drop because everyone starts using linux PCs, then Apple will probably not try this again.
Alphanos
I wonder how effective this really is for home use? Will the performance improvement on my Powerbook be worth running XGrid on it and firing up a couple older computers (600Mhz IMac, Pentium III 1.0 Ghz) on Linux/OS X and adding them to the cluster. Would 100Mbs Ethernet cut it, what about WLAN?
STOP ROCK VIDEO
But the world hasn't fallen apart using Microsoft either...oops, I said that outloud....
http://jayceecorder.blogspot.com
In the past, as I have moved between jobs, I've written a number of Object->relational mapping tools.
After a while they cease to become fun to write, and you'd rather just get on with writing code that does something instead of infrastructure. By using and contributing to OSS projects, you can use the same code no matter what company you end up at. Because the code is portable it can become part of the package you can offer to a potential employer - they not only get an employee but potentially one that can producive almost right away because they are familiar with the tools they'll be using, with no cost to the company for said tools.
So it makes life easier for you, less re-work. And it makes life easier for employers, as they get richer products sooner. And if the employee becomes really proficient at a widely used OSS project they can write their own way through consulting or training.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
This troll is getting old. MS does not and never did own 40% of Apple. They bought a large chunk of non voting shares in exchange for making IE Apple's default browser. As soon as the 3 year contractual agreement was up, MS sold the shares, and for a decent profit.
Stop thinking of developers as individuals who are trying to sell a product and think of developers as people who work/contract for organisations.
Instead of buying a product that is 95% of what I want I can take a OSS package that is 90% of the way there and pay a developer to customise it to exactly my needs. Now I have a solution that is perfect for my business, maybe given something back to the OSS community. While if I had bought the product I would probably have to change my business to use the product. The company now is also free of licensing and upgrade issues. Also they do not have to worry about the vendor going out of business or introducing a new version with no support for the old version.
If you think of software as tools for business rather than something that a developer trys to sell OSS makes a lot more sense.
Go out and get sailing!
I wouldn't say that - I find it pretty amusing you've been registered at ./ for so long and are still so wrong.
p.s. I know I should reference - how about 'MS owns fuck all anymore' - will this do?
The Mothership
Maybe that's not the right way to look at it. The way I see it is that these people put the time and effort into making great tools, not end product. Now they, and everyone else, are free to use those tools to create great products, which they don't give away for free.
The mistake I see in every Microsoft attack on OSS and the great fallacy behind every purchased white-paper that predicts that OSS will destroy the economy is that writing and selling software is only a very small part of the economy! Most of the economy is involved in creating real, tangible things like cars and planes and food, etc, etc. Most of the economy is not involved in endlessly copying and selling the same pattern of bits.
OSS creates tools that promise to improve the creation of many, many things on this planet and improve the prosperity of all. The only ones threatened by this are those that have made a business of monoplizing ideas. Ideas that are so easy to duplicate or recreate that they are deliberately trying to setup and use the force of law to keep people from producing ideas on their own.
OSS is really a "paradigm shift". This phrase has been used so emptily so many times by senseless marketing droids that it has lost impact over the years. But it is here, it is now, and it is unstoppable. How can they stop it? We have the source!
Is "mac" some guy who works for Apple? Or do you normally refer to companies by their product names?
When will Windows write similar grid tools?
Why does Unix keep suing people?
When will Mac make a Windows box?
Apple is good at writing pretty, easy to use interfaces over complex to configure things. Many of these complex things are written by people who ASSUME the end user has the same skill set as they do. But as we all know... The average computer users is an IDIOT. The average system administrator is usually no better.
Let's face it, some slash-dotters who don't even work as system administrators know more them.
Some households have a mix of computers and one can begin to see the benefits - for example, to halve the video compression time of iMovie when making a DVD.
Considering Apple's ease-of-use for heavyweight *NIX apps this would empower more people to have more computing resources available rather than the big fish out there - schools with low budgets would be able to stretch their capabilities that bit further. And so on.
Can anybody confirm if the linux and unix ports are smp aware?
(I wrote the xgridagent).
As the other poster said, XGrid does not care what the binary does (so it can be smp aware, multi-threaded, whatever). However, the xgridagent itself is not explicitly smp aware, but it is multi-threaded. Each task is started in its own thread and depending on the OS(?) I guess they could spread to other CPUs. The other aspect of the question is "Does the Unix XGrid agent support MPI like Apple's GridAgent for OS X?". It does not and I can't say for sure how difficult it would be to support it. However, since all communication is done via the XGrid protocol, I don't see what would prevent it from being implemented. BUt other things need to be done first.
The most pressing issue is to fix the annoying "large message" issue which makes the agent hang (while it waits forever for the controller to accept more frames). I am convinced it is trivial, I just don't know enough about BEEP to fix it. I am hoping somebody who knows BEEP will take a look at xgridagent-profile.c and fix the xgridagent_SengMSG() function and send me the patch.
Daniel Côté
In the proprietary model the software is becoming worth less and less. 5 years ago run time licenses accounted for over 80% of the income of commercial software provider companies, now you will be lucky to see it account for 40% and it is going down rapidly. The rest being made up of support, training and other services.
However, the cost of producing software is the same, and what is more, it is an upfront cost. You cannot get money for it until after you have paid a programmer to write it.
Open source takes the above to a logical conclusion. As software is becoming relatively worthless (as far as run-time licenses go) you do not lose by giving the software away for free, and if you Open Source it you have available a 90% solution from free software out there before you begin thus cutting down on the production costs.
It is not about "giving stuff away" or people "not paying a cent" to use your software, it is about facilitating an extremely cost effective way for which software companies can provide services to the customer by using open source predecessors, and passing the benefit on to successors.
Web Sig: Eddy Currents
Well, when I develop a piece of software (or hire someone to do it for me), I solve one of my problems. That's the benefit. End of story, really.
.. I write software *to benefit myself only*. I am a capitalist. I fully believe in free markets. I believe people should make as much as they can and get to keep it all. I also believe there's no justification for charging for something that costs nothing to copy, so I don't. It goes against my thinking: the only way something that costs nothing can be charged for is if you have authoritarian government enforcing it (which we do). Charge for service, sure. Charge for installation, sure. Charge for consulting, yup. Charge for the box, the CD, whatever. All of that takes time or materials and I can't "copy" it for the next guy.
For instance, I need a special library for an app. And none of the off-the shelf ones exactly match it. So I write it.
Now, I find out that other people have a similar problem. So I think to myself "well, I already got my ROI, so to speak. I solved my problem. So now I'll put this software out as open source and see what happens".
And people use the software in ways I didn't think of. They give suggestions on how it might be better. A few send in patches. Suddenly my solution is an even better solution, at no cost to me.
On the flip side: I download an open source library. It works okay, but there are some bugs and it needs a little refactoring. It will cost $1000 in labor to fix this library, vs. $5000 to write it from scratch. So I do it and send the patch to the author. The author is happy (free patch), I'm happy ($4000 worth of code for free), and I don't have to re-do my fixes in the next version! I sure wish commercial software worked that way.
A lot of folks make it seem that OSS is a bunch of people working for others, for free, like communists or something. Not true
Of course, you don't have to explain *how* OSS works. Just look and see that it exists and is self-sustaining, that's enough to prove that *something* about it works!
Xgrid is proprietary, closed-source software. I think that hardly counts as "embracing" open-source software. Many other parts of the Macintosh platform are proprietary and closed source as well.
I'm not disputing that Apple released Darwin source code. But before you start cheering, keep in mind that Darwin started out as open source: the CMU Mach kernel and bits and pieces of BSD. And it's not like Apple made a big sacrifice in releasing a kernel that looks and feels like half a dozen other open source kernels.
The other packages require a bit of planning, whereas Xgrid excels at locating nearby resources for pawning off processing tasks. Rendezvous (ZeroConf) is exactly about the need for ad hoc networking. Xgrid extends that to the cluster...
There exists no way of exchanging information without making judgments. --Bene Gesserit Axiom
"Either that or OpenMosix"
Xgrid treats the cluster as one proccessor, while OpenMosix assigns each to thread to a cpu thats not doing muck work.
Facts do not cease to exist because they are ignored. -Aldous Huxley
Well, there's Darwin, their (improved, IMnsHO) version of BSD.
Rendezvous is their (improved) version of ZeroConf.
Safari runs on the KHTML engine. Apple made some improvements and gave them back to the KHTML people, who thanked and praised Apple.
They've worked to improve gcc on PPC-based compilers.
They also provide the standard tools like apache, perl, python, etc etc etc, with OS X. I don't know if they have worked on these specifically, but it wouldn't surprise me in the least.
The Independent: Reverend Spooner Arrested in Friar Tuck Incident - ISIHAC, Historical Headlines