Create tests to measure performance #42
Description
This is related to #41 but I thought I'd break it out into its own issue as it's a discrete unit of work. Without tests, it's very hard to tell if even a really minor tweak to a regex (or similar) is detrimental to performance. I'm not sure of the best way to do this, but we need even a really rough order of magnitude test suite that can pick up on this sort of thing. The change referenced in the aforementioned issue has hit perf by up to 1000x (33 emails per sec in the 300s report versus 3,091 before the change), so I imagine it won't be hard to detect something that varies perf by that much. Hopefully we can get a more finely tuned measurement model together and even start chipping away further at the best perf stats we've achieved.