Details

    • Type: Story
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: Fedora 4.0.0
    • Fix Version/s: None
    • Component/s: f4-core

      Description

      Based on the Testing Considerations:
      https://wiki.duraspace.org/display/FF/Assessment+Plan+-+Performance#AssessmentPlan-Performance-TestingConsiderations

      ...please modify (or simply run) existing test (ingest.py) to achieve the following three states:
      - a steady state is achieved
      - a declining state is achieved
      - Fedora 4 exhibits high error rates or stops responding

      Please collect and document the results in a way that:
      - someone else can run the same tests
      - it is clear where the failure points are, i.e. how many objects before failure, or what rate of ingest before failure, etc

      Once we have demonstrated that the grinder framework is actually useful in assessing F4 performance, then we can move on to the access tests.

      Here are some results from last sprint: https://wiki.duraspace.org/display/FF/Grinder+Results

        Attachments

          Activity

            People

            • Assignee:
              ksclarke Kevin S. Clarke
              Reporter:
              awoods Andrew Woods
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: