Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate performance tests #52

Open
chrisnatali opened this issue May 19, 2015 · 3 comments
Open

Automate performance tests #52

chrisnatali opened this issue May 19, 2015 · 3 comments

Comments

@chrisnatali
Copy link
Contributor

To simplify running and keep track of performance over time

@vr2262
Copy link

vr2262 commented May 19, 2015

If you find a good solution for this, I'm all ears.

@vr2262
Copy link

vr2262 commented May 19, 2015

See travis-ci/travis-ci#3313

@blogle
Copy link
Contributor

blogle commented May 19, 2015

I get that performance is hardware dependent but it seems this could be factored out. Always run a nontrivial baseline algorithm and use its performance to detrend the performance increase of updated hardware and use this to normalize changes in performance on what you are actually testing.

-Ogle

Sent from my iPhone

On May 19, 2015, at 4:59 PM, Viktor Roytman [email protected] wrote:

See travis-ci/travis-ci#3313


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants