Project

General

Profile

Actions
Copy link

action #120540

closed

[timeboxed:10h][research] Find inefficient test implementations and backend use by a "tests per hardware machine ratio" size:S

Added by okurz about 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
robert.richardson
Target version:
openQA Project (public) - Ready
Start date:
2022-11-15
Due date:
% Done:

0%

Estimated time:

Description

Motivation

#73072 and #120154 . We have most of our tests based on the qemu backend which allows efficient uses. In other cases like the ppc hmc backend we treat tests like "bare metal" tests which is rather inefficient, e.g. does not allow loading VM images, AFAIK RAM can not be configured from tests limiting the number of instances per hardware instances a lot. To find out our least efficient implementations we should query the database of tests to find a "tests per hardware machine ratio".

Suggestions

  • Run SQL queries against OSD's production database to get the data either manually, e.g. ssh osd 'sudo -u geekotest psql openqa' and in there copy-paste one of the existing SQL commands from telegraf config for a a start, or use our metabase instance https://maintenance-statistics.dyn.cloud.suse.de (okta credentials, e.g. username "okurz", not email)
  • Compare to https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/monitoring/telegraf/telegraf-webui.conf#L108 . Maybe easiest to just come up with the according query and replace "by host" with "by backend"
  • Run a calculation like number of "failed"/number of all jobs grouped by "machine" or "backend" or "WORKER_CLASS" whatever is easiest
  • Make list of "inefficient" vs. "efficient" backends (or is everything but QEMU "inefficient?) That's the hypothesis to prove
Actions
Copy link

Also available in: Atom PDF