Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
parallel_rsync [20.05.2020 19:32] – [the code] Pascal Suter | parallel_rsync [20.05.2020 19:39] – [the bash function] Pascal Suter | ||
---|---|---|---|
Line 21: | Line 21: | ||
how many jobs should run in parallel and how many directories deep you want to parallellize your jobs really depends on your sepcific situation. if you have several terabytes of data and you do a complete sync it makes sense to dive deeper into the structure than when you just want to update an already existing copy of the same data, in that case it might be faster to only dive 1 to 2 levels deep into your structure or even not use this script at all, when most of the time is spend by " | how many jobs should run in parallel and how many directories deep you want to parallellize your jobs really depends on your sepcific situation. if you have several terabytes of data and you do a complete sync it makes sense to dive deeper into the structure than when you just want to update an already existing copy of the same data, in that case it might be faster to only dive 1 to 2 levels deep into your structure or even not use this script at all, when most of the time is spend by " | ||
- | ==== known issues ==== | + | in the second version I have added the possibility |
- | * when i wrote the script i used excessive escaping | + | a second filename can be passed optionally as $6. prsync will save its progress |
+ | |||
+ | these two optional options should only be used if the source does not change between prsync runs. It is specially beneficial if the source storage | ||
==== the code ==== | ==== the code ==== | ||