Re: waf default number of jobs

2020-10-05 Thread Sebastian Huber
On 03/10/2020 08:37, Chris Johns wrote: On 2/10/20 5:53 am, Joel Sherrill wrote: On Thu, Oct 1, 2020 at 2:39 PM Sebastian Huber mailto:sebastian.hu...@embedded-brains.de>> wrote: On 01/10/2020 20:09, Joel Sherrill wrote: > What was the rationale behind the choice of the default for

Re: waf default number of jobs

2020-10-02 Thread Chris Johns
On 2/10/20 5:53 am, Joel Sherrill wrote: > On Thu, Oct 1, 2020 at 2:39 PM Sebastian Huber > > > wrote: > > On 01/10/2020 20:09, Joel Sherrill wrote: > > > What was the rationale behind the choice of the default for the number > > of jobs for

Re: waf default number of jobs

2020-10-01 Thread Sebastian Huber
On 01/10/2020 21:53, Joel Sherrill wrote: + make -j24 real    1m53.064s user    7m14.675s sys     1m45.913s . + ./waf -j 24 real    1m1.404s user    0m9.601s sys     0m1.547s Notice how the build time for waf is 50 seconds faster but that doesn't match the user and system time. Perhaps t

Re: waf default number of jobs

2020-10-01 Thread Joel Sherrill
On Thu, Oct 1, 2020 at 2:39 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 01/10/2020 20:09, Joel Sherrill wrote: > > > What was the rationale behind the choice of the default for the number > > of jobs for the waf build system? > I don't know. It is the default behaviour of

Re: waf default number of jobs

2020-10-01 Thread Sebastian Huber
On 01/10/2020 20:09, Joel Sherrill wrote: What was the rationale behind the choice of the default for the number of jobs for the waf build system? I don't know. It is the default behaviour of waf. I noticed also scalability problems but had no time to track them down. It could be also a limita