These are chat archives for bluescarni/piranha

15th
Feb 2016
Francesco Biscani
@bluescarni
Feb 15 2016 09:09
@isuruf are you around?
Isuru Fernando
@isuruf
Feb 15 2016 09:57
yes
Francesco Biscani
@bluescarni
Feb 15 2016 09:59
I was wondering why appveyor builds pushes to a PR twice https://ci.appveyor.com/project/bluescarni/piranha/history
Isuru Fernando
@isuruf
Feb 15 2016 09:59
The top job is the PR.
Second one is the push to the branch
Francesco Biscani
@bluescarni
Feb 15 2016 10:00
is there a way to have a setup in which the pushes to a PR are not considered?
I think travis is setup to build only once: https://travis-ci.org/bluescarni/piranha/builds
Isuru Fernando
@isuruf
Feb 15 2016 10:01
Travis too does the same
Francesco Biscani
@bluescarni
Feb 15 2016 10:03
ah ok maybe I am missing something from the travis summary
it seems a bit wasteful though
Isuru Fernando
@isuruf
Feb 15 2016 10:03
In travis, builds tab and pull requests tab show the 2 builds
Francesco Biscani
@bluescarni
Feb 15 2016 10:03
yeah I just noticed, cheers
I'll keep it as it is then :)
I also meant to ask if you have anything similar to the ASV setup but for symengine instead of sympy?
Isuru Fernando
@isuruf
Feb 15 2016 10:05
No, haven't setup something similar
Francesco Biscani
@bluescarni
Feb 15 2016 10:05
I was about to start hacking something together to track performance but I'd rather not duplicate efforts
ok... basically I was thinking of building a very simple tool that maintains a database of historical performance tests and can output to a javascript webpage with plots made with plotly
just as a "fun" side project really
I was thinking of using TinyDB as a simple json file database and gitpython to interact with GIT repos via python
I just got bitten by a performance bug in Piranha that could have been easily detectable if such a tool had been employed
Isuru Fernando
@isuruf
Feb 15 2016 10:08
You mean like using the same computer and tools, and keeping a history?
history over time
Francesco Biscani
@bluescarni
Feb 15 2016 10:09
exactly
I'd like to populate the database with the performance of previous commits
let's say going back 6 months or so
on various machines
then just run it manually on new PR's let's say before merging, or something like that
and host the report webpage on github pages
you would have some API that allows you to run a perf test on a specific commit and record the results in the database, tracking machine, date, OS, etc.
something like add_benchmark('fateman1_perf',args='--threads=8',commit='399s9s00dad0aa')
even without the Javascript graphing goodies it would be good to have such a database