lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Speed tips, again, for extremely large scores?


From: Graham Percival
Subject: Re: Speed tips, again, for extremely large scores?
Date: Mon, 1 Feb 2010 13:02:06 +0000
User-agent: Mutt/1.5.18 (2008-05-17)

On Mon, Feb 01, 2010 at 12:37:42PM -0000, Trevor Daniels wrote:
>
> Mats Bengtsson wrote Monday, February 01, 2010 11:52 AM
>>
>> Martin Tarenskeen wrote:
>>>
>>> On Mon, 1 Feb 2010, Michael Kappler wrote:
>>>
>>>> I'm also still very interested if there are possibilities to  
>>>> increase LilyPond performance further.
>>>> My machine is very slow, though and I cannot speak for many people 
>>>> when raising performance issues.
>>>
>>> Would it be an idea to create a "Lilypond Benchmark" webpage, small, 
>>> interesting, and useless ;-)
>
> It would be both interesting and a useful check on
> whether code additions to new releases have had an
> effect on processing speed.  Although for this we
> would have to establish one or maybe several standard
> configurations so the tests are directly comparable.

ARGH!  Bloody mao!  (not directed at you, Trevor)

Like **so many** things in lilypond, this was done ages ago.  For
the past few YEARS, the regtests have included this information.

The problem is that it isn't documented anywhere, the output is
hard to read, and I have a sneaky suspicion that part of it is
broken at the moment but would only require a 10-minute bugfix if
the person knew what he was doing.


You want to improve the situation?  There's two options:

1) start reading the sources to figure out how this benchmarking
works.  Figure out what the output means, whether or not it's
currently working, look at old versions to see what it looked like
back then, etc.

2) start helping me with easy stuff (like writing plain text for
the new website), so that *I* can work on #1.  I have the
technical knowledge and persistance required to solve #1, but
given the lack of other people on more critical things, I doubt
I'll start working on it for at least 3 months.

- Graham




reply via email to

[Prev in Thread] Current Thread [Next in Thread]