You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To enforce our performance goals, we need to create a CI job or modify an existing one which enforces certain performance thresholds.
The e2e job in the github CI is a good first candidate. It allows us to avoid creating another CI job and use the near-real-world runtime environment to look for performance issues. If we find that the overhead of having prometheus running on our e2e tests is too high, we can instead add a new CI job and perhaps make it periodic.
The text was updated successfully, but these errors were encountered:
To enforce our performance goals, we need to create a CI job or modify an existing one which enforces certain performance thresholds.
The e2e job in the github CI is a good first candidate. It allows us to avoid creating another CI job and use the near-real-world runtime environment to look for performance issues. If we find that the overhead of having prometheus running on our e2e tests is too high, we can instead add a new CI job and perhaps make it periodic.
The text was updated successfully, but these errors were encountered: