http://metacentrum-demo.duckdns.org/ 2026-05-24T01:34:10+00:00 http://metacentrum-demo.duckdns.org/ http://metacentrum-demo.duckdns.org/lib/tpl/reskin/images/favicon.ico text/html 2026-04-18T13:14:40+00:00 Anonymous (anonymous@undisclosed.example.com) http://metacentrum-demo.duckdns.org/doku.php?id=en:devel:torque:administration&rev=1776518080&do=diff Administration Environment injection One of the issues we run into with Torque was the need to have machine specific job environment. This would be very impractical to implement into Torque itself, therefore we added generic environment injection using a simple bash script that prints pairs of lines representing environment variable name and value. Creating machine specific job environment is now a simple task of changing this script. text/html 2026-04-18T13:14:40+00:00 Anonymous (anonymous@undisclosed.example.com) http://metacentrum-demo.duckdns.org/doku.php?id=en:devel:torque:resource_mngmnt&rev=1776518080&do=diff Resource Mngmnt Plain Torque has very weak resource semantics and leaves most of resource management logic to the scheduler. This approach suffers from scalability issues and also doesn't allow multiple schedulers on one server, because the scheduler requires exclusive access to the GRID to maintain synchronized GRID state. In our fork, we have moved resource semantics into the server, which now supports static allocation of generic resources and serves as a guard preventing any invalid (over l… text/html 2026-04-18T13:14:40+00:00 Anonymous (anonymous@undisclosed.example.com) http://metacentrum-demo.duckdns.org/doku.php?id=en:devel:torque:start&rev=1776518080&do=diff Torque Batch systems are the core component of GRIDs. Their main task is to manage the life time of computational jobs. Torque batch system consists of three main components: * The server, which serves mostly as a gate-keeper and job and gridstate database and is also responsible for verifying the integrity andcorrectness of all requests. * The scheduler, which is responsible for planning the execution of jobs onto computing nodes. * The mom daemons, which run on each computing node and are re… text/html 2026-04-18T13:14:40+00:00 Anonymous (anonymous@undisclosed.example.com) http://metacentrum-demo.duckdns.org/doku.php?id=en:devel:torque:support&rev=1776518080&do=diff Support One of the long term challenges in our GRID is to communicate as much information about the internal functionality of the GRID as possible. Most common interaction between users and user support are related to jobs that are waiting for execution without any obvious cause for not being executed immediately.