Project

Profile

Help

Issue #6334

closed

Low applicability performance for large setups due to inefficient query of repo content

Added by ttereshc about 4 years ago. Updated almost 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
2.21.2
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

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.

Also available in: Atom PDF