Story (Required)

• Test "timebased-sign-pruner" pipeline with total=1000 and concurrency=60, 70, 80, 90 and 100 with 5 namespace.(ie)https://github.com/openshift-pipelines/performance/tree/main/tests/scaling-pipelines/scenario/timebased-sign-pruner
• Create a set of graphs like in https://docs.google.com/spreadsheets/d/1pKYX694nmXPMbHjpyTD1hU6NmOfFQXGuP6X4Y9ASvNk/edit?usp=sharing
• Create various CI jobs for both 1.19 and 1.20 version 

Background (Required)

<Describes the context or background related to this story>

Out of scope

<Defines what is not included in this story>

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met