Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #9387

closed

Depsolving computes repoclosure once per-rpm being copied

Added by ggainey about 3 years ago. Updated about 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Urgent
Assignee:
ggainey
Sprint/Milestone:
3.16.0
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 105
Quarter:

Description

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.

Related issues

Has duplicate RPM Support - Issue #9335: Huge memory consumption when performing depsolving-enabled copiesCLOSED - DUPLICATEggaineyActions
Copied to RPM Support - Backport #9388: Backport "Depsolving computes repoclosure once per-rpm being copied" to 3.14.zCLOSED - CURRENTRELEASE

Actions
Actions
Send by e-mail Copy link

Also available in: Atom PDF