Project

General

Profile

action #97190

coordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes

coordination #92854: [epic] limit overload of openQA webUI by heavy requests

Limit size of initial requests everywhere, e.g. /, /tests, etc.

Added by okurz 10 months ago. Updated 17 days ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2022-05-30
Due date:
% Done:

0%

Estimated time:
(Total: 0.00 h)
Difficulty:

Description

Motivation

We have more and more tests, e.g. on https://openqa.suse.de/, either completed tests or sometimes even just scheduled tests, see #97043 . This showed that some routes or pages can become quite slow. IMHO a good design approach is to always limit size of initial requests, i.e. always foresee that there could be much more data in a certain set that initially imagined

Ideas

  • Wherever we process openQA jobs initially limit. We already do it for "finished" jobs on /tests but not for "running" or "scheduled"
  • the index page of https://openqa.suse.de/ at time of writing takes like 10s to show results. Likely the index page should also only process less data by default if it's "too much" and load more only on request

Subtasks

action #111770: Limit all displayed tests on /tests, but query configurable and show complete number of jobsNew


Related issues

Related to openQA Project - action #41054: /tests is superslow if there are a lot of scheduled jobsResolved2018-09-14

Related to openQA Project - action #110680: Overview page shouldn't allow long-running requests without limits size:MResolved2022-02-03

Related to openQA Project - action #110677: Investigation page shouldn't involve blocking long-running API routes size:MResolved2022-02-03

History

#1 Updated by okurz 10 months ago

  • Related to action #41054: /tests is superslow if there are a lot of scheduled jobs added

#2 Updated by mkittler 10 months ago

It would still be nice to see the total number of scheduled, blocked and running jobs on "All tests". So when limiting the number of rows that should be taken into account.

Note that I improved the performance of loading the table of running jobs yesterday: https://github.com/os-autoinst/openQA/pull/4133

#3 Updated by okurz 10 months ago

  • Parent task set to #92854

#4 Updated by okurz 10 months ago

#5 Updated by okurz about 2 months ago

  • Target version changed from future to Ready

#6 Updated by okurz about 2 months ago

  • Related to action #110680: Overview page shouldn't allow long-running requests without limits size:M added

#7 Updated by okurz about 2 months ago

  • Related to action #110677: Investigation page shouldn't involve blocking long-running API routes size:M added

#8 Updated by okurz about 2 months ago

  • Status changed from New to Blocked
  • Assignee set to okurz

blocked by #110677 and #110680

#9 Updated by okurz 17 days ago

  • Status changed from Blocked to New
  • Assignee deleted (okurz)

Both #110677 and #110680 resolved, now we can rediscuss what to do for other tables, especially /tests

Also available in: Atom PDF