XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Performance
    • None
    • 2
    • False
    • None
    • False
    • SECFLOWOTL-72 - Baseline various Tekton Controller performance

      Acceptance Criteria

      • Run cluster-resolver scenario for the following profiles (run each for TEST_CLUSTER_RESOLVER__TYPE cluster 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.

            rh-ee-rashetty Rahul Shetty
            rh-ee-rashetty Rahul Shetty
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: