This gives a 218MB file and takes 9 minutes and 20 seconds on this hardware. The current system uses xz level 6 compression and forces single threaded operation. Summary (file-level-threads-time) in name: -rw-r-r- 1 me me 1534832640 Feb 18 12:11 ungoogled-chromium_. I had previously done some compression benchmarking and regularly use xz in -0 -threads=0 mode and decided to compare (0 means ‘all cpu cores/threads’ in xz-speak, which is eight threads on this laptop).
ungoogled-chromium_.109.seconds))) seconds | tee secondsįind debian/scripts/ungoogled-chromium/ -name _pycache_ -type d -exec rm -r + Selected GCC installation: /usr/lib64/gcc/x86_64-suse-linux/7Ĭandidate multilib: multilib: and packaging steps OS and version for building: openSUSE Leap 15.0įound candidate GCC installation: /usr/lib64/gcc/x86_64-suse-linux/7.
#TAR XZ MULTITHREADED ARCHIVE#
out/Default archive -o /tmp/download/ungoogled-chromium/build/src/ungoogled_packaging/ungoogled-chromium_.110-1_ -i /tmp/download/ungoogled-chromium/build/src/ungoogled_packaging/README Noticed in KDE System Monitor while this command was running in console, there was only one core at 100%, all others were at 0%. Perhaps some optimization can be made to speed it up (using multiple CPU cores). The final step of building (exporting a tar.xz file) seems to use a single CPU core only.
0 kommentar(er)
