Acceptance Criteria

• Run hub resolver scenario for the following profiles (run each for TEST_RESOLVER_TYPE git and task):

• • Increasing Concurrency:
    • TEST_TOTAL: 1000
    • Concurrency: 60/70/80/90/100
    • Namespace: 1 
    • Multi-Step Count: 1
  • Increasing Namespace:
    • Concurrency: 20
    • Namespace: 3/4/5/6/7
    • TEST_TOTAL: 140/105/84/70/60 (Changing TEST_TOTAL to keep consistent PR count)
    • Multi-Step Count: 1
  • Increasing Task Payload Size:
    • TEST_TOTAL: 200
    • Concurrency: 10
    • Namespace: 5
    • Multi-Step Count: 1/5/10/20
• Prepare a report for the above 3 scenarios with the following key metrics:
  • PR/TR durations
  • ResolutionRequest Durations
  • Pipeline Controller Resource Usage (workqueue, cpu, memory, etc)
  • ETCD DB Usage & Request Latency
  • Kube-API server Utilizations (cpu, memory)
• Present the findings to Engineering.