action #41054
/tests is superslow if there are a lot of scheduled jobs
Start date:
2018-09-14
Due date:
% Done:
0%
Estimated time:
Difficulty:
easy
Description
scheduled_jobs queries $job->comments->count which means 3000 SQL queries for 3000 jobs
Related issues
History
#1
Updated by coolo over 4 years ago
- Target version changed from Ready to Current Sprint
#2
Updated by mkittler over 4 years ago
- Assignee set to mkittler
#3
Updated by mkittler over 4 years ago
- Status changed from New to In Progress
#4
Updated by mkittler over 4 years ago
- Status changed from In Progress to Feedback
Seems to work on OSD. Let's see how well it performs if lots of jobs are scheduled.
#5
Updated by mkittler over 4 years ago
- Status changed from Feedback to Resolved
I have just checked out OSD with currently 1158 scheduled jobs (941 blocked by other jobs) and it took only 2.9 seconds to load.
#6
Updated by szarate over 4 years ago
- Target version changed from Current Sprint to Done
#7
Updated by coolo over 4 years ago
- Target version changed from Done to Current Sprint
#8
Updated by coolo over 4 years ago
- Target version changed from Current Sprint to Done
#9
Updated by okurz almost 2 years ago
- Related to action #97190: Limit size of initial requests everywhere, e.g. /, /tests, etc., over webUI and API added