RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

I'm throttling dnf in order to avoid consuming full bandwidth, being a good fellow and sharing my internet connection with my wife which also works from home during this covid19 pandemic.

dnf update is taking 100% of the CPU and with 320MB to download at 200k/s causes my laptop CPU reaching 96°C which makes my keyboard too hot to be used.

No production impact so setting severity to medium but I would be grateful seeing this fixed for 8.3.z

# rpm -qa |grep dnf
dnf-4.2.17-7.el8_2.noarch
python3-dnf-plugins-core-4.0.12-4.el8_2.noarch
python3-libdnf-0.39.1-6.el8_2.x86_64
python3-dnf-plugin-spacewalk-2.8.5-11.module+el8.1.0+3455+3ddf2832.noarch
libdnf-0.39.1-6.el8_2.x86_64
python3-dnf-plugin-versionlock-4.0.12-4.el8_2.noarch
dnf-data-4.2.17-7.el8_2.noarch
dnf-plugin-subscription-manager-1.26.20-1.el8_2.x86_64
dnf-plugin-spacewalk-2.8.5-11.module+el8.1.0+3455+3ddf2832.noarch
python3-dnf-4.2.17-7.el8_2.noarch
dnf-plugins-core-4.0.12-4.el8_2.noarch

# cat /etc/dnf/dnf.conf 
[main]
gpgcheck=1
installonly_limit=3
clean_requirements_on_remove=True
best=True
skip_if_unavailable=False
exclude=redhat-internal-configuser-firststart*
deltarpm=1
throttle=200k
max_parallel_downloads=1

DNF uses the librepo library to downloading. The problem is in this library. And it affects DNF and other library users.

I prepared a fix: https://github.com/rpm-software-management/librepo/pull/217

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (librepo bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4429