Low applicability performance for large setups due to inefficient query of repo content
Regenerate applicability (both for a repo or for a consumer) requests from mongo repo_content_units data that are not required for the calculation. This has very evident negative performance impact, as
- it puts mongo under higher load
- the task keeps redundant data in a map
Restricting the search to return just required fields only improves task performance.
Avoid checking the pkglist of the errata in other repos when calculating the applicability for a repo in the majority of cases. The collections get updated every time the repo is synced. Katello is always calculating the applicability against the synced repos only. For very old content or for copied repos there should be a fallback logic.