Re: multicore management system
On Fri, Dec 28, 2007 at 06:58:42AM -0600, Ron Johnson wrote:
> On Friday December 28 2007 00:27:24 Jerome BENOIT wrote:
> [snip]
> >
> > I have a long list of jobs that I want to launch on my box.
> > On a one core box, I can make a for loop in order to submit
> > then in sequence. On a multi-core box, this approach does not
> > work anymore. Hence my intention to use Torque: here I envisage
> > my multi-core box as a cluster where each core is a node. Note
> > that you can configure LAM in such a way.
>
> Old school OSs like OS/MVS, DOS/VSE, OpenVMS, MPE, MCP, etc all
> have sophisticated batch queue functionality.
>
> I've never understood why Unix has never received such power.
Because nobody has written it. Ron, I've never run any of those OSs.
AIUI, you had queues: one for heavy IO, one for heavy comp, one for a
mix. The queue manager ran one heavy IO with one heavy comp, but only
one mixed one at a time. IIUC, this would require the
operator/programmer to classify the program as to which queue it should
reside.
Right now, with cron, jobs get done sequentially. If you watch it with
top, at any given point, you could find the system maxing out CPU and IO
being trivial, or the system spent waiting for IO with free comp cycles
available.
It shouldn't be too hard to write program that looked at the current
load and decided which queue to select for the next program to run.
This would take into account running programes not under controll of the
queueing system (eg normal cron runs, other users, etc). Although,
IIRC, on those older OSs, the system was either in multi-user state or
batch state.
Doug.
Reply to: