Story (Required)

• Test "signing-tr-tekton-bigbang" scenario with total=2500/5000/7500, concurrency=100
• Create a set of graphs like in https://docs.google.com/document/d/1h-MIqHYIlsaHQjNqm-a4jiodeUWusiNp07gKpJATyaY/edit?usp=sharing
• Create a CI job for all 4 configurations
  • Default
  • HA setup
  • Fine Tuning QBT (Queries, Burst, Threads)
  • HA + QBT
• Create various CI jobs for both 1.19 and 1.20 versions and compare the data

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 are running cleanly in the continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) can proceed with new code included
• Customer-facing documentation, API docs, etc., are produced/updated, reviewed, and published
• Acceptance criteria are met