Plugins » Katello

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: