| 1 |
Michael <confabulate@××××××××.com> writes: |
| 2 |
|
| 3 |
> On Saturday, 26 February 2022 22:47:52 GMT Ramces Tampo-og Red wrote: |
| 4 |
> |
| 5 |
>> Yeah, I was just thinking about that since building a powerful, new |
| 6 |
>> computer around my area is prohibitively expensive. But getting old, |
| 7 |
>> prebuilt computers is ludicrously cheap. I figured that I can get a few |
| 8 |
>> of them for $50-75 and just plug them to an ethernet switch to do the |
| 9 |
>> compiling for me. |
| 10 |
> |
| 11 |
> Distributed compiling may not be as useful as you think. Not all phases of a |
| 12 |
> build can be distributed, pre-processing and linking will still take a lot of |
| 13 |
> time, some packages will not compile over distcc and will fail, any gains in |
| 14 |
> compiling time could be eaten away by network losses, etc. On the other hand |
| 15 |
> a 'better' PC with more RAM and a faster CPU with more cores could prove |
| 16 |
> transformative in its performance impact, when used as a building server for |
| 17 |
> binary packages to be installed thereafter on slower systems. |
| 18 |
> |
| 19 |
> I have found older PCs with limited resources eventually reach an EOL as far |
| 20 |
> as their capability to emerge large packages. I have a very old Core 2 Duo |
| 21 |
> Pentium laptop with 4G RAM, which even with MAKEOPTS="-j1" takes forever to |
| 22 |
> build qtwebengine: |
| 23 |
> |
| 24 |
> genlop -t dev-qt/qtwebengine |
| 25 |
> |
| 26 |
> Fri Feb 4 20:06:46 2022 >>> dev-qt/qtwebengine-5.15.2_p20211216 |
| 27 |
> merge time: 1 day, 3 hours, 12 minutes and 7 seconds. |
| 28 |
> |
| 29 |
> Chromium got so slow over the years, I stopped emerging it long ago. |
| 30 |
> |
| 31 |
> Give distcc a go if you have a spare PC to experiment and want to test % |
| 32 |
> improvements with your setup, but personally I wouldn't invest money on it. |
| 33 |
> Instead I'd save up for a faster machine. YMMV. |
| 34 |
|
| 35 |
That sucks. I'll try it out but I guess there's no way out on building a |
| 36 |
proper rig that can handle the compile jobs. |
| 37 |
|
| 38 |
Though to be honest, I've been compiling all of my stuff in both my X200 |
| 39 |
and T400 laptops and both are Core 2 Duo machines. The only real issue |
| 40 |
that I've had with those is with compiling Qtwebengine which took around |
| 41 |
12-14 hours. Other than that the compile times are negligible enough |
| 42 |
that I don't really notice it that much. |
| 43 |
|
| 44 |
Either way, thanks for the heads up. |
| 45 |
|
| 46 |
Cheers! |
| 47 |
|
| 48 |
-- |
| 49 |
|----Give them an inch and they will take a mile.----| |
| 50 |
|----------------------------------------------------| |
| 51 |
|---------{gopher,gemini}://kalayaan.xyz-------------| |
| 52 |
|-C4AE 5D53 46A0 01DF 6E92 CB46 92D7 9FBB AB9F 3E37-| |
Archives