Add speed regression database to doctesting

[roed314]

Currently there's no systematic way of detecting whether a change to the sage library drastically slows down some function (perhaps even the function that's being updated in a ticket).

This ticket aims to add features to the new doctesting code at #12415 that provide the option to run doctests in a mode where they add timing data to a database.

Apply attachment: 12720.patch

Apply attachment: 12720_script.patch to the script repo

CC: @videlec @koffie @embray @roed314

Component: doctest framework

Issue created by migration from https://trac.sagemath.org/ticket/12720

[jhpalmieri]

comment:1

Could monitoring Sage's startup time be incorporated into this?

[roed314]

Changed dependencies from #12415 to #13278

[roed314]

Still very much in progress

[roed314]

Attachment: 12720.patch.gz

[roed314]

comment:3

Attachment: 12720_script.patch.gz

[roed314]

comment:4

Now that #12415 is in Sage, I'll be working on this some. It will probably be at least a few weeks though (I'm going to be working on p-adics and the git transition first).

In the mean time, I've updated the patches to apply against #12415 (actually, rebased against #13278). There's still a lot to be done to make them work well.

[videlec]

comment:10

Hello,

just cc'ing me!

[jdemeyer]

Changed dependencies from #13278 to #24655

[saraedum]

comment:13

roed, I believe that this should probably be closed. The approach of rolling our own system for doing something that asv does very well is probably not appropriate anymore. What do you think?

[jdemeyer]

comment:14

Duplicate of #25262

[jdemeyer]

Changed dependencies from #24655 to none