Project

Profile

Help

Backport #9388

Backport "Depsolving computes repoclosure once per-rpm being copied" to 3.14.z

Added by ggainey 3 months ago. Updated 2 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Urgent
Assignee:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Triaged:
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

Copied from RPM Support - Issue #9387: Depsolving computes repoclosure once per-rpm being copiedCLOSED - CURRENTRELEASE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision f0e1a783 View on GitHub
Added by dalley 2 months ago

Fix depsolving perf-issues by doing repoclosure once.

backports #9387. [nocoverage]

fixes #9388

(cherry picked from commit 4594deb84fb8df9a8ba131daacc2f7d98626d456)

History

#1 Updated by ggainey 3 months ago

  • Copied from Issue #9387: Depsolving computes repoclosure once per-rpm being copied added

#2 Updated by dalley 3 months ago

  • Sprint/Milestone set to 3.14.4

#3 Updated by dalley 3 months ago

  • Assignee deleted (ggainey)

#4 Updated by dalley 3 months ago

  • Status changed from NEW to POST

#5 Updated by dalley 3 months ago

  • Tracker changed from Issue to Backport
  • % Done set to 0
  • Severity deleted (3. High)
  • Groomed deleted (No)

#6 Updated by dalley 2 months ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#7 Updated by pulpbot 2 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF