ablu has quit [Read error: Connection reset by peer]
ablu has joined #yocto
zeddii has quit [Ping timeout: 272 seconds]
davidinux has quit [Ping timeout: 260 seconds]
davidinux has joined #yocto
nwhitlock has quit [Ping timeout: 256 seconds]
vthor has joined #yocto
vthor has quit [Changing host]
vthor has joined #yocto
<manuel>
I think a considerable part of a yocto build is compressing/uncompressing stuff. I took for granted that all compression algorithms take advantage of multithreading, but learned that this is not the case.
<manuel>
Did anyone look into speeding up yocto builds by using only MT able compression algorithms?
<manuel>
Guess I'm not the first having that idea
<RP>
manuel: FWIW we try and use multithreaded compression where we can
<RP>
manuel: we have the added fun of wanting to be reproducible too
goliath has joined #yocto
Soopaman has joined #yocto
zeddii has joined #yocto
jmiehe has joined #yocto
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<marex>
manuel: look at e.g. ZSTD_COMPRESSION_LEVEL and ZSTD_THREADS
vthor has quit [Ping timeout: 240 seconds]
vthor has joined #yocto
vthor has quit [Changing host]
vthor has joined #yocto
lexano has joined #yocto
Soopaman has quit [Quit: Leaving.]
xmn has joined #yocto
nerdboy has quit [Remote host closed the connection]
vthor has quit [Quit: kill -9 $pid]
nerdboy has joined #yocto
Saur_Home77 has joined #yocto
vthor has joined #yocto
vthor has quit [Changing host]
vthor has joined #yocto
Saur_Home39 has quit [Ping timeout: 250 seconds]
goliath has quit [Quit: SIGSEGV]
Saur_Home86 has joined #yocto
Saur_Home77 has quit [Ping timeout: 250 seconds]
mjm has quit [Quit: mjm]
amitk has quit [Ping timeout: 260 seconds]
florian__ has joined #yocto
florian__ has quit [Ping timeout: 240 seconds]
vthor has quit [Remote host closed the connection]