[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-bug
Subject:    Re: New suggestion to make Lily pond speed up on multiple CPU cores
From:       Jean Abou Samra <jean () abou-samra ! fr>
Date:       2022-07-17 14:03:50
Message-ID: 1b4906e1-86e6-f726-1234-ded3194e30ca () abou-samra ! fr
[Download RAW message or body]

Le 15/07/2022 à 19:10, Arno Waschk a écrit :
> Hi Jean,
>
> thanks for your reply!
> I was aware of what you demonstrate and elaborate on line breaking, 
> but i tried to stick for pagebreaks in my statement for those very 
> reasons.



Umm, if you replace \break with \pageBreak in my example, you will
see that exactly the same problem exists with page breaks.

\version "2.23.11"

\paper {
   ragged-right = ##t
}

{
   c'1\<
   \pageBreak
   c'1\!
}

\pageBreak

{
   c'1\<
   \pageBreak
   c'2 2\!
}



> I could have added that i mean fixed pagebreaks like when stated 
> explicitely by \pagebreak, or an equivalent a more or maybe even less 
> clever algo could add for speed up in some kind of draft mode, which 
> maybe useful even if suboptimal.


It's not hard in each case to find some suboptimal value;
you'd need to ensure, however, that an error does not ensue.

I haven't tried it to see if it was hard.


>
> Probably you have a valid point about POSIX threads. Given that it 
> could not be solved by an equivalent of "make -j 8" and glueing things 
> together (which could be a quite quick and not too dirty solution 
> btw), we had at least something for non-windows users. :-)
>
> Hopefully someone with more insight could comment on that?
>
> Last not least, as anything happended around the gsoc idea, is there 
> any code for it?

I don't think anyone took it.



_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

[prev in list] [next in list] [prev in thread] [next in thread]