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

OADP 1.3 Performance & Scale

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Normal Normal
    • OADP 1.3.0
    • None
    • Documentation
    • None
    • False
    • Hide

      None

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

      Overall the majority of CSI and Restic flows showed comparable performance with the previous OADP 1.2, including Velero Builtin DataMover

      The main performance-related difference for Datamover in 1.2 vs 1.3: concurrency limited to the number of workers for VBDM - known limitation.

      Kopia in general performed slightly better than Restic in regards to backup duration.

      Kopia, a new plugin for 1.3, showed reduced time for subsequent backups, following initial backup.

      Largest PV backup and restore tested: pv of 4TB of which 3TB was utilized, completed successfully with  Kopia, Restic, and CSI 

      Max number of pods in single namespace tested for backup/restore: 5000 pods completed successfully with Kopia, Restic and CSI

      Max number of namespaces tested in a single backup and single restore: 200 namespaces totaling: 800 pods using Kopia plugin.

      Validated Nodeagent & Velero resource recommendations using Kopia, Restic, and CSI, including native datamover flows.

      Over 8 weeks of testing:  More than 34,000 pods, PVs, 24TB+ of data successfully backed up, and restored, including native data-mover and Kopia.

      For more details, see https://docs.google.com/document/d/1eXbMLiCzPK1coYZeHm8_rOXo6kUF93d-IhUuMUxTxPA/edit#heading=h.d2lscd8e3s3s
       
       
       

            richard.hoch Richard Hoch
            rhn-support-anarnold A Arnold
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: