Difference between revisions of "Condor"
| Line 4: | Line 4: | ||
When a computer goes idle, the Condor software will recognize this and look to its queue to see if there are any jobs waiting to be run. If it finds jobs, they are run, while the computer stays idle. When, however, someone comes to and uses the computer, Condor instructs itself to set a checkpoint and stops processing the data. | When a computer goes idle, the Condor software will recognize this and look to its queue to see if there are any jobs waiting to be run. If it finds jobs, they are run, while the computer stays idle. When, however, someone comes to and uses the computer, Condor instructs itself to set a checkpoint and stops processing the data. | ||
| − | + | Condor at NC State is still in developmental stages, but hopefully will be available soon. Both a Windows and Red Hat Linux solution are being developed. More information will be made available as soon as the project nears completion. | |
*[[/Documentation| Documentation]] | *[[/Documentation| Documentation]] | ||
Revision as of 08:15, 30 June 2006
The Condor Project is currently under way within the ECE department. This is an effort to bring the Condor software to NC State. Condor software provides a specialized workload management system for a network of computers, allowing for the unused clock cycles of computers on a network to be exploited.
When a computer goes idle, the Condor software will recognize this and look to its queue to see if there are any jobs waiting to be run. If it finds jobs, they are run, while the computer stays idle. When, however, someone comes to and uses the computer, Condor instructs itself to set a checkpoint and stops processing the data.
Condor at NC State is still in developmental stages, but hopefully will be available soon. Both a Windows and Red Hat Linux solution are being developed. More information will be made available as soon as the project nears completion.