On Wed, Nov 18, 2009 at 3:29 PM, Daniel Bump <b...@match.stanford.edu> wrote:
>
>> 3) The time for weyl_characters.py to complete on -long has gone up
>> to 250s or so. I'm not sure if this is due to adding more expensive
>> tests or a speed regression. This currently runs twice as long as
>> any other single file on -long.
>
> The patch #5794 adds a lot of branching rules, and tests are provided
> for most of these. I marked many of them long.
>
>> This is due to #5794, and the looooong tests for all the new
>> cool exceptional types features.
>>
>> Dan: it is recommended for # long time tests to not exceed 30s (see
>> http://www.sagemath.org/doc/developer/conventions.html).
>>
>> Would you have time shortly to go through the # long time tests,
>> annotate them with about how much time they take and, if that exceeds
>> 30s, replace the #long time by #not tested?
>>
>> Otherwise, let me know, and I'll take on the chore.
>
> I won't have time immediately but should be able to get to it
> over the weekend. If that is not soon enough, I don't mind if
> you do it. In case you do, observe the following lines:
>
> sage: E6=WeylCharacterRing("E6",style="coroots") # long time
> sage: D5=WeylCharacterRing("D5",style="coroots") # long time
> sage: fw = E6.fundamental_weights() # long time
> sage: [E6(fw[i]).branch(D5,rule="levi") for i in [1,2,6]] # long time
>
> I think only the last item in this list will be slow. (Actually
> this test takes about 1.99 seconds on one machine.) But unless they
> are involved in some test, there is no need to define the Weyl
> character rings D5 and E6, so the other lines are marked long time too.
>
> As I read the doc, no single test should exceed 30s. But there are
> tests marked "long time". So it is possible that most of them
> are under 30s yet they accumulate to over 250s. Therefore could
> you suggest a target for the entire file to run on with typical
> hardware when testing with -long?
In sage-4.2.1, the top offenders are:
113.5
159.8
161.5
173.1
193.2
200.6
204.1
206.8
So, I suggest a per-file upper bound of 200seconds, though honestly I
would prefer to see 120s.
-- William
--
You received this message because you are subscribed to the Google Groups
"sage-combinat-devel" group.
To post to this group, send email to sage-combinat-de...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sage-combinat-devel?hl=.
