On Oct 20, 10:44 pm, Simon King <[email protected]> wrote: > Thus, each example of C.all_super_categories() is small, but a single > elliptic curve computation could easily involve thousands of examples.
Have you checked that the elliptic curve computations *use* all_super_categories? I understand that it's there for generic reasons, but if actual code shows that people want to be able to do a little bit of work with polynomials over thousands of different finite fields, perhaps there should be lighter weight option available? Reducing overhead is a lofty goal, but it can't beat removing it (or not introducing it in the first place). Can this attribute be lazy? The whole paradigm of "parents are heavy, elements are light" is only effective if people create relatively few parents and then do a lot with elements of those. It fits with many computer algebra computations, but if in your observation the creation of the parents is a significant part of the runtime for some elliptic curve computations then perhaps a model with different trade-offs would be more appropriate. -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
