Changes between Initial Version and Version 15 of Ticket #25262


Ignore:
Timestamp:
Aug 9, 2018, 12:44:30 AM (4 years ago)
Author:
Julian Rüth
Comment:

Adding this to all doctests is probably hard and would require too much hacking on asv. It's probably best to use the tool as it was intended to be used. Once #24655 is in, I would like to setup a prototype within Sage. Any area that you would like to have benchmarked from the start?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #25262

    • Property Authors changed from to Julian Rüth
    • Property Cc Maarten Derickx Vincent Delecroix added
    • Property Milestone changed from sage-8.3 to sage-8.4
  • Ticket #25262 – Description

    initial v15  
    1 I am currently playing with airspeed velocity to track speed regressions in Sage. For a start I would like to track the runtime of our doctests per method and see if that is already useful information.
     1I am currently playing with airspeed velocity to track speed regressions in Sage. ~~For a start I would like to track the runtime of our doctests per method and see if that is already useful information.~~ We could have specially named methods, say starting in `_benchmark_time_…` that are automatically tracked by CI on the develop branch.
    22
    3 A demo is here: https://pv.github.io/numpy-bench/#/regressions
     3We have this set up for https://github.com/MCLF/mclf/tree/master/mclf/benchmarks now. There are only two benchmarks but it works nicely.
     4
     5A more interesting demo that is not related to Sage is here: https://pv.github.io/numpy-bench/#/regressions