QA » openQA Project

mkittler, szarate: I think this is strongly linked to #20606 , isn't it?

@okurz: Yes, my implementation of #20606 covers already this ticket for the 'Live Preview' tab.

Since 'Details' is default anyways, only the tabs 'Logs & Assets', 'Settings', 'Comments' and 'Previous results' remaining. I doubt that anything else than 'Previous results' would give us a noticeable performance benefit, but I can check of course.

mkittler wrote:

I did some profiling and like expected the heaviest tab is 'Details' which we want to be displayed by default anyways. Reading the test modules takes alone 35 % of the time. Rendering the job modules ('Details' tab) makes another 40 %. Rendering overall page elements another 10 %.

So I don't think there is currently much to gain from loading 'Logs & Assets', 'Settings', 'Comments' and 'Previous results' only on demand. I would let this ticket open because it maybe makes sense when we add more features to tests page (like https://progress.opensuse.org/issues/25680).

But this ticket mentions "test details" already. So let me refine my suggestion:

• Lazy load the details tab because it is in most cases the one with longest loading time
• Optional: Lazy load the other tabs

Still "Low"?

I have experimented with this myself recently when I was adding the "investigation" feature. But for now I ended up keeping the behaviour to always show the "Details" tab even in case there are no module results at all because we just show the log content, already asynchronously, in case of incompletes.

QA tools team discussed this 2020-04-07 and we have the following ideas:

• By default we should only load content synchronously that comes from the database, everything loading from filesystem should be done asynchronously or "on demand", either later by requests from the initial page loaded or by user actions, e.g. when clicking on tabs or buttons
• Of course loading from"fast" (expensive) storage like SSD or NVMe can help but shouldn't be relied upon
• Also see related ticket #32611 about correct page self-refreshes
• We have a "reason" in every job that we already use successfully for incompletes. Our initial goal was to use the reason when the worker did not manage to upload any log file at all. Then we extended to always use the reason for every incomplete job. We can extend that concept to every not-passed job as long as we limit the size that we store in the database, e.g. cut reason string at a reasonable, human-readable length, e.g. 120 characters. This way we can also load the reason synchronously.

maybe, but please consider any "ltp" jobs out of scope for this ticket. There are LTP specific tickets.

Those are not just ltp jobs, e.g. on o3 these are currently the biggest jobs:

openqa=# select id, test, result_size, (result_size / 1024 / 1024 / 1024) as  result_size_gb from jobs where result_size is not null order by result_size desc limit 20;
   id    |            test            | result_size | result_size_gb 
---------+----------------------------+-------------+----------------
 1224142 | gnome                      |  1438745990 |              1
 1219900 | gnome                      |  1064366118 |              0
 1219897 | gnome                      |  1022172477 |              0
 1226040 | textmode                   |  1016078684 |              0
 1224146 | textmode                   |   906820427 |              0
 1224144 | install_with_updates_kde   |   769961168 |              0
 1216733 | gnome                      |   671770211 |              0
 1224147 | cryptlvm                   |   666113740 |              0
 1226041 | cryptlvm                   |   661436222 |              0
 1216736 | gnome                      |   653178283 |              0
 1217807 | install_with_updates_kde   |   646933169 |              0
 1217806 | install_with_updates_gnome |   641942140 |              0
 1223483 | kde-wayland                |   619408445 |              0
 1218735 | kde-wayland                |   613924168 |              0
 1226065 | RAID5                      |   609392278 |              0
 1227140 | RAID5                      |   597121762 |              0
 1217809 | textmode                   |   591906838 |              0
 1223563 | extra_tests_in_textmode    |   583677747 |              0
 1218229 | gnome                      |   582889441 |              0
 1221359 | gnome                      |   573328610 |              0
(20 Zeilen)

The top ones can not be accessed because they time out.

PR: https://github.com/os-autoinst/openQA/pull/2943

The PR does not include fragmented loading of the "Details" or "External results" tab so it is not solving the timeout problem yet. However, I suppose it already fulfills the acceptance criteria.