Summary

Those WT performance tests (recently migrated to Evergreen CI system) currently run for every single commit merged into the main (develop) branch. We should consider lowering the running frequency as most of the commits have a very limited impact on performance, and running performance tests is relatively costly than running other types of tests. 

Motivation

Does this affect any team outside of WT?

No.

How likely is it that this use case or problem will occur?

It affects testing efficiency.

If the problem does occur, what are the consequences and how severe are they?

N/A

Is this issue urgent?

No
Acceptance Criteria (Definition of Done)

Have a lowered running frequency for WT performance tests in place, and save infrastructure cost. 

Testing

WT Performance tests.
Documentation update

N/A

[Optional] Suggested Solution

Is there any suggested solution to handle this issue? Is it related to any existing WT ticket? Is it related to any previous issue fixed? If yes, link the WT ticket number using related to, depends on, dependent on by links