I have a shiny new server for running simulations on, with a pair of Tesla GPUs and 32 cores, running CentOS 7.2. I'd like for multiple users to be able to submit jobs to the server that get queued up and run when the previous finishes, preferably with some sort of prioritisation system and time limit, like PBS/TORQUE but for a single machine rather than a cluster. I know I can install and configure TORQUE for a single machine, but it seems like overkill - theoretically, the scheduler should only have to run when jobs finish or run overtime. I can probably homebrew a set of scripts, but I was wondering if a solution already exists?

  • 1
    I would suggest just using an existing batch scheduler like PBS or TORQUE. Why hack up a sub-optimal solution of your own when there's already something available that is meant to solve exactly the problem you're trying to solve? Sure, you have a "cluster" of 1, but you're still looking for a job submission and scheduling system. – larsks Feb 5 '16 at 2:06
  • ksh93 comes with this ability builtin in the coshell builtin and the library's cs utility's connect stream services. Its associated userspace 3d filesystem viewpaths really enhance the the usability of such things, in my opinion. – mikeserv Feb 5 '16 at 2:24
  • larsks - I'll see how I go, but I find it hard to believe that no-one else has this problem, so I figured I'd ask. Thanks! @mikeserv - I can't find any documentation for coshell, and when I try to run it in my install of ksh it can't find the command. Could you point me in the right direction? – Yoshanuikabundi Feb 5 '16 at 2:51
  • You need ksh93 - ksh88 will not do. But you might start here. – mikeserv Feb 5 '16 at 2:57
  • @mikeserv - I compiled the beta branch and could get everything to run, but submitting jobs in a test environment with coshell -r localhost /home/yoshanuikabundi/test.sh resulted in a segfault. coshell --man and coshell -h both don't give any useful info. – Yoshanuikabundi Feb 5 '16 at 5:40

Consider TaskSpooler -- http://viric.name/soft/ts/.

It seems to work like 'at' but drops everything into the same sequential queue.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.