On Tue, 17 Dec 2024 at 10:17, netfab wrote:
> Le 17/12/24 à 11:02, Jorge Almeida a tapoté :
> > On Tue, 17 Dec 2024 at 08:18, netfab wrote:
> >
> > > Le 16/12/24 à 18:11, Jorge Almeida a tapoté :
> > > > Any distcc user in the same boat?
> > >
> > > Yes. How many CPU cores do you have ?
> > >
>
Le 17/12/24 à 11:02, Jorge Almeida a tapoté :
> On Tue, 17 Dec 2024 at 08:18, netfab wrote:
>
> > Le 16/12/24 à 18:11, Jorge Almeida a tapoté :
> > > Any distcc user in the same boat?
> >
> > Yes. How many CPU cores do you have ?
> >
>
> 8 + 6
Here is my assumption : in man distccd we can read
On Tue, 17 Dec 2024 at 08:34, Alexandru N. Barloiu wrote:
> Not only to save time and resources, but also it's a way for the server
> to be able to report to the client which CPUs are available for
> compilation. It will favour those which are less busy.
>
> On Tue, 2024-12-17 at 16:26 +0800, Wil
On Tue, 17 Dec 2024 at 08:18, netfab wrote:
> Le 16/12/24 à 18:11, Jorge Almeida a tapoté :
> > Any distcc user in the same boat?
>
> Yes. How many CPU cores do you have ?
>
8 + 6
In make.conf:
MAKEOPTS="-j29 -l8"
Not only to save time and resources, but also it's a way for the server
to be able to report to the client which CPUs are available for
compilation. It will favour those which are less busy.
On Tue, 2024-12-17 at 16:26 +0800, William Kenworthy wrote:
> My understanding is that its so there are fr
My understanding is that its so there are free processes ready to go (it
takes time and resources to spawn a new process) ... its normal on my
systems.
BillK
On 17/12/24 01:11, Jorge Almeida wrote:
I have this in the output of "ps axf"
532 ? SN 0:00 \_ /usr/bin/distccd --user
Le 16/12/24 à 18:11, Jorge Almeida a tapoté :
> Any distcc user in the same boat?
Yes. How many CPU cores do you have ?
7 matches
Mail list logo
