Red Hat Bugzilla – Bug 1296657
dnf-plugins-core version of repoquery with --resolve much slower than yum-utils
Last modified: 2016-01-11 08:11:46 EST
Description of problem:
old way with yum-utils: repoquery --requires --resolve <some_pkg>
new way with dnf-plugins-core: dnf repoquery --requires --resolve <some_pkg>
Version-Release number of selected component (if applicable):
% rpm -qa | egrep 'yum-utils|dnf-plugins-core'
Steps to Reproduce:
Compare wall time to run yum-utils' repoquery vs. dnf-plugins-core:
sh -c 'time repoquery --requires --resolve gscan2pdf'
sh -c 'time dnf repoquery --requires --resolve gscan2pdf'
On both cases, the metadata cache was up to date before running the repoquery.
Without --resolve, the times are comparable (< 5 s).
Is this a difference due to fundamentally different issues between yum & dnf? The magnitude of speed difference seems to be indicate than just 'python adds a little overhead'.
Hints to where to start profiling are appreciated - I currently have near zero internals knowledge for yum/dnf, but I'm willing to dig a little.
*** This bug has been marked as a duplicate of bug 1279538 ***