GNU Astronomy Utilities - Tasks: task #14779, Enable usage in HTCondor at...
You are not allowed to post comments on this tracker with your current authentication level.
task #14779: Enable usage in HTCondor at configure time
Submitter: | Mohammad Akhlaghi <makhlaghi> | ||
Submitted: | Wed 20 Dec 2017 11:08:19 PM UTC | ||
Should Start On: | Tue 19 Dec 2017 11:00:00 PM UTC | Should be Finished on: | Tue 19 Dec 2017 11:00:00 PM UTC |
Category: | Installation | Priority: | 5 - Normal |
Item Group: | Enhancement | Status: | Postponed |
Privacy: | Public | Assigned to: | None |
Percent Complete: | 0% | Open/Closed: | Open |
Effort: | 0.00 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-02a9.
Corresponding source code
From its webpage: "HTCondor is a specialized workload management system for compute-intensive jobs. Like other full-featured batch systems, HTCondor provides a job queueing mechanism, scheduling policy, priority scheme, resource monitoring, and resource management. Users submit their serial or parallel jobs to HTCondor, HTCondor places them into a queue, chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion."
In its standard universe, HTCondor will create checkpoints, to migrate a (partially complete) job from one system to another when necessary and thus not needing to redo the job. It also allows "remote system calls". The latter is great in efficiency, because in practice it will trick a program on one machine to use the resources of another system without knowing it (very good for processing efficiency).
However, to benefit from these features of this "standard universe", a program should be compiled with the `condor_compile' command to re-link it with HTCondor libraries (see the description for examples). Some special features (all of which, if present, are optional in Gnuastro)) like `mmap' are not allowed and libraries must be statically linked.
All these HTCondor requirements to allow usage in a "standard universe" can easily be implemented in Gnuastro with a configure time option. For example `--enable-htcondor'. When configured with this option, the compiled Gnuastro executables can benefit from these great features.
This can include BuildProgram, so even programs that the user defines themselves using the Gnuastro Library can be run with the features of the "Standard universe".