On 24 July 2010 07:13, Mike Hansen <mhan...@gmail.com> wrote: > On Fri, Jul 23, 2010 at 11:10 PM, Robert Bradshaw > <rober...@math.washington.edu> wrote: >> We should do this as part of the tests, collect timing data on each >> test block (and perhaps even each line?). There have been vague plans >> to do this for a while, and I thought about waiting for it before >> getting this in, but no one's produced code. > > I think Craig may actually have some code for this. > > --Mike
I created this ticket long ago, but don't know how to go about writing it myself http://trac.sagemath.org/sage_trac/ticket/6808 That was aimed at having a more direct comparison with Mathematica. I agree with Robert, doing something as part of the doctests would be useful. Clearly one would need a way to separate CPU time from wall time. If the CPU time used by a test changes a lot, it should be flagged as a possible source of problem. One could also say the same about memory usage. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
