On Fri, 10 Aug 2007, William Stein wrote:
>> An automated test could then be written to pick up on things that
>> significantly slow down between releases. For example, maybe when sage
>> -test is run, it can be supplied with timing data from a previous run,
>> and produce warnings if anything is slower that it used to be.
>
> I think doing this, but with the doctests (as David Harvey I think suggested)
> might work better, since they are already written and are regularly
> maintained.
Sorry, I don't think I meant to say that profiles should be done using
already existing doctest code. I think the kind of things we want to
profile are quite different from the kind of things we want to run tests
on. For example I want to know how fast Integer creation is, or basic
arithmetic on GF(p) for small p, etc.
david
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
