Re: Issue 1211 in lilypond: [PATCH]Optimizations for pure-height approximations. (issue1817045)

[Neil Puttock]

On 20 November 2010 21:50, Graham Percival <address@hidden> wrote:

> 1) is it likely to produce misleading results using the same computer,
> same operating system, same build environment?
> if yes... and if the range of "misleading values" is too large to be
> statistically significant... then fine, let's drop the idea.  If the
> "misleading values" produce a spread of, say, 10%, then it would still
> be useful to catch huge drops in speed.
> if no, then this would be useful for the "make check" stuff.  I think
> this is the more likely option.
>
> 2) is it likely to produce misleading results using the same computer,
> same operating system, but possibly changed build environment?
> if yes, then we'll document that the official regtest times may be misleading.
> if no, then we'll document that the official regtest times are
> generally ok, but occasionally they'll get all wacked out.  I can tell
> people exactly when I've changed the build environment (i.e. new OS,
> or doing a GUB git pull), so we'd know when the results should be
> disregarded.

I'm not sure either way, but if you want to test the waters, here's a patch.

I've done a few test runs, and there doesn't seem to be any
significant change (probably since the weighting between `time' and
`cells' for distance calculation is heavily biased towards the
latter).

Cheers,
Neil

0001-Enable-timing-information-for-regression-testing.patch
Description: Text Data