There are some dedicated backup tools that successfully run multiple threads, but lots more that just split the workload by directory at a high level. Whats New Features Compare Specs Unzip all major formats With just a click, open all major compression formats, including Zip, Zipx, RAR, 7z, TAR, GZIP, VHD, XZ, POSIX TAR and more. The module TrueVFS Kernel modules features federating, multithreading, multiplexing. There was a hack for Solaris Tar for use on ZFS: new TFile(archive.zip).cprp(new TFile()). I'm not sure of any actual parallel archivers that are mainstream. Its similar to cp -pdr, though both cpio and (especially) tar have more. Pass-through: This is basically both of the above, akin to tar -pc tar -px but in a single command (and therefore microscopically faster).
Tar xz multithreaded archive#
Copy-in: This is for archive extraction, akin to tar -px. This is done using the -I argument to tar, which tells tar what program to use to. Copy-out: This is for archive creation, akin to tar -pc. It does so by specifying the arguments to be passed to the xz subprocess, which compresses the tar archive.
The meaningful question becomes, what does the output from a parallel archive look like? It's no longer just a single file descriptor / stdout, but a file descriptor per thread.Īn example of this so far is the parallel dump mode of Postgresql pg_dump, wherein it dumps to a directory, with threads working over the set of tables to back up (work queue w/ multiple threads consuming the queue). tar -c -I 'xz -9 -T0' -f list of files and folders This compresses a list of files and directories into an.
If the source material is coming from a filesystem where different directories/files might be on different disks, or even a single fast disk that exceeds the input speed of the compression tool(s), then could indeed be beneficial to have multiple streams of input going into the compression layers. The OP asked about parallel archiving, not parallel compression.
0 kommentar(er)
