Software:TORQUE

From HandWiki

}}

TORQUE
Developer(s)Adaptive computing
Initial release2003 (2003)
Stable release
7.0 / 27 January 2023; 12 months ago (2023-01-27)
Written inANSI C
Operating systemUnix-like
Size5 MB
Available inEnglish
TypeDistributed resource manager
LicenseProprietary License (As of June 2018),[1] OpenPBS version 2.3[2][3] (non-free in DFSG[4])
Websiteadaptivecomputing.com/cherry-services/torque-resource-manager/

The Terascale Open-source Resource and Queue Manager (TORQUE)[5] is a distributed resource manager providing control over batch jobs and distributed compute nodes. TORQUE can integrate with the non-commercial Maui Cluster Scheduler or the commercial Moab Workload Manager to reduce overall utilization, scheduling and administration on a cluster.

The TORQUE community has extended the original Portable Batch System (PBS) to extend scalability, fault tolerance, and functionality. Contributors include NCSA, OSC, USC, the US DOE, Sandia, PNNL, UB, TeraGrid and other HPC organizations. As of June 2018, TORQUE is no longer open-source even though previously it was described by its developers as open-source software,[1] using the OpenPBS version 2.3 license[2] and as non-free software by the Debian Free Software Guidelines[4] due to license issues.

Feature set

TORQUE provides enhancements over standard OpenPBS in the following areas:

  • Fault Tolerance
    • Additional failure conditions checked/handled.
    • Node health check script support.
  • Scheduling Interface
    • Extended query interface providing the scheduler with additional and more accurate information.
    • Extended control interface allowing the scheduler increased control over job behavior and attributes.
    • Allows the collection of statistics for completed jobs.
  • Scalability
    • Significantly improved server to worker nodes' Machine Oriented Mini-server (MOM) communication model.
    • Ability to handle larger clusters. (over 15 TF/2,500 processors)
    • Ability to handle larger jobs. (over 2000 processors)
    • Ability to support larger server messages.
  • Usability
    • Extensive logging additions.
    • More human readable logging. (i.e. no more "error 15038 on command 42")

See also

References

External links