Versions Compared

Old Version 29

changes.mady.by.user Daniel Davis

Saved on

compared with

New Version Current

changes.mady.by.user Chris Wilper

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

Performance Testing Initiative

This document is the beginning of a new performance testing initiative for the Fedora Repository and components integrated into Fedora Commons Framework. This work builds upon the superb performance tests and analysis performed by Fiz Karlsruhe, Sun Microsystems (now Oracle) and the performance testing included in each release of the Fedora Repository. We hope this will provide a common performance testing framework and begin a community effort to characterize Fedora performance to document best practices for configuration and identify bottlenecks for subsequent software development. It is presumed that most performance testing will be black-box (through the APIs) but instrumentation may be added to help find bottlenecks.

Goals Include:

  • Bottleneck analysis - Eliminate or remove bottlenecks in the current code base
  • Feature analysis - Guide the addition of new feature with performance information
  • Tuning analysis - Provide information to help tune installations and identify if your installation is under performing
  • Sizing information - Provide information to permit installation to size their systems and subsystems
  • Performance scalability test
  • Size scalability test

Testing Framework Requirements

Performance testing will be accomplished using testbeds kindly provided by a number of community sources. Testing will can also be accomplished using Cloud infrastructure such as Amazon's offerings. Individual user organization can stand up their own versions of the testing framework for their unique infrastructure. Details of the test configurations will be documented in this Wiki as the configurations are implemented.

...

There can be any combination of the above and but it can start simplesimply, built incrementally.

Questions to Answer.

What is the minimal useful starting point:?
What is the first reference platform?
What to we consider the first key tests?
Who will write tests?
When (what events) are tests run?
Can we test a branch?
What is the overlap with integration/functional tests?

Starting Configurations

Configuration 1 -

  • Single server-grade host with direct attached disks
    • Load injector on server
  • Bamboo server from DuraSpace
  • Publishing at DuraSpace

...

  • Cloud server set
    • Fedora Host Server Instance and cloud storage (EBS equivalent)
    • Database Server Instance and cloud storage (EBS equivalent) or combined with Fedora Instance
    • Resource Index Server Instance and cloud storage (EBS equivalent) or combined with Fedora Instance
    • Load Injector Instance
  • Bamboo from DuraSpace
  • Publishing at DuraSpace