Uploaded image for project: 'OpenShift Runtimes'
  1. OpenShift Runtimes
  2. RUN-1298

Tune the performance of Podman as noted in the description

    XMLWordPrintable

Details

    • Epic
    • Resolution: Done
    • Normal
    • None
    • None
    • None
    • Tune Podman's Performance
    • False
    • False
    • To Do
    • sst_container_tools
    • 100
    • 100% 100%
    • Undefined

    Description

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • Create better overall performance for the Podman project.  Brent Baude has noted a number of potential areas that can be improved.

      Why is this important?

      • The faster we are, the better customers like us.

      Scenarios

      Thanks to Brent Baude for generating these.

      1. Come up with some common Podman tasks that one might consider perf
        sensitive (create, run, rm, etc).
      1.  

       Run against Podman v2.X and record.

      1.  

       Run against Podman 3.x and record.

      1.  

       Understand any regressions.

      1.  

       Instrument Podman v3.0 runs and look at where time is spent.

      1.  

       Record heavy usage of time spent on cards for SME's to examine.

      1. More?

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. Should be none except for time to investigate and fix.

      Previous Work (Optional):

      Open questions::

      1. Are there other opportunities to improve performance?

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

      Attachments

        Activity

          People

            Unassigned Unassigned
            tsweeney@redhat.com Tom Sweeney
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: