Implement a cacheless database for testing purposes

[jason-upchurch]

User story

As a developer, I want to be able to use the API to make GET requests while guaranteeing the query is not already cached so that I can benchmark queries and run back-to-back tests to assess the effect of openFEC code-base changes on API performance.

Background

• We have tools like locust test which help assess the effect of random users/inputs and load. This tool is not a good fit for answering the question, "How does this code change affect the performance of a particular query?"
• We use caching (especially in production, but generally in dev and stage as well) to improve performance of subsequent, identical queries

Technical considerations

• what are the advantages of having cache on dev database?
• the current method of waiting 24 hours (or overnight) to conduct an identical query to assess the performance is prohibitive at scale. Can we repurpose dev to remove cache since it's more a testing environment, or if that is not acceptable, can we add a cacheless database for testing?