Versions Compared

Old Version 21

changes.mady.by.user Daniel Davis

Saved on

compared with

New Version 22

changes.mady.by.user Daniel Davis

Saved on

Key

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

...

  • Use - Core 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
  • Performance - The number of units of work that are accomplished during an operation
  • Interleaving Concurrency - The number and kinds of operations being performed at the same nominal time  (as opposed to a single repetition of an operation)
  • Unit of Work - A metric to be defined appropriate to the Fedora Repository.
    • There may be more than one metric
    • Working definitions:
      • 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

...

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 us how we expect Fedora 4 to be used.
  •  Add repository operations to each category?
  •  Map user operations to tests
  •  Choose performance units for each test
  •  Choose performance expectations for each test
  •  Construct interleaving 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

 

...

Simple access (a.k.a simple read or download) is the download of content and metadata (a.k.a representation of a resource) as a single user operation and one or a small number of repository operations.  It usually RESTful, and usually contained a single request. Simple Access must not require any interleaved writes concurrent writes to accomplish the single user operation.  The content and metadata stays fixed from the beginning to the end of the access.

...