Posted by: Anonymous Coward
on November 24, 2005 11:47 AM
A major problem with Condor is that it is NOT OPEN SOURCE!! The source code is not freely available, rather you have to licence it from the UW, and the source will only be made available to you if you can prove that you will build a substantial system on it. My Lab has had experience with it, and we did get the source, only after extensive negotiations.
Another problem with Condor is that their are a few jobs which can really run on Condor. They have to be batch, they have to seek input from an input file.
Another major problem is that it doesnt use the capabilities of the Cluster to it's full potential. What it simply does is just execute a job at the most powerful workstation. and even if the job is multithreaded the entire job is run on a single PC. This is tatamount to just taking the job to the most powerfull computer and take the result. Cluster softwares should break up multithreaded jobs inorder to achieve computational speed up.
All in all Condor is to simplistic, and it would be a poor choice to use it in to setup a cluster.
Problems with Condor
Posted by: Anonymous Coward on November 24, 2005 11:47 AMAnother problem with Condor is that their are a few jobs which can really run on Condor. They have to be batch, they have to seek input from an input file.
Another major problem is that it doesnt use the capabilities of the Cluster to it's full potential. What it simply does is just execute a job at the most powerful workstation. and even if the job is multithreaded the entire job is run on a single PC. This is tatamount to just taking the job to the most powerfull computer and take the result. Cluster softwares should break up multithreaded jobs inorder to achieve computational speed up.
All in all Condor is to simplistic, and it would be a poor choice to use it in to setup a cluster.
#