History

Boris Pavlovic 2f4555be27 Rephrase docs call things properly

In a lot of placeses we are using word "benchmark" which
can mean workload, subtask, or test case which is very confusing.

This patch partially address wrong usage of "benchamrk" word

Change-Id: Id3b2b7ae841a5243684c12cc51c96f005dbe7544

2017-08-03 18:39:10 +00:00

implemented

Rephrase docs call things properly

2017-08-03 18:39:10 +00:00

capture_task_logging.rst

Fix some typos by toolkit typo

2015-11-20 00:55:01 +08:00

check_queue_perfdata.rst

Rephrase docs call things properly

2017-08-03 18:39:10 +00:00

comparing_results_of_2_tasks.rst

Add feature_request mechanism

2014-08-25 19:20:15 +04:00

distributed_load_generation.rst

Rephrase docs call things properly

2017-08-03 18:39:10 +00:00

explicitly_specify_existing_users_for_scenarios.rst

[Feature request] Explicitly specify existing users for scenarios

2015-05-23 09:34:43 +03:00

historical_performance_data.rst

Word spells have been corrected

2015-08-22 12:36:29 +05:30

installation_script_enhancements.rst

Feature request improve install script

2015-06-09 10:52:37 +00:00

installing_isolated.rst

[docs] reduce sphinx warnings

2017-02-07 15:28:53 +02:00

launch_specific_benchmark.rst

Rephrase docs call things properly

2017-08-03 18:39:10 +00:00

multi_scenarios_load_gen.rst

Rephrase docs call things properly

2017-08-03 18:39:10 +00:00

multiple_attach_volume.rst

[docs][6] Re-design docs to cover all user-groups

2017-01-10 11:25:00 -08:00

persistence_benchmark_env.rst

Rephrase docs call things properly

2017-08-03 18:39:10 +00:00

production_ready_cleanup.rst

Rephrase docs call things properly

2017-08-03 18:39:10 +00:00

README.rst

[docs][6] Re-design docs to cover all user-groups

2017-01-10 11:25:00 -08:00

README.rst

Feature requests

To request a new feature, you should create a document similar to other feature requests. And contribute it to this directory using the next instruction.

If you don't have time to contribute your feature request via Gerrit, please contact Andrey Kurilin (andr.kurilin@gmail.com)