On Fri, Dec 19, 2008 at 4:07 PM, Craig Citro <craigci...@gmail.com> wrote:
>
>> eisenstein_submodule, sorry I wasn't more specific.
>>
>
> Hmm, interesting. Do you have the log? I'm just surprised that
> anything could cause that file to timeout, especially without causing
> anything else to timeout. Could I con you into running that test
> again, and seeing if it still times out? If it does, could you do it
> with -verbose to see what's taking so long?
When I just built some of the binaries for sage-3.2.2 I had this file
(eisenstein_submodule.py) timeout on two of my build machines after
360 seconds. One is the G5 in Clement's office, and another is a
32-bit Ubuntu virtual machine with 512MB RAM running on my office
computer.
Using --verbose, first, this doctest takes a *long* time (minutes):
z, n =
sage.modular.modform.eisenstein_submodule.cyclotomic_restriction(L,N)###line
401:_sage_ >>> z, n =
sage.modular.modform.eisenstein_submodule.cyclotomic_restriction(L,N)
Expecting nothing
This also takes a very long time:
z =
sage.modular.modform.eisenstein_submodule.cyclotomic_restriction_tower(L,K)###line
478:_sage_ >>> z =
sage.modular.modform.eisenstein_submodule.cyclotomic_restriction_tower(L,K)
So I'm guessing maybe there was a massive performance regression in
cyclotomic_restriction, whatever that is.
-- William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
