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.

Sign up for GitHub

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

Jump to bottom

Add a performance test #94

Open
sebastian-philipp opened this issue Aug 27, 2014 · 1 comment
Open

Add a performance test #94

sebastian-philipp opened this issue Aug 27, 2014 · 1 comment
Milestone
0.4.0.0

Comments

@sebastian-philipp
Copy link
Member

We should add a performance test using criterion to detect bugs like #93 in the future. Mabe we can use travis-ci for executing a performace test that fails, if that takes longer than the last run?
@chrisreu
Copy link
Member

Yes we should do that.

I think, we should use the latest Criterion library for that. It not only tracks running time now but also provides memory statistics.

We could define upper bounds for both runtime and memory usage for specific tests and then let criterion verify that.

@chrisreu chrisreu added this to the 0.3.0.0 milestone Aug 31, 2014
@chrisreu chrisreu modified the milestones: 0.3.0.0, 0.4.0.0 Sep 9, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.4.0.0
Development

No branches or pull requests
2 participants
@sebastian-philipp @chrisreu