Parallel: A Command-line CPU Load Balancer Written in Rust

This is an attempt at recreating the functionality of GNU Parallel, a work-stealer for the command-line, in Rust under a MIT license. The end goal will be to support much of the functionality of GNU Parallel and then to extend the functionality further for the next generation of command-line utilities written in Rust. While functionality is important, with the application being developed in Rust, the goal is to also be as fast and efficient as possible.

See the to-do list for features and improvements that have yet to be done. If you want to contribute, pull requests are welcome. If you have an idea for improvement which isn't listed in the to-do list, feel free to email me and I will consider implementing that idea.

Benchmark Comparison to GNU Parallel

GNU Parallel

~/D/parallel (master) $ seq 1 10000 | time -v parallel echo > /dev/null Command being timed: "parallel echo" User time (seconds): 97.04 System time (seconds): 29.17 Percent of CPU this job got: 232% Elapsed (wall clock) time (h:mm:ss or m:ss): 0:54.17 Average shared text size (kbytes): 0 Average unshared data size (kbytes): 0 Average stack size (kbytes): 0 Average total size (kbytes): 0 Maximum resident set size (kbytes): 66848 Average resident set size (kbytes): 0 Major (requiring I/O) page faults: 0 Minor (reclaiming a frame) page faults: 15070207 Voluntary context switches: 250452 Involuntary context switches: 113320 Swaps: 0 File system inputs: 0 File system outputs: 0 Socket messages sent: 0 Socket messages received: 0 Signals delivered: 0 Page size (bytes): 4096 Exit status: 0

Rust Parallel

~/D/parallel (master) $ seq 1 10000 | time -v target/release/parallel echo > /dev/null Command being timed: "target/release/parallel echo" User time (seconds): 0.48 System time (seconds): 2.48 Percent of CPU this job got: 59% Elapsed (wall clock) time (h:mm:ss or m:ss): 0:04.93 Average shared text size (kbytes): 0 Average unshared data size (kbytes): 0 Average stack size (kbytes): 0 Average total size (kbytes): 0 Maximum resident set size (kbytes): 12928 Average resident set size (kbytes): 0 Major (requiring I/O) page faults: 0 Minor (reclaiming a frame) page faults: 2198164 Voluntary context switches: 73174 Involuntary context switches: 36678 Swaps: 0 File system inputs: 0 File system outputs: 0 Socket messages sent: 0 Socket messages received: 0 Signals delivered: 0 Page size (bytes): 4096 Exit status: 0

Syntax Examples

The following syntax is supported:

sh parallel 'echo {}' ::: * // {} will be replaced with each input found. parallel echo ::: * // If no placeholders are used, it is automatically assumed. parallel echo :::: list1 list2 list3 // Read newline-delimited arguments stored in files. parallel echo ::: arg1 ::::+ list :::+ arg2 // Interchangeably read arguments from the command line and files. parallel echo ::: 1 2 3 ::: A B C ::: D E F // Permutate the inputs. parallel echo {} {1} {2} {3.} ::: 1 2 file.mkv // {N} tokens are replaced by the Nth input argument parallel ::: "echo 1" "echo 2" "echo 3" // If no command is supplied, the input arguments become commands. parallel 'cd {}; echo Directory: {}; echo - {}' // Commands may be chained in the platform\'s shell. ls | parallel 'echo {}' // If no input arguments are supplied, stdin will be read. ls -1 | parallel --pipe cat // Piping arguments to the standard input of the given command.

Manual

Parallel parallelizes otherwise non-parallel command-line tasks. When there are a number of commands that need to be executed, which may be executed in parallel, the Parallel application will evenly distribute tasks to all available CPU cores. There are three basic methods for how commands are supplied:

  1. A COMMAND may be defined, followed by an which denotes that all following arguments will be usde as INPUTS for the command.

  2. If no COMMAND is provided, then the INPUTS will be interpreted as COMMANDS.

  3. If no INPUTS are provided, then standard input will be read for INPUTS.

Parallel groups the standard output and error of each child process so that outputs are printed in the order that they are given, as if the tasks were executed serially in a traditional for loop. In addition, commands are executed in the platform's preferred shell by default, which is sh -c on Unix systems, and cmd /C on Windows. This comes at a performance cost, so it can be disabled with the --no-shell option.

INPUT MODES

Input modes are used to determine whether the following inputs are files that contain inputs or inputs themselves. Files with inputs have each input stored on a separate line, and each line is considered an entire input.When there are multiple collected lists of inputs, each individual input list will be permutated together into a single list.

INPUT TOKENS

COMMANDs are typically formed the same way that you would normally in the shell, only that you will replace your input arguments with placeholder tokens like {}, {.}, {/}, {//} and {/.}. If no tokens are provided, it is inferred that the final argument in the command will be {}. These tokens will perform text manipulation on the inputs to mangle them in the way you like. Ideas for more tokens are welcome.

OPTIONS

Options may also be supplied to the program to change how the program operates:

Useful Examples

Transcoding FLAC music to Opus

ffmpeg is a highly useful application for converting music and videos. However, audio transcoding is limited to a a single core. If you have a large FLAC archive and you wanted to compress it into the efficient Opus codec, it would take forever with the fastest processor to complete, unless you were to take advantage of all cores in your CPU.

sh parallel 'ffmpeg -v 0 -i "{}" -c:a libopus -b:a 128k "{.}.opus"' ::: $(find -type f -name '*.flac')

Transcoding Videos to VP9

VP9 has one glaring flaw in regards to encoding: it can only use about three cores at any given point in time. If you have an eight core processor and a dozen or more episodes of a TV series to transcode, you can use the parallel program to run three jobs at the same time, provided you also have enough memory for that.

sh vp9_params="-c:v libvpx-vp9 -tile-columns 6 -frame-parallel 1 -rc_lookahead 25 -threads 4 -speed 1 -b:v 0 -crf 18" opus_params="-c:a libopus -b:a 128k" parallel -j 3 'ffmpeg -v 0 -i "{}" $vp9_params $opus_params -f webm "{.}.webm"' ::: $(find -type f -name '*.mkv')

Installation Instructions

There are a number of methods that you can use to install the application. I provide binary packages for AMD64 systems that are available for download:

Gentoo

I have a personal Gentoo layman overlay that provides this application for installation.

Arch Linux

A PKGBUILD is available for Arch Linux users from the AUR.

Ubuntu

Debian packages are provided on the releases page. If a release is not available, it's because I haven't built it yet with cargo deb.

Everyone Else

sh wget https://github.com/mmstick/parallel/releases/download/0.6.1/parallel_0.6.1_amd64.tar.xz tar xf parallel_0.6.1.tar.xz sudo install parallel /usr/local/bin

Compiling From Source

All of the dependencies are vendored locally, so it is possible to build the packages without Internet access.

First Method

If you would like to install the latest release directly to ~/.cargo/bin using the official method.

sh cargo install parallel

Second Method

If you would like to install the latest git release:

sh cargo install --git https://github.com/mmstick/parallel parallel

Third Method

If you would like to install it system-wide.

sh wget https://github.com/mmstick/parallel/archive/master.zip unzip master.zip cd parallel-master cargo build --release sudo install target/release/parallel /usr/local/bin