Issue #2623
closed
Errata publish performace degradation
Description
pulp-admin rpm repo create --repo-id epel7 --relative-url epel7 --feed https://dl.fedoraproject.org/pub/epel/7/x86_64/ --download-policy on_demand
pulp-admin rpm repo sync run --repo-id epel7
Notice that publish of errata is extremely slow, several seconds per each erratum.
My tests shows that it is because of this recent errata fix.
Related issues
Updated by semyers about 7 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to semyers
I feel like we worked pretty hard to keep the performance the same, so I'll take a look. If the cause of the slowdown is not obvious or simple to fix then I propose to just revert my PR, fix the bug the initial (and terrible way) I did, open up a separate refactor issue referencing the reverted commit, and we can get the new errata behavior in formally with 2.13.
Updated by bizhang about 7 years ago
- Sprint/Milestone set to 34
- Triaged changed from No to Yes
Added by semyers about 7 years ago
Updated by semyers about 7 years ago
- Related to Issue #2560: Non-unique collection names in erratum pkglists causes yum not to show all packages added
Updated by semyers about 7 years ago
- Status changed from ASSIGNED to POST
Updated by semyers about 7 years ago
- Status changed from POST to MODIFIED
Applied in changeset f93b8dc947b5e212ca52bfbd8ae72c503b72c896.
Updated by semyers about 7 years ago
This is a little odd, since it was broken and fixed between the 2.12.1 and 2.12.2 releases. If we want to verify this, it would be to ensure there's little to no difference between the performance of publishing errata in 2.12.1 and 2.12.2.
Updated by bizhang about 7 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
.
Don't rebuild repo_unit_nevra for every unit
This made errata publish very slow.
closes #2623 https://pulp.plan.io/issues/2623