On Mon, 12 Jul 2010 15:02:26 +0200, Carl Sorensen <address@hidden>
wrote:
> On 7/12/10 4:48 AM, "Arno Waschk" <address@hidden> wrote:
>>> Just finished a profile run with a larger score- ly_scm2interval is
>>> reported to have consumd 16% of computation time. There must be
>>> something wrong.
>>
>> ... which appears in a loop, which is performed >2 billions times (!)
>> for
>> a 18 a3 page test score.
>> Says gprof...
>>
>> Is that possible/necessary?
>
> Well, if it's an 18 page score, then there are lots of page break
> options,
> and so there would be lots of calculations. 2 billion seems like a
lot,
> but there are a lot of ways to figure out line and page breaks in 18
> pages
> of score....
>
> ly_scm2interval is part of the beam scoring code. So that might be
where
> many of the calls come from.
no, from the beam thing it is only called ~1000 tmes, the two billion
come
from a loop in Axis_group_interface::combine_pure_heights (...)