Bug #18916
closed
identify pulp errata by id only, to save pulp celery memory
Description
Description of problem:
Having a large repo with many (>4000) errata added to a Content View, then publishing this C.V. causes pulp celery worker consuming much memory (i.e. 5GB). Reasoning is described in
http://pulpproject.org/2017/02/17/why-does-copy-use-lots-of-memory/
Let specify fields uniquely identifying errata like katello does for RPM in:
https://github.com/Katello/katello/blob/master/app/services/katello/pulp/rpm.rb#L6
Version-Release number of selected component (if applicable):
tfm-rubygem-katello-3.0.0.95-1.el7sat.noarch
How reproducible:
100%
Steps to Reproduce:
1. Sync a big repo with >4k errata
2. Create a Content View with that repo
3. Publish the repo
4. During the publish, monitor memory usage of pulp celery workers
Actual results:
4. shows very high memory usage (seen 5GB, depends a lot on repo)
Expected results:
4. shows reasonable low memory usage
Additional info:
Updated by The Foreman Bot almost 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/6679 added
Updated by Pavel Moravec almost 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|c83af8691f238ac106b416b8574140d069342295.
Updated by Eric Helms almost 8 years ago
- Translation missing: en.field_release set to 211