Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • 4
    Tar does not compress. Commented Apr 17, 2019 at 16:30
  • 1
    What will you do with the tar file when you have it. This may affect the answer, as a speed up in one area may slow down another, or vica versa. Commented Apr 17, 2019 at 16:31
  • 2
    The CPU and the number of cores don't make much difference as the operation of creating a tar archive is disk-bound, not CPU-bound. You could use several tar processes running in parallel, each handling their own subset of the files, creating separate archives, but they would still need to fetch all the data from the single disk. Commented Apr 17, 2019 at 16:32
  • @ ctrl-alt-delor after the tar file , i will transfer that with network or just mv to another folder. Commented Apr 17, 2019 at 16:46
  • 1
    @GuoYong the ideal split would be a combination of number of files and aggregate disk usage. If you're looking to copy the files elsewhere to another server why not just use scp and skip the tar phase entirely? Commented Apr 17, 2019 at 17:11