This is a simple fork of par2cmdline which replaces core computation routines with ParPar’s processing backend, improving par2cmdline’s performance on x86/ARM platforms.
The original par2cmdline README can be found here, which covers more info including build and usage instructions.
par2cmdline-turbo aims to keep close with its upstream and only differs in the following areas related to performance. As such, the scope of this project covers:
- GF16, MD5 and CRC32 computation, using ParPar’s implementation
- Use ParPar’s internal checksumming to detect RAM errors during GF16 computation
- Adopts ParPar’s stitched hashing approach
Note that this fork isn’t intended to change too much of par2cmdline itself and hence, is not aimed at fixing bugs or functionality improvements. Bug reports and feature requests should be directed at the upstream project where relevant. The minimalistic nature of this project also means that there’s some degree of performance left on the table, and there’s no focus on improving PAR1 performance.
Note that par2cmdline-turbo may use slightly more memory than par2cmdline, due to increased buffering in ParPar’s backend.
par2cmdline-turbo removes par2cmdline's OpenMP dependency, replacing it with C++11's threads. This change enables fully static builds, as a number of environments can only dynamically link to the OpenMP runtime.
This does have a flow on effect that the -t/-T flags and libpar2’s threads related parameters will be present and work, regardless of OpenMP presence (in par2cmdline, these would differ depending on whether OpenMP support was compiled in).
I know of two other forks to par2cmdline: par2cmdline-tbb and phpar2, both of which focus on performance (like this fork). Key changes of those forks, over the original upstream par2cmdline, from what I can gather:
par2cmdline-tbb
- adds multi-threading via TBB
- adds MMX optimized routines for GF16 computation (from phpar2)
- adds support for concurrency during creation/verification/repair
- adds experimental CUDA (GPU) support
- async I/O
- only available on x86 platforms, due to use of Intel TBB and x86 assembly
phpar2
- adds multi-threading
- adds MMX optimized routines for GF16 computation
- assembly optimized MD5 routine
- only available on x86 Windows platforms, due to use of x86 assembly and Windows API reliance
par2cmdline-turbo differences:
- the above forks were based off the original par2cmdline (0.4?), whereas this fork is based off (at time of writing) the latest ‘mainline’ fork (0.8.1 with unreleased changes)
- faster GF16 techniques, taking advantage of modern SIMD extensions, are used instead of MMX
- faster CRC32 implementations
- uses stitched MD5+CRC32 hashing
- accelerates matrix inversion
- does not add support for async I/O, though it might get some due to the async nature of ParPar’s GF16 backend
- does not add GPU computation (but ParPar has elementary OpenCL support, so might arrive in the future)
- optimizations for ARM and RISC-V CPUs
- cross-platform support
Some speed comparisons posted by others:
- PAR2 create
- PAR2 create (v0.9.0)
- PAR2 verification/repair (multiple machines/OSes)
ParPar is a from-scratch PAR2 implementation, different from par2cmdline, but only focuses on PAR2 creation.
Key reasons to use par2cmdline-turbo over ParPar:
- drop-in par2cmdline replacement
- par2cmdline supports verification and repair, where ParPar does not
Key reasons to use ParPar over par2cmdline-turbo:
- par2cmdline-turbo doesn’t implement all performance optimisations in ParPar, such as async I/O, streaming hash computation etc
- features unique to ParPar, such as auto-slice size scaling
- currently ParPar is more actively maintained than par2cmdline; changes common to these two projects will first be made in ParPar before being ported to par2cmdline-turbo
Pre-built binaries for common systems are available on the releases page.
- Relatively recent compilers are recommended to take advantage of recent SIMD support (e.g. MSVC >=2019, GCC >=10)
- ParPar backend requires C++11 support
See original README for build instructions.
If you have an issue, please test with the original par2cmdline. If the issue is present there, please report it to the par2cmdline repository. Only report issues specific to par2cmdline-turbo here.
Similarly, questions and pull requests should also be directed to the par2cmdline repository, unless it specifically relates to par2cmdline-turbo.