Repository navigation
v1.6.1 — concurrent batches
Concurrent batch processing
Batches previously ran one awaited round trip per file, so a folder of images spent nearly all its wall time with an idle connection. They now run with up to -j/--jobs requests in flight (default 4), across both the image and PDF paths.
Output still reports in submission order, not completion order — a finished job waits in its slot until everything submitted before it has printed, so mochify *.jpg > list.txt and a piped find behave exactly as before.
- One job per (file, variant): a prompt that answers a single file with two formats now overlaps the same way two files do.
-j 1restores strictly sequential processing.MochifyClientis cloneable, so every request in a batch reuses one connection pool.
Measured on 6 images → webp: 1.20s → 0.66s.
Install
cargo install mochifyOr grab a binary below — macOS (arm64/x86_64), Linux (arm64/x86_64, static musl), Windows (x86_64).
Full changelog: v1.6.0...v1.6.1