hugin-devs team mailing list archive

[Tim Haynes <ubuntu@xxxxxxxxxxxxxxxxxxxxxxxxxx>]

If that were true, why bother offering parallel execution at all?

I regularly create batches of maybe a dozen jobs, for various permutations of scene, crop, enfuse or enblend, with or without LDR normalization, etc, normally with output sizes of 40-50 megapixels. 
The fact of nona and other utilities being multithreaded is not relevant; each spawned process as a whole alternates between long periods of CPU or disk, during which time another job (or two) could happily be using the other resource.
Running them in series is an inefficient waste of time; running them *all* in parallel at once is obviously impossible.

What I'd like is to take this functionality:

panobulk () {
        nt="$1"
        [ -z "$nt" ] && nt=2
        find . -name '*.pto' | while read i
        do
                pto2mk -o "$i.mk" -p "$i:t:r" "$i"
                echo "zsh -c '(cd \"$i:h\" && taskset -a -c 0-3  make -f \"$i:t.mk\" ; make -f \"$i:t.mk\" clean )'"
        done | nice parallel -j "$nt"
}

and stick it in the PTBatcherGUI by means of a concurrent-job-limit
number beside the parallel execution checkbox, for all to enjoy.

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1404849

Title:
  PTBatcherGUI parallel execution limit to N threads

Status in Hugin - Panorama Tools GUI:
  Triaged

Bug description:
  Currently, PTBatcherGUI has a checkbox for parallel execution (or
  not). For reasons of efficient resource utilization, please could we
  have the ability to run up-to-N jobs (default 2 or 3, maybe)
  simultaneously?

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1404849/+subscriptions