openstack/rally-openstack
Code Issues Proposed changes
feac64db9b
rally-openstack/doc/feature_request/check_queue_perfdata.rst
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

702 B
Raw Blame History

Check queue perfdata

Use case

Sometimes OpenStack services use common messaging system very prodigally. For example Neutron metering agent sending all database table data on new object creation i.e https://review.openstack.org/#/c/143672/. It cause to Neutron degradation and other obvious problems. It will be nice to have a way to track messages count and messages size in queue during tasks.

Problem description

Heavy usage of queue isn’t checked.

Possible solution

  • Before running task start process which will connect to queue topics and measure messages count, size and other data which we need.