Project

Profile

Help

Actions
Send by e-mail Copy link

Backport #9388

closed

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

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

Status:
CLOSED - CURRENTRELEASE
Priority:
Urgent
Assignee:
-
Sprint/Milestone:
3.14.4
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 - CURRENTRELEASEggaineyActions
Actions
Copy link
 #1

Updated by ggainey about 3 years ago

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

Updated by dalley about 3 years ago

  • Sprint/Milestone set to 3.14.4
Actions
Copy link
 #3

Updated by dalley about 3 years ago

  • Assignee deleted (ggainey)
Actions
Copy link
 #4

Updated by dalley about 3 years ago

  • Status changed from NEW to POST
Actions
Copy link
 #5

Updated by dalley about 3 years ago

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

Added by dalley about 3 years ago

Revision f0e1a783 | View on GitHub

Fix depsolving perf-issues by doing repoclosure once.

backports #9387. [nocoverage]

fixes #9388

(cherry picked from commit 4594deb84fb8df9a8ba131daacc2f7d98626d456)

Actions
Copy link
 #6

Updated by dalley about 3 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions
Copy link
 #7

Updated by pulpbot about 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Send by e-mail Copy link

Also available in: Atom PDF