Backstory

• On analyzing the summary and reports for the following scenario :
  Concurrency: 20
  Namespace: 3/4/5/6/7
  TEST_TOTAL: 140/105/84/70/60 (Changing TEST_TOTAL to keep consistent PR count)
  Data points: https://docs.google.com/spreadsheets/d/1LgxoN2j5VImw9sfOhO6gpZ6eckD7UTtrOQreMyZWnNo/edit?gid=1451515775#gid=1451515775
• We found that the trend for the resolution request is not linear and needs a few more analyses and data points to understand the behavior of the feature.(ie) While scaling the namespace its not responding as expected 

Acceptance Criteria 

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

• • Increase Namespace : 8/10/15/20
• Add those data in the report 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.