The longest part of any update from AUR with yay is this one:
-> Compressing package...
htop tells me this is when yay is using the xz tool to compress the package. I was thinking that you could replace xz with pigz, which has feature parity with xz, but is multithreaded and therefore much faster. It won't negatively affect speed on single core or dual core machines. I tried to replace the xz binary myself, but yay seemed to have problems with that, so I was hoping if you could look into replacing it within the application. Thanks!
Okay so I made a mistake. My bad.
That's makepkg's job and you can configure it yourself: https://wiki.archlinux.org/index.php/Makepkg#Utilizing_multiple_cores_on_compression.
Just what I was looking for, thanks!
-------- Original Message --------
On Jan 21, 2019, 9:22 PM, Anna wrote:
That's makepkg's job and you can configure it yourself: https://wiki.archlinux.org/index.php/Makepkg#Utilizing_multiple_cores_on_compression.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
Most helpful comment
That's makepkg's job and you can configure it yourself: https://wiki.archlinux.org/index.php/Makepkg#Utilizing_multiple_cores_on_compression.