Dan Smith c2772c2984 Gather performance data after tempest
This makes us gather a bunch of consistent statistics after we run
tempest that can be use to measure the impact of a given change. These
are stable metrics such as "number of DB queries made" and "how much
memory is each service using after a tempest run."

Note that this will always run after devstack to generate the JSON
file, but there are two things that control its completeness:

 - MYSQL_GATHER_PERFORMANCE must be enabled to get per-db stats
 - Unless tls-proxy is enabled, we will only get API stats for keystone

Change-Id: Ie3b1504256dc1c9c6b59634e86fa98494bcb07b1
2022-04-20 13:07:22 -07:00
..
2015-03-28 14:35:12 -05:00
2021-01-12 17:41:19 -08:00
2019-03-29 11:20:19 -07:00
2016-08-22 17:00:50 +00:00
2022-02-01 11:27:05 +00:00
2021-10-16 17:33:12 +02:00
2021-06-09 09:37:34 +02:00