Depsolving computes repoclosure once per-rpm being copied
Unlike Pulp2, Pulp3 on-copy depsolving is computing repoclosure on the destination repo once per RPM copied . It only takes 1s to compute - but when copying 10K rpms, that adds up, in both CPU and memory.
#1 Updated by ggainey about 1 month ago
The reason this is happening is that we addressed https://pulp.plan.io/issues/6820. My contention is tha the bahvior called out by 6820 is in fact correct. On copy, what we try to insure is repoclosure for yum/dnf's sake - if you issue "dnf install foo" should result in the latest version of foo being installed.
Note that Pulp2 depsolving code currently also only does repo-closure on the final repo - see https://github.com/pulp/pulp_rpm/blob/2-master/plugins/pulp_rpm/plugins/importers/yum/pulp_solv.py#L987-L990
Please register to edit this issue