Establish statistically significant and consistent performance tests #8

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

Open

mousetraps opened this issue Jan 17, 2017 · 0 comments

Labels

performance test-infrastructure

Contributor

mousetraps commented Jan 17, 2017

Currently, there is a lot of variance with performance tests - we need to set up an environment where:

we can understand the impact of our work on multiple machine configurations
we can minimize variance between test runs and have higher confidence that a potential performance optimization is actually adding value rather than unnecessarily complicating the codebase
the tests should run continuously so we can detect issues as soon as possible

mousetraps added test-infrastructure performance labels

mousetraps mentioned this issue

How this tool differs to nikic/PHP-Parser #36

Closed

nicolas-grekas mentioned this issue

CPU profiling to identify potential performance improvements #15

Open

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