#archlinux-ports | Logs for 2026-03-13
Back
[00:40:49] -!- kitlith_ has joined #archlinux-ports
[00:41:48] -!- kitlith has quit [Ping timeout: 264 seconds]
[00:43:44] -!- kitlith_ has quit [Read error: Connection reset by peer]
[00:51:31] -!- kitlith has joined #archlinux-ports
[04:29:31] -!- hcmb_ has joined #archlinux-ports
[04:29:31] -!- hcmb has quit [Killed (zinc.libera.chat (Nickname regained by services))]
[04:29:31] hcmb_ is now known as hcmb
[07:31:35] <solskogen|M> gromit: can you take a look at mkurz MRs for chromium? :-)
[09:24:58] <gromit> solskogen|M: I'm currently building it on my arm machine, but rather than going with the quite messy approach from the MR I re-added the rollup-patch as it was needed for x86_64 aswell
[09:25:29] <solskogen|M> Great :-)
[09:26:13] <gromit> But man, building on 4 cores instead of 48 is slow af xD
[09:26:38] <solskogen|M> I'd suggest going for 32 or more cores :-)
[09:28:33] <gromit> Yesterday I checked the price of one of those system76 tera beast machines
[09:28:41] <gromit> But 10k is a bit much for my taste :D
[09:29:58] <solskogen|M> cheaper to buy 12 Pi5s and setup a distcc cluster :-)
[10:22:50] <linkmauve> This will also be waaaaaaay slower.
[11:27:24] -!- kitlith has quit [Ping timeout: 264 seconds]
[11:37:14] -!- kitlith has joined #archlinux-ports
[14:15:08] <solskogen|M> linkmauve: not as slow as with only 4 cores
[15:00:15] -!- drathir_tor has quit [Remote host closed the connection]
[15:00:37] -!- drathir_tor has joined #archlinux-ports
[15:33:56] -!- drathir_tor has quit [Remote host closed the connection]
[15:34:16] -!- drathir_tor has joined #archlinux-ports
[16:01:19] -!- coherence42 has joined #archlinux-ports
[16:02:48] -!- cjc7373 has quit [Ping timeout: 264 seconds]
[16:34:20] <linkmauve> Serializing to the network is very slow, I once had access to a 128 cores amd64 monster through distcc, but it was only twice as fast to build Inkscape than my four cores laptop.
[16:36:32] <linkmauve> 8 minutes instead of 20 minutes.
[16:37:40] <linkmauve> Whereas building it directly on the machine took 35s.
[17:32:40] -!- yjun123 has quit [Quit: Konversation terminated!]
[17:34:17] <solskogen|M> I'd say 8min instead of 20 is a big improvement :-)
[17:34:44] <solskogen|M> You can even use distcc together with a cross compiler on a faster host
[17:34:45] <linkmauve> Yes, but the machine is capable of 35s without the overhead of serializing the translation units in both directions through the network.
[17:35:01] -!- yjun123 has joined #archlinux-ports
[17:35:22] <linkmauve> 8 minutes instead of 35s is a very bad disimprovement.
[17:35:34] <solskogen|M> Heh, sure.
[17:36:14] <solskogen|M> With distcc cpp and linking is being done on the slow host.
[18:27:58] -!- cjc7373 has joined #archlinux-ports
[18:28:15] -!- coherence42 has quit [Ping timeout: 246 seconds]
[19:26:54] <phantomas> not in pump mode iirc (at least for cpp)
[19:27:35] <phantomas> linking is done on the host that started the session in both modes
[23:10:13] -!- titus_livius has joined #archlinux-ports