[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: scheme night-mare...
From: |
Carl Sorensen |
Subject: |
Re: scheme night-mare... |
Date: |
Mon, 12 Jul 2010 07:02:26 -0600 |
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.
I'm not sure what the fix might be.
Carl
- Re: scheme night-mare..., (continued)
Re: scheme night-mare..., Arno Waschk, 2010/07/12
- Re: scheme night-mare...,
Carl Sorensen <=
- Re: scheme night-mare..., Arno Waschk, 2010/07/12
- Re: scheme night-mare..., Joe Neeman, 2010/07/12
- Re: scheme night-mare..., Arno Waschk, 2010/07/12
- Re: scheme night-mare..., Joe Neeman, 2010/07/12
- Re: scheme night-mare..., Neil Puttock, 2010/07/13
- Re: scheme night-mare..., Joe Neeman, 2010/07/13
- Re: scheme night-mare..., Arno Waschk, 2010/07/14
- Re: scheme night-mare..., Arno Waschk, 2010/07/14
- Re: scheme night-mare..., Joe Neeman, 2010/07/14
- Re: scheme night-mare..., Arno Waschk, 2010/07/14