Mailinglist Archive: opensuse (5130 mails)

< Previous Next >
Re: [SLE] RANT: Advantages of Dual Core
  • From: Joachim Schrod <jschrod@xxxxxxx>
  • Date: Tue, 30 May 2006 16:01:51 +0200
  • Message-id: <447C504F.6060009@xxxxxxx>
Per Jessen wrote:
Joachim Schrod wrote:

Orn E. Hansen wrote:
Mánudaginn 29 maí 2006 21:31 skrifaði Per Jessen:
That page is in need of some editing - there is nothing implicitly
sequential about batch-processing - certainly not on a multi-way
machine, but even on a uni-processor, batchjobs maybe executing in
parallel, even if not concurrently.

Batch does imply sequentiality

Having implemented big batch jobs on IBM mainframes, made up from
several thousand job steps, under JCL and under CA7, I can assure you
that this is no the case.

That's what I was trying to say - and when I started it was still
UCC7 :-)

Yes, I agreed with you and wanted to substantiate it.

I think what batch perhaps implies is sequentiality within a job, but a
pile of batchjobs is certainly not sequential by default.

Ah, that's one of the reasons to switch to CA7. There you can define that job steps are independent and can be executed in parallel. Some wizards can even bind that parallelization to resource availability; though that's not my level of expertise.

Bringing this thread back to SUSE and Linux: Anybody knows a good Open Source scheduler/batch system for Linux? batch and cron are a joke, and LSF is (a) expensive and (b) overshoot for single systems. We always start to write own, more or less application-specific, schedulers in Perl, but that's not a real solution. Integration in fail-over cluster environments (i.e., support for jobs on logical hosts that might or might not be active on a physical node) is a must. Utilizing Petri-Net methods (pre- and postconditions of input and output availability for scheduling and parallelization decisions) would be a definitive plus.


Joachim Schrod Email: jschrod@xxxxxxx
Roedermark, Germany

< Previous Next >
Follow Ups