A while back I moaned about the lack of simple Unix schedulers that could go beyond the simple world of cron.

Following on from that, I’ve done some detailed digging into alternatives and options, and figured it might be worth putting up for others to make use of. Don’t expect an opinion on any of them, this is just a list for you to use at your own risk. Opinions and recommendations are my day job when it comes to this sort of thing. Some of them are appropriate for my needs, some of them not up to the job, some of them are over the top. So, in no particular order:

  • Autosys, the often considered de facto option from Computer Associates.
  • Cybermation
  • Cronacle
  • Appworx
  • JP1 from Hitachi.
  • Tidal Software Enterprise Scheduler
  • Control M from BMC
  • Condor from the University of Wisconsin. Getting into High Throughput and Parallel Computing here, but still relevant.
  • PBS Pro based on Open PBS.
  • And, to cap it all, I did hack together some basic scripts to do something very simple Unix dependency management. I’ll make them available here if anybody is interested. Just drop me a mail. I’m playing with the idea of a Sourceforge project, but figured it’s of limited interest right now.

    More on batch schedulers here (Google is your friend), and here.

    3 Responses to “More on simple unix schedulers”

    1. 1
      mark speakman Says:

      Hello

      Stumbled across your site on another search but it touched a nerve. I’ve got a reasonable amount of work unit scheduling and scheduling products experience (have twice assesed new products).
      I have previously come to the conclusion that generally the products on offer are too weighty, complex and expensive and that there is a niche to be filled by a simple (very) low cost no frills product, definately no GUI.
      I have the skills to develop one but have never started for a variety of reasons but the main 2 are:
      I work in a support/development role and tend to like to switch off at the end of a working day and on the occassions I get past this I then assume that the Linux devotees will already have developed one anyway.

      Cheers

      Mark

    2. 2
      Richard Leyton Says:

      I’ve had a few requests for QSBS, so it’s available here:

      http://www.leyton.org/download/qsbs-0.1.tar.gz

      Needless to say: it’s VERY alpha, not complete, and very, well, Quick and Simple (as in not much effort). If you find a use for it, great, but use it at your own risk. For now, it’s distributed under the GNU General Public License, and comes with no warranty (See the README and COPYING files).

      I’m leaving to go travelling in a month or so, but I may start work on something a bit more fully featured later this year, after I return from South-East asia in June/July.

    3. 3
      Jim Kimball Says:

      Richard -

      I have done a lot of work with schedulers over my years and, indeed, have ended up with Autosys everywhere I have worked. Even though it is outrageously expensive, it is also reliable and for this job, we can’t afford to pinch pennies. One of the Windows groups where I currently work had implemented some jobs in an app called 24×7 (http://www.softtreetech.com/24×7). It was simple and cheap but they admitted that it failed/crashed a couple times a week. So we are converting their stuff to Autosys.

      A motivation for my writing to you is that I am also a convert to the Mac for a little over the past year. Our office is investigating alternatives to Solaris machines ($9000 for 2U dual CPU Sparc 240). The current favorite in the systems group is RH Linux ($7500 for dual CPU incl. Server software). I am trying to push dual CPU G5 XServes. The only thing holding me back is Autosys availability. Heaven knows what it will take to move the CA mountain, but thought I’d pass on to you that I am going to try.

    Leave a Reply

    Please be sure to read the comment policy before posting.