• This software is owned by The university of California, Irvine, and is not distributed under any version of the GPL. GPL is a fine series of licenses, but the owners of the software need it to be distributed under these terms.
  • IQS is essentially two things:
    1. IQS is an implicit queuing system, in the sense that users do not have to explicitly submit jobs to a queue with commands like qsub or llsubmit.
    2. IQS is a sort of portable ultrabatch scheduling class, in the sense that processes are still managed by your operating system's usual scheduler, but IQS adds an additional layer of scheduling overtop of that, which is extremely coarse-grained (subject to how you configure IQS).
  • How IQS functions:
  • Paths of note:
  • Relevant signals (alphabetically):
  • Command line options:
  • Here's an xload -update 1 graph showing what impact IQS has on CPU load. More specifically, this graph was made as I fired up 5: processes, to intentionally pound a Solaris system's single CPU. As you can see, the load starts at zero, zooms up to 4, and then slowly tapers back down to a steady 1. This is because it takes IQS a while to notice new CPU hungry processes, and I started all five of them at nearly the same moment. The load comes down to one, because I started IQS with -n 1, meaning "run only one process concurrently". The unusual slope of this curve, I believe, is not because of IQS or the while loops, but likely due to an oddity of the Solaris kernel load computation.
  • Download it here
  • Kinds of interactive processes that IQS tends to try to manage that it probably shouldn't in many cases
  • Supported Operating Systems:


    Hits: 5962
    Timestamp: 2024-02-26 15:41:43 PST

    Back to Dan's tech tidbits

    You can e-mail the author with questions or comments: