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

Performance testing #37

Open
gampleman opened this issue Oct 29, 2018 · 0 comments
Open

Performance testing #37

gampleman opened this issue Oct 29, 2018 · 0 comments
Labels
build Related to CI systems, website or testing. help wanted

Comments

@gampleman
Copy link
Owner

I would like to figure out a way to track performance so that subsequent commits don't backslide the performance gains (at least inadvertently) from micro optimizations like #36. For example reverting the changes made in that PR would be totally reasonable in a code cleanup PR that a reviewer (who doesn't remember why they were made) wouldn't blink twice about.

Originally posted by @gampleman in #36
@gampleman gampleman added help wanted build Related to CI systems, website or testing. labels Oct 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
build Related to CI systems, website or testing. help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gampleman