Uploaded image for project: 'Cluster Integration and Delivery'
  1. Cluster Integration and Delivery
  2. CLID-255

V2 - Profile memory, cpu, network and disk usage

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • oc-mirror
    • False
    • Hide

      None

      Show
      None
    • False
      • Document all profiling data
      • Collaborate with DOC's team to update current oc-mirror v2 documents
        • Minimum requirements
        • General info (all parameters)
    • ---
    • ---
    • None

      Overview

      Customers have asked about what "minimal" requirements do we need to execute oc-mirror v2, so that they can provision a server accordingly specficically for oc-mirror and also for CI/CD scenarios

       

      Goal

      Use any type of tooling (i.e prometheus, grafana comes to mind, or htop, system-monitor etc) to profile 

      • CPU usage on all cores
      • Memory (list the major user of memory i.e could be diskToMirror) 
      • Network (peaks and overall network usage)
      • Disk space (cache and tars) after a full mirroring

      This info can then be added to our current documentation for customers to consume

       

       

            Unassigned Unassigned
            luzuccar@redhat.com Luigi Mario Zuccarelli
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: