Changes between Version 15 and Version 24 of Ticket #25262


Ignore:
Timestamp:
08/17/18 14:26:17 (4 years ago)
Author:
saraedum
Comment:

Btw., the naming of the benchmarks is a bit unfortunate currently as you can only see the module and the method name but not the class which makes it a bit hard to track down which __init__ exactly saw a regression.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #25262

    • Property Branch changed from to u/saraedum/25262
    • Property Commit changed from to f7f3847b26048b3b5f437731230d8dd2ade93eae
  • Ticket #25262 – Description

    v15 v24  
    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.~~ We could have specially named methods, say starting in `_benchmark_time_…` that are automatically tracked by CI on the develop branch.
     1I am currently playing with airspeed velocity to track speed regressions in Sage. I would like to benchmark every doctest that has a "long time" marker in it and also benchmark every method that has a `time_` prefix (probably only in some benchmark module.)
    22
    3 We have this set up for https://github.com/MCLF/mclf/tree/master/mclf/benchmarks now. There are only two benchmarks but it works nicely.
     3We have something similar set up for https://github.com/MCLF/mclf/tree/master/mclf/benchmarks now. There are only two benchmarks but it works nicely.
    44
    5 A more interesting demo that is not related to Sage is here: https://pv.github.io/numpy-bench/#/regressions
     5I ran the above proposal for all the tags from 8.3.beta0 to 8.3. There's a lot of noise (because there was other activity on the machine) but you get the idea: https://saraedum.github.io/sage/
     6
     7Another interesting demo of airspeedvelocity that is not related to Sage is here: https://pv.github.io/numpy-bench/#/regressions