schedule regular performance tests - pipelines

[pritidesai]

Pipeline controller sometimes cause performance issues. It's not easy to identify whether a code change is introducing any delay. With such a wide code base and so many moving pieces, the contributors unknowingly can introduce a bottleneck. We discover such issues when they are reported by the users, such as:

tektoncd/pipeline#3521
tektoncd/pipeline#5420

While troubleshooting these issues, we often have no idea how much time did a unit/integration test took with the last release or a couple of past releases. It will be great if we can start running a performance test nightly or on a certain cadence such that we can capture these numbers in future and graph them when needed.

/kind feature

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[vdemeester]

/lifecycle frozen