Description of problem:
The tasks list is slow. It takes a while to find all tasks:
Displaying entries 1 - 50 of 10026 in total
With the oldest tasks being 5 months old:
Create user 'API Admin' stopped success 2014-09-18 08:43:18 UTC
Create user 'Anonymous Admin' stopped success 2014-09-18 08:43:17 UTC
Please limit the default view of the task list to a relevant time range of 24h.
Have an UI element quickly change the relevant time range in easy steps:
This limit in timestamp shall also improve the performance of the tasks list
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create 10000+ tasks
2. List Tasks
Slow loading of the data. Many pages available.
Only relevant tasks in the specified time range.
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
I tested the speed of the tasks page on Satellite 6.1 and 6.2 (snapshot version):
on 6.1: /foreman_tasks/tasks for 96 tasks, pagination of 20 takes 4692ms
/foreman_tasks/tasks for 96 tasks, pagination of 10,000 takes 15426ms
on 6.2: /foreman_tasks/tasks for 2035 tasks, pagination of 20 takes 1103ms
/foreman_tasks/tasks for 2035 tasks, pagination of 10,000 takes 53606ms
I saw similar improvement on a Katello 2.4 installation with >3000 tasks, pagination of 20.
I am investigating more now to see what caused the improvement.
This appears to be addressed via an index that was added to the DB.
I believe this bug was addressed by adding an index to the tasks table, which sped things up significantly. I think this makes the dropdown with default of 24h not needed anymore, but if you disagree please reply back to this BZ. Thanks!
@ Sat 6.2 Snap 9.2
I tested this with 4493 tasks in 225 pages with 20 entries per page.
Its loading the tasks in expected/reasonable time.
So, moving the bz to verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.