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., over webUI and API
76%
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", both in webUI as well as API
- Add configurable limit for "finished", then extend to "scheduled" and "running"
- Run (at least a single-time manual test) of 100k or more "scheduled" or "running" jobs :)
- 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
Related issues
History
#1
Updated by okurz almost 2 years ago
- Related to action #41054: /tests is superslow if there are a lot of scheduled jobs added
#2
Updated by mkittler almost 2 years 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 almost 2 years ago
- Parent task set to #92854
#4
Updated by okurz almost 2 years ago
maybe https://github.com/os-autoinst/openQA/pull/4145 helps for a start.
#5
Updated by okurz about 1 year ago
- Target version changed from future to Ready
#6
Updated by okurz about 1 year ago
- Related to action #110680: Overview page shouldn't allow long-running requests without limits size:M added
#7
Updated by okurz about 1 year ago
- Related to action #110677: Investigation page shouldn't involve blocking long-running API routes size:M added
#8
Updated by okurz about 1 year ago
- Status changed from New to Blocked
- Assignee set to okurz