Project

General

Profile

Actions

action #94354

closed

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

Optimize /dashboard_build_results and /group_overview/* pages

Added by tinita over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2021-06-21
Due date:
% Done:

0%

Estimated time:

Description

On the homepage and group_overview pages comment_data_for_jobs is called. It collects bugrefs and fetches all bugs, but in those views we don't even show this data.
Also, all columns of Comments are selected, while only two are needed.

I looked into this while working on #93925
I already did a fix, so even if this is not a high priority, it's already done, and an easy fix. So i took the liberty to create this ticket and a PR.

Runtime before:
/group_overview/1: 1.0-1.1s
/dashboard_build_results: 0.9-0.95s
Runtime after:
/group_overview/1: 0.8-0.85s
/dashboard_build_results: 0.75-0.77s

SQL statements which will be saved:

SELECT me.id, me.bugid, me.title, me.priority, me.assigned, me.assignee, me.open, me.status, me.resolution, me.existing, me.refreshed, me.t_created, me.t_updated FROM bugs me WHERE ( me.bugid = ? ): 'boo#1183454'
SELECT me.id, me.bugid, me.title, me.priority, me.assigned, me.assignee, me.open, me.status, me.resolution, me.existing, me.refreshed, me.t_created, me.t_updated FROM bugs me WHERE ( me.bugid = ? ): 'poo#92945'
SELECT me.id, me.bugid, me.title, me.priority, me.assigned, me.assignee, me.open, me.status, me.resolution, me.existing, me.refreshed, me.t_created, me.t_updated FROM bugs me WHERE ( me.bugid = ? ): 'poo#92401'
SELECT me.id, me.bugid, me.title, me.priority, me.assigned, me.assignee, me.open, me.status, me.resolution, me.existing, me.refreshed, me.t_created, me.t_updated FROM bugs me WHERE ( me.bugid = ? ): 'boo#1180358'
# and so on

for each build

Actions #1

Updated by tinita over 2 years ago

  • Description updated (diff)
  • Status changed from In Progress to Feedback
Actions #2

Updated by okurz over 2 years ago

  • Target version set to Ready
Actions #3

Updated by tinita over 2 years ago

osd, before:

  • /dashboard_build_results: around 7.5-9s
  • /group_overview/129: around 2s
  • /group_overview/129?limit_builds=400: 19-21s

after:

  • /dashboard_build_results: 6.5-8s
  • /group_overview/129: 1.5-1.8s
  • /group_overview/129?limit_builds=400: 15-16s

o3, before:

  • /dashboard_build_results: around 3-3.3s
  • /group_overview/1: around 2.1-2.3s

after:

  • /dashboard_build_results: around 2.5-2.8s
  • /group_overview/1: 1.6-1.9s
Actions #4

Updated by okurz over 2 years ago

  • Related to action #93925: Optimize SQL on /tests/overview added
Actions #5

Updated by okurz over 2 years ago

  • Related to deleted (action #93925: Optimize SQL on /tests/overview)
Actions #6

Updated by okurz over 2 years ago

  • Parent task set to #92854

#92854 is a good parent for this one as well, right?

Actions #7

Updated by tinita over 2 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF