Tagged: torque

Update on Transition to Torque/Maui

Posted on September 1, 2009 at 9:18 am

ChargerNet Cluster Users:

This is a reminder that we are transitioning away from the Condor Job Scheduler to the Torque/Maui Scheduling system.  We have been running both systems for most of the summer in order to allow sufficient time for you to learn the new commands and update your submission scripts and procedures.  We have now moved most of our compute nodes into Torque/Maui and we plan to complete the transition and retire Condor on September 15th.

read more »

Transition to Torque/Maui

Posted on June 22, 2009 at 10:04 am

ChargerNet Users:

We are beginning to transition from the Condor Job Scheduler that we have used in the cluster since its inception in 2005 to the Torque/Maui Scheduling system which has become the predominate scheduler for academic HPC environments.  This change will allow us to take better advantage of tools and techniques developed at other universities, provide better integration with commercial products which support Torque/Maui for parallel processing (like MatLab), and improve our queue management by implementing resource limits or “fair share” algorithms. read more »

Job Scheduling with Torque

Posted on May 18, 2009 at 11:37 am

Introduction

As part of URC’s efforts to provide users with a more user-friendly and efficient environment, we are in the process of transitioning our job scheduler from Condor to Torque/Maui.  Torque is an Open Source scheduler based on the old PBS scheduler code. read more »


About Us


University Research Computing (URC) is one of several support groups within Information & Technology Services (ITS). Our mission is to support the unique computing needs of UNC Charlotte's diverse community of research faculty by developing shared computing facilities and offering specialized services that would be difficult for individual research groups or departments to provide internally.


Cluster Queues

urc: 160 cores (21 busy, 139 free)
% used 13%
URC Stats
mees: 96 cores (16 busy, 80 free)
% used 16%
URC Stats
mees10: 96 cores (80 busy, 16 free)
% used 83%
URC Stats
wrf: 16 cores (2 busy, 14 free)
% used 12%
URC Stats