Performance testing

[Murphydbuffalo]

Let's find out if any of the API calls are slow, and if so, why? Are indexes being used as we expect? Are many rows being scanned? Important to have these API calls be fast, engineers won't adopt the product if it slows down their apps.

Prior to private beta we can just poke around manually in Postman and make sure that things are reasonably fast. But prior to the public beta (as our database starts to accumulate more rows) we'll want a higher degree of confidence in the performance of the API.

• [ ] Staging environment
• [ ] Script to generate lots of data
• [ ] Script to make lots of concurrent requests to the API

[Murphydbuffalo]

Might be useful to use something like siege to see how performance looks if we batter production with a ton of API calls

[Murphydbuffalo]

Try out: does read performance improve if we include all the fields we SELECT off of the Variant model during assignment? Those are id, name, num_conversions, num_interactions. So we'd be adding 4 extra fields. Does this hurt write performance?