openstack/rally
Code Issues Proposed changes
8e9a7dc918
rally/doc/feature_request/historical_performance_data.rst
Boris Pavlovic ef583a3415 Add feature_request mechanism 
This will be standart way for end users to ask Rally team to get
some new feature.

The idea is to make it realy simple for end users to ask about covering
their use cases.

E.g. to add request users don't need to deep dive in rally community,
road map and how it works. They need just to share their use cases
that is not covered by current rally functionality.

As a bonus adding some Readme.rst files related to doc/* dirs

Change-Id: I4c615101012ac9d1668ed766ac831f7e5c8129a8
2014-08-25 19:20:15 +04:00

647 B
Raw Blame History

Historical performance data

Use case

OpenStack is really rapidly developed. Hundreds patches are merged daily and it's really hard to track how performance is changed during time. It will be nice to have a way to track performance of major functionality of OpenStack running periodically rally task and building graphs that represent how performance of specific method is changed during the time.

Problem description

There is no way to bind tasks

Possible solution

  • Add grouping for tasks
  • Add command that creates historical graphs