- 
    Type:Task 
- 
    Resolution: Unresolved
- 
    Priority:Unknown 
- 
    None
- 
    Affects Version/s: None
- 
    Component/s: Infrastructure, Performance Benchmarking
- 
    None
- 
        Python Drivers
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
Context
Our current performance tests run up to once a day, but only when a commit is merged into master. This is the supported workflow by Evergreen's performance metrics we use (Trend charts), but means that if no commits are merged to master for a given period, no performance tests will be automatically run during that period. Another downside to this is that test inconsistencies are more pronounced with less frequent runs.
Definition of done
Determine the work required and benefit gained from automatic daily performance tests. Sandbox this spike to one day or less.
Pitfalls
The Evergreen performance metrics we use do not support such a daily workflow. We will need to either come up with our own method of recording results or hack together something else. This is likely the biggest obstacle to making a production version of this spike worthwhile.