Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-5127

[Scale] Baseline Node-agent Concurrency

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Scale&Perf-QE
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • ToDo
    • 0
    • 0.000
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown
    • None

      Lets identify the optimal number of node-agent's to use.

      per https://velero.io/docs/v1.14/node-agent-concurrency/   Node agent concurrency can be set globally or per node.

      Its your call if you want to assign r640s vs r650's differently but in general the aim is to identify the impact of concurrent node-agents and how many to user per resource expectations.

              dvaanunu@redhat.com David Vaanunu
              mlehrer@redhat.com Mordechai Lehrer
              Mordechai Lehrer Mordechai Lehrer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: