-
-
Notifications
You must be signed in to change notification settings - Fork 50
Performance testing #37
Copy link
Copy link
Open
Labels
buildRelated to CI systems, website or testing.Related to CI systems, website or testing.help wanted
Metadata
Metadata
Assignees
Labels
buildRelated to CI systems, website or testing.Related to CI systems, website or testing.help wanted
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