To maximize CPU usage (I run things on a Debian Lenny in EC2) I have a simple script to launch jobs in parallel:
#!/bin/bash
for i in apache-200901*.log; do
Using GNU Parallel will make your script even shorter and possibly more efficient:
parallel 'echo "Processing "{}" ..."; do_something_important {}' ::: apache-*.log
This will run one job per CPU core and continue to do that until all files are processed.
Your solution will basically split the jobs into groups before running. Here 32 jobs in 4 groups:
GNU Parallel instead spawns a new process when one finishes - keeping the CPUs active and thus saving time:
To learn more:
I had to do this recently and ended up with the following solution:
while true; do
wait -n || {
code="$?"
([[ $code = "127" ]] && exit 0 || exit "$code")
break
}
done;
Here's how it works:
wait -n
exits as soon as one of the (potentially many) background jobs exits. It always evaluates to true and the loop goes on until:
127
: the last background job successfully exited. In
that case, we ignore the exit code and exit the sub-shell with code
0.With set -e
, this will guarantee that the script will terminate early and pass through the exit code of any failed background job.
This is my crude solution:
function run_task {
cmd=$1
output=$2
concurency=$3
if [ -f ${output}.done ]; then
# experiment already run
echo "Command already run: $cmd. Found output $output"
return
fi
count=`jobs -p | wc -l`
echo "New active task #$count: $cmd > $output"
$cmd > $output && touch $output.done &
stop=$(($count >= $concurency))
while [ $stop -eq 1 ]; do
echo "Waiting for $count worker threads..."
sleep 1
count=`jobs -p | wc -l`
stop=$(($count > $concurency))
done
}
The idea is to use "jobs" to see how many children are active in the background and wait till this number drops (a child exits). Once a child exists, the next task can be started.
As you can see, there is also a bit of extra logic to avoid running the same experiments/commands multiple times. It does the job for me.. However, this logic could be either skipped or further improved (e.g., check for file creation timestamps, input parameters, etc.).
There's a bash
builtin command for that.
wait [n ...]
Wait for each specified process and return its termination sta‐
tus. Each n may be a process ID or a job specification; if a
job spec is given, all processes in that job’s pipeline are
waited for. If n is not given, all currently active child pro‐
cesses are waited for, and the return status is zero. If n
specifies a non-existent process or job, the return status is
127. Otherwise, the return status is the exit status of the
last process or job waited for.