Re: [gentoo-user] distccd offspring

[Jorge Almeida <jjalmeida@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]

On Tue, 17 Dec 2024 at 10:17, netfab <netbox253@netc.eu> wrote:

> Le 17/12/24 à 11:02, Jorge Almeida a tapoté :
> > On Tue, 17 Dec 2024 at 08:18, netfab <netbox253@netc.eu> 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 :
> > -j, --jobs JOBS
> >   Sets  a  limit on the number of jobs that can be accepted
> >   at any time.  By default this is set to *two greater than
> >   the number of CPUs on the machine*, to allow for some processes
> >   being blocked on network IO.  (Daemon mode only.)
>
> I think that the distccd daemon spawns one thread for each potential
> accepted job. In your case, 8+6+2 = 16
>
> In my case, I have 4 cores, and 6 distccd waiting threads.
>
> Do you have 16 threads below the main distccd process ?
>

Actually, I have 18 children of the main  distccd process. But this seems
to be consistent with the part of the manual you cited: 2*8 + 2 (the "8+6"
I mentioned before was the number of cores of both client and server, to go
into MAKEOPTS---as per the Wiki, I think)

This explains the number of children. Why they exist while being idle is a
matter of upstream decision, and I'll live with it.

thanks

Jorge Almeida

[-- Attachment #2: Type: text/html, Size: 1994 bytes --]