On Wed, Mar 2, 2016 at 7:09 AM, Misja <[email protected]> wrote: > Dear All, > > I've been having some issues with Sage's new_subspace() function. Mainly, it > seems to be very, very slow. > > For example, in the following example > > C=ModularForms(DirichletGroup(10)[1],13).cuspidal_subspace(); > > N=C.new_subspace(); > > The second line takes about 28 s to run on my laptop. In magma the answer is > almost instantaneous. What is going on here?
My guess: Sage used to be similar in speed to Magma for such things (exactly the above was what I used to optimize everything around), and slowly people made little tweaks and changes to linear algebra (and maybe modular symbols, but probably not) until Sage became much, much slower. Also, how you build Sage could matter a lot. All it takes is changing one default algorithm choice of parameter to potentially dramatically slow things down. People often get excited by "rewrite this using that", then the benchmark everything for their own applications (which maybe have nothing to do with modular forms), and it's all over. -- William > > -- > You received this message because you are subscribed to the Google Groups > "sage-support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/sage-support. > For more options, visit https://groups.google.com/d/optout. -- William (http://wstein.org) -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
