[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Add a cooperative FS lock to lilypond-book. (issue 555360043 by addr
Re: Add a cooperative FS lock to lilypond-book. (issue 555360043 by address@hidden)
Sat, 07 Mar 2020 07:08:24 -0800
On 2020/03/07 12:39:31, dak wrote:
> Han-Wen Nienhuys <mailto:address@hidden> writes:
> > On Fri, Mar 6, 2020 at 11:18 PM <mailto:address@hidden> wrote:
> >> Sigh. I just noticed that opposed to the patch title, this does
> >> just introduce a file lock for lilypond-book but _also_ changes the
> >> build system such that now almost double the number of allocated
> >> get used. It would be good if different topics weren't conflated
> >> single issues so that it's easier to discuss what one is actually
> >> dealing with and make decisions based on the respective merits of
> >> individual parts.
> >> "It doesn't actually work well as a job control measure in
> >> with parallel Make" should likely have been an indicator of what I
> >> thought I was talking about.
> > Can you tell me what problem you are currently experiencing?
> Harm has a system with memory pressure. That means that he so far has
> only been able to work with
> CPU_COUNT=2 make -j2 doc
CPU_COUNT=3 make -j3 doc
is mostly no problem
> Since now lilypond-doc is no longer serialised, he'd need to reduce to
> CPU_COUNT=1 make -j2 doc
> CPU_COUNT=2 make -j1 doc
Let me check, putting this patch on top of current master, right?
With guile-1 or guile-2?
I've little time atm, thus I'm not sure when I'm able to start