Versions Compared

Old Version 31

changes.mady.by.user Daniel Davis

Saved on

compared with

New Version 32

changes.mady.by.user Daniel Davis

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Use - Canonical action in a use case from the user's view
  • User Operation - Users view of a logical, single operation
  • Repository Operation - Repositories view of a logical, single operation for our purposes as the result of one or more API calls
  • Performance - The number of units of work that are accomplished during an operation
  • Concurrency - The number and kinds of operations being performed at the same nominal time  (as opposed to a single repetition of an operation)
  • Measurement - Metrics (to be defined) that are appropriate for measuring the results of a performance test of the Fedora Repository.
    • There may be more than one metric
    • Working ideas:
      • The amount in bytes of content and metadata for an operation, or per unit of time
      • The number of operations per unit of time
      • The time between when an operation is started and when it is completed
      • Count of operations performed possible eliminating content transfer time (normalized)

 

Warning
titleTo Be Done
  •  Are these a good list of usage categories?
  •  Validate/Add user operations for each category (examples). Mark them as now, or future, or never? Note, if an external tool is needed. - This tell to the likely limits we can do). Prioritize short term goals. - This tells us how we expect Fedora 4 is to be used.
  •  Add repository operations to each category?test
  •  Map user operations to tests
  •  Choose performance units for each test
  •  Choose performance expectations for each test
  •  Construct concurrency matrix (to the limit of what is practical to accomplish) - Note: single thread tests will be use as a baseline as informed by Single Node tests

 

...