Gubb, David, Holmes, Violeta, Kureshi, Ibad, Liang, Shuo and James, Yvonne (2012) Implementing a Condor pool using a Green-IT policy. In: Digital Research 2012, 10-12 September 2012, Oxford, UK.
High Throughput Computing (HTC) systems are designed to utilise available resources on a network of idle machines in an institution or organization by cycle stealing. It provides an additional ‘free’ resource from the existing computing and networking infrastructure for modelling and simulation requiring a large number of small jobs, such as applications from biology, chemistry, physics, and digital signal processing. At the University of Huddersfield, there are thousands of idle laboratory machines that could be used to run serial/parallel jobs by cycle stealing. Our HTC system, implemented in Condor , is part of the Queensgate Campus Grid (QGG)  that consists of a number of dedicated departmental and university computer clusters.
Condor is an excellent HTC tool that excels in cycle stealing and job scheduling on idle machines. However, only idle powered machines can be used from a networked pool. Many organizations deploy power saving mechanisms to try to reduce energy consumption in their systems, and power down idle resources, using rigid and inflexible power management policies. The University of Huddersfield Computing Services use the Energy Star EZ GPO power saving tool that runs as a Windows service and detects how long the computer has been idle. Then it allows the computer to first turn off the screen and then go into hibernation.
Our research and development work is focused on implementing a HTC system using Condor to work within a “green IT” policy of a higher education institutions that conform to green IT challenges for a multi-platform, multi-discipline user/ resource base. This system will allow Condor to turn on machines that may have gone to sleep due to lack of usage when there is a large queue of pending jobs. The decision to utilise dormant resources will be made on a variety of factors such as job priority, job requirements, user priority, time of day, flocking options, queue conditions etc. Good practice scheduling policies would need to be devised that would work within this “green IT” pool.
Item control for Repository Staff only: