home.social

#distcc — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #distcc, aggregated by home.social.

  1. I still remember the time #DistCC and #CCache was installed on all my computers so I could compile faster..

    #Gentoo #Linux #Compile #DIY

  2. I still remember the time #DistCC and #CCache was installed on all my computers so I could compile faster..

    #Gentoo #Linux #Compile #DIY

  3. I still remember the time #DistCC and #CCache was installed on all my computers so I could compile faster..

    #Gentoo #Linux #Compile #DIY

  4. I still remember the time #DistCC and #CCache was installed on all my computers so I could compile faster..

    #Gentoo #Linux #Compile #DIY

  5. I still remember the time #DistCC and #CCache was installed on all my computers so I could compile faster..

    #Gentoo #Linux #Compile #DIY

  6. Thought my old PC was looking lonely, decided to turn it into a distcc build server for Portage and my other compilation needs. Resulted in a noticeable speed boost.

    For older/unused hardware, Linux is the gift that keeps on giving. :tux:

  7. Thought my old PC was looking lonely, decided to turn it into a distcc build server for Portage and my other compilation needs. Resulted in a noticeable speed boost.

    For older/unused hardware, Linux is the gift that keeps on giving. :tux:

    #Linux #SelfHosting #programming #distcc #compilation #Gentoo

  8. Thought my old PC was looking lonely, decided to turn it into a distcc build server for Portage and my other compilation needs. Resulted in a noticeable speed boost.

    For older/unused hardware, Linux is the gift that keeps on giving. :tux:

    #Linux #SelfHosting #programming #distcc #compilation #Gentoo

  9. Thought my old PC was looking lonely, decided to turn it into a distcc build server for Portage and my other compilation needs. Resulted in a noticeable speed boost.

    For older/unused hardware, Linux is the gift that keeps on giving. :tux:

    #Linux #SelfHosting #programming #distcc #compilation #Gentoo

  10. Thought my old PC was looking lonely, decided to turn it into a distcc build server for Portage and my other compilation needs. Resulted in a noticeable speed boost.

    For older/unused hardware, Linux is the gift that keeps on giving. :tux:

    #Linux #SelfHosting #programming #distcc #compilation #Gentoo

  11. Pains of needing to use an older computer to work...

    I am installing #distcc in my #android tablet so I can compile without needing to restart the computer because of freezes.

    Fun times.

    If you are wondering, this PC is a Inspiron 5421 (Modified to have an SSD and more RAM) and my tablet is a Samsung SM-P620.

    Oh, and I also using tethering because the wifi does not support 5Ghz.

    Man, I miss my other PC.

  12. So, distcc lets you compile C or C++ applications on machines (or nodes) over the network, sharing the workload. But for the life of me I can't make it work from within a distrobox on the Steam Deck.

    So I tried icecream (icecc), which is made by the SuSE folks. Not only does it work with distrobox, but it requires less configuration (just enable some systemd services or run the daemon) and everything Just Works. Having three machines + compiling projects with the --parallel flag should make even Qt compile quickly.

    #c #cpp #cplusplus #distcc #distrobox #icecc #suse

  13. So, distcc lets you compile C or C++ applications on machines (or nodes) over the network, sharing the workload. But for the life of me I can't make it work from within a distrobox on the Steam Deck.

    So I tried icecream (icecc), which is made by the SuSE folks. Not only does it work with distrobox, but it requires less configuration (just enable some systemd services or run the daemon) and everything Just Works. Having three machines + compiling projects with the --parallel flag should make even Qt compile quickly.

    #c #cpp #cplusplus #distcc #distrobox #icecc #suse

  14. So, distcc lets you compile C or C++ applications on machines (or nodes) over the network, sharing the workload. But for the life of me I can't make it work from within a distrobox on the Steam Deck.

    So I tried icecream (icecc), which is made by the SuSE folks. Not only does it work with distrobox, but it requires less configuration (just enable some systemd services or run the daemon) and everything Just Works. Having three machines + compiling projects with the --parallel flag should make even Qt compile quickly.

    #c #cpp #cplusplus #distcc #distrobox #icecc #suse

  15. So, distcc lets you compile C or C++ applications on machines (or nodes) over the network, sharing the workload. But for the life of me I can't make it work from within a distrobox on the Steam Deck.

    So I tried icecream (icecc), which is made by the SuSE folks. Not only does it work with distrobox, but it requires less configuration (just enable some systemd services or run the daemon) and everything Just Works. Having three machines + compiling projects with the --parallel flag should make even Qt compile quickly.

    #c #cpp #cplusplus #distcc #distrobox #icecc #suse

  16. What I imagined would happen: I enable #DistCC on my weak laptop, it will pour compilation jobs on my Ryzen PC like crazy, keeping all 12 threads on boost 100% busy and finish webkit-gtk in no time.

    What actually happened: the 4 laptop cores are 100% busy preprocessing and can't keep up delivering jobs to the Ryzen, and it is eating through them so fast it's barely busy.

    Well, at least preprocessing doesn't take as much memory as the compiler, so things are actually progressing rather than getting stuck on swapping.

    #Gentoo

  17. What I imagined would happen: I enable #DistCC on my weak laptop, it will pour compilation jobs on my Ryzen PC like crazy, keeping all 12 threads on boost 100% busy and finish webkit-gtk in no time.

    What actually happened: the 4 laptop cores are 100% busy preprocessing and can't keep up delivering jobs to the Ryzen, and it is eating through them so fast it's barely busy.

    Well, at least preprocessing doesn't take as much memory as the compiler, so things are actually progressing rather than getting stuck on swapping.

    #Gentoo

  18. What I imagined would happen: I enable #DistCC on my weak laptop, it will pour compilation jobs on my Ryzen PC like crazy, keeping all 12 threads on boost 100% busy and finish webkit-gtk in no time.

    What actually happened: the 4 laptop cores are 100% busy preprocessing and can't keep up delivering jobs to the Ryzen, and it is eating through them so fast it's barely busy.

    Well, at least preprocessing doesn't take as much memory as the compiler, so things are actually progressing rather than getting stuck on swapping.

    #Gentoo

  19. What I imagined would happen: I enable #DistCC on my weak laptop, it will pour compilation jobs on my Ryzen PC like crazy, keeping all 12 threads on boost 100% busy and finish webkit-gtk in no time.

    What actually happened: the 4 laptop cores are 100% busy preprocessing and can't keep up delivering jobs to the Ryzen, and it is eating through them so fast it's barely busy.

    Well, at least preprocessing doesn't take as much memory as the compiler, so things are actually progressing rather than getting stuck on swapping.

    #Gentoo

  20. What I imagined would happen: I enable #DistCC on my weak laptop, it will pour compilation jobs on my Ryzen PC like crazy, keeping all 12 threads on boost 100% busy and finish webkit-gtk in no time.

    What actually happened: the 4 laptop cores are 100% busy preprocessing and can't keep up delivering jobs to the Ryzen, and it is eating through them so fast it's barely busy.

    Well, at least preprocessing doesn't take as much memory as the compiler, so things are actually progressing rather than getting stuck on swapping.

    #Gentoo

  21. Jak sobie to wyobrażałem: włączę #DistCC na cienkim lapku, zasypie stacjonarnego Ryzena kompilacjami, utrzymując 12 wątków z boostem na 100% obciążeniu, i skończy kompilować webkit-gtk w chwilę.

    Jak wyszło w praktyce: 4 rdzenie laptopa są w 100% obciążone preprocesorem i nie wyrabiają z dostarczaniem zadań Ryzenowi, a ten je wykonuje tak szybko, że ledwie jest obciążony.

    No cóż, przynajmniej preprocesor nie zużywa tak dużo pamięci jak pełna kompilacja, więc budowanie cały czas postępuje, zamiast zaciąć się na swapowaniu.

    #Gentoo

  22. Jak sobie to wyobrażałem: włączę #DistCC na cienkim lapku, zasypie stacjonarnego Ryzena kompilacjami, utrzymując 12 wątków z boostem na 100% obciążeniu, i skończy kompilować webkit-gtk w chwilę.

    Jak wyszło w praktyce: 4 rdzenie laptopa są w 100% obciążone preprocesorem i nie wyrabiają z dostarczaniem zadań Ryzenowi, a ten je wykonuje tak szybko, że ledwie jest obciążony.

    No cóż, przynajmniej preprocesor nie zużywa tak dużo pamięci jak pełna kompilacja, więc budowanie cały czas postępuje, zamiast zaciąć się na swapowaniu.

    #Gentoo

  23. Jak sobie to wyobrażałem: włączę #DistCC na cienkim lapku, zasypie stacjonarnego Ryzena kompilacjami, utrzymując 12 wątków z boostem na 100% obciążeniu, i skończy kompilować webkit-gtk w chwilę.

    Jak wyszło w praktyce: 4 rdzenie laptopa są w 100% obciążone preprocesorem i nie wyrabiają z dostarczaniem zadań Ryzenowi, a ten je wykonuje tak szybko, że ledwie jest obciążony.

    No cóż, przynajmniej preprocesor nie zużywa tak dużo pamięci jak pełna kompilacja, więc budowanie cały czas postępuje, zamiast zaciąć się na swapowaniu.

    #Gentoo

  24. Jak sobie to wyobrażałem: włączę #DistCC na cienkim lapku, zasypie stacjonarnego Ryzena kompilacjami, utrzymując 12 wątków z boostem na 100% obciążeniu, i skończy kompilować webkit-gtk w chwilę.

    Jak wyszło w praktyce: 4 rdzenie laptopa są w 100% obciążone preprocesorem i nie wyrabiają z dostarczaniem zadań Ryzenowi, a ten je wykonuje tak szybko, że ledwie jest obciążony.

    No cóż, przynajmniej preprocesor nie zużywa tak dużo pamięci jak pełna kompilacja, więc budowanie cały czas postępuje, zamiast zaciąć się na swapowaniu.

    #Gentoo

  25. Jak sobie to wyobrażałem: włączę #DistCC na cienkim lapku, zasypie stacjonarnego Ryzena kompilacjami, utrzymując 12 wątków z boostem na 100% obciążeniu, i skończy kompilować webkit-gtk w chwilę.

    Jak wyszło w praktyce: 4 rdzenie laptopa są w 100% obciążone preprocesorem i nie wyrabiają z dostarczaniem zadań Ryzenowi, a ten je wykonuje tak szybko, że ledwie jest obciążony.

    No cóż, przynajmniej preprocesor nie zużywa tak dużo pamięci jak pełna kompilacja, więc budowanie cały czas postępuje, zamiast zaciąć się na swapowaniu.

    #Gentoo

  26. To speed up software upgrades on my dated :gentoo: laptop, I finally installed (distributed C/C++ compilation) on a more powerful machine in the network (was easy with Docker).

    I'm impressed how much big this difference this makes. Much quicker than expected, I can actually use the laptop during updating, _and_ I don't get random compilation errors due to hardware overheating.

  27. To speed up software upgrades on my dated #gentoo :gentoo: laptop, I finally installed #distcc (distributed C/C++ compilation) on a more powerful machine in the network (was easy with Docker).

    I'm impressed how much big this difference this makes. Much quicker than expected, I can actually use the laptop during updating, _and_ I don't get random compilation errors due to hardware overheating.

  28. To speed up software upgrades on my dated #gentoo :gentoo: laptop, I finally installed #distcc (distributed C/C++ compilation) on a more powerful machine in the network (was easy with Docker).

    I'm impressed how much big this difference this makes. Much quicker than expected, I can actually use the laptop during updating, _and_ I don't get random compilation errors due to hardware overheating.

  29. To speed up software upgrades on my dated #gentoo :gentoo: laptop, I finally installed #distcc (distributed C/C++ compilation) on a more powerful machine in the network (was easy with Docker).

    I'm impressed how much big this difference this makes. Much quicker than expected, I can actually use the laptop during updating, _and_ I don't get random compilation errors due to hardware overheating.

  30. To speed up software upgrades on my dated #gentoo :gentoo: laptop, I finally installed #distcc (distributed C/C++ compilation) on a more powerful machine in the network (was easy with Docker).

    I'm impressed how much big this difference this makes. Much quicker than expected, I can actually use the laptop during updating, _and_ I don't get random compilation errors due to hardware overheating.

  31. Welp, I tried to get #distcc working with #scons, but it never seemed to pick it up. I guess I'll have to try another day.

  32. Welp, I tried to get #distcc working with #scons, but it never seemed to pick it up. I guess I'll have to try another day.

  33. Welp, I tried to get #distcc working with #scons, but it never seemed to pick it up. I guess I'll have to try another day.