You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Switching of bottlenecks happens since xz compression takes considerable amount of time. We could realise next nar while compressing the previous. More relevant for fixed output paths.
For example, nix copy /nix/store/4x7f05y3zxkaq74mk44jinnxnpx26yri-MafDb.gnomAD.r2.1.hs37d5_3.8.0.tar.gz means compressing 5.8 GiB with slow lzma/xz. Moreover, it's already compressed with zlib/gzip.
Maybe I should consider switching between compression algorithms when the size is such big or the path is already compressed anyway.
The text was updated successfully, but these errors were encountered:
AleXoundOS
changed the title
realise/nix-copy in parallel
realise and nix copy in parallel
Jun 20, 2020
Switching of bottlenecks happens since xz compression takes considerable amount of time. We could realise next nar while compressing the previous. More relevant for fixed output paths.
For example, nix copy /nix/store/4x7f05y3zxkaq74mk44jinnxnpx26yri-MafDb.gnomAD.r2.1.hs37d5_3.8.0.tar.gz means compressing 5.8 GiB with slow lzma/xz. Moreover, it's already compressed with zlib/gzip.
Maybe I should consider switching between compression algorithms when the size is such big or the path is already compressed anyway.
The text was updated successfully, but these errors were encountered: