Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1038824

Summary:	[perf] decompression of metadata should be down in the background
Product:	[Fedora] Fedora	Reporter:	Elad Alfassa <elad>
Component:	dnf	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	rawhide	CC:	jsilhan, jzeleny, michal, packaging-team-maint, pnemade, rholy
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-11-24 12:33:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Elad Alfassa 2013-12-05 21:42:48 UTC

It seems that when dnf is downloading metadata, it basically does
download (repo1)
decompress/process (repo1)
download/process (repo2)
decompress/process (repo2)
and so on.

Since downloading is not a cpu-heavy task but processing/decompressing of metadata usually is, it would make sense to preform the decompression/processing in the background, without blocking the download of the rest of the repository metadata.

Comment 1 Ales Kozumplik 2013-12-06 07:14:43 UTC

Hello, we'll look into this when time to optimize comes. Most users however use scheduled makecache and wouldn't benefit from this.

Comment 2 Ales Kozumplik 2014-04-06 11:42:44 UTC

*** Bug 1084564 has been marked as a duplicate of this bug. ***

Comment 3 Honza Silhan 2014-11-24 12:33:41 UTC


*** This bug has been marked as a duplicate of bug 850896 ***