On my AMD Ryzen R7 2700X, unxz of a ~260MiB unstable .img.xz takes 30s. In comparison, unxz -T0 of the same ~260MiB unstable .img.xz takes 4s.
According to the xz release notes, multithreaded compression has been supported since xz version 5.2.0, which was released in 2014.
xz 5.2.2 was added to the Solus repos in October 2016, so all Solus installs since then would have supported multi-threaded decompression, making the addition of the -T0 flag in solbuild guaranteed to work on existing systems.
The end result is a nicer user experience when updating solbuild images.
On my AMD Ryzen R7 2700X, unxz of a ~260MiB unstable .img.xz takes 30s. In comparison, unxz -T0 of the same ~260MiB unstable .img.xz takes 4s.
According to the xz release notes, multithreaded compression has been supported since xz version 5.2.0, which was released in 2014.
xz 5.2.2 was added to the Solus repos in October 2016, so all Solus installs since then would have supported multi-threaded decompression, making the addition of the -T0 flag in solbuild guaranteed to work on existing systems.
The end result is a nicer user experience when updating solbuild images.