Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #1462

closed

Errata Install to Content Host takes too long and doesn't scale well

Added by mhrivnak over 8 years ago. Updated about 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
dkliban@redhat.com
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.6.0
Platform Release:
2.8.5
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Sprint 2
Quarter:

Description

We have a report that installing a number of erratta takes a long time. There is no info about what the bottleneck is, so we need to investigate.

From bugzilla:


When applying (installing) errata on a Content Host from the server, it takes a very long time.

For example, installing ~556 errata on a single content host was observed to take ~44 minutes. Most of that time (~36 minutes) was during the 'initiating the install' phase of the task (i.e. executing the pulp consumer content install).  While this may not sound too bad a first glance, it won't scale well as the behavior is linear.  As a result, if there were 100 content hosts, that same action could take ~3 days.
Actions
Send by e-mail Copy link

Also available in: Atom PDF