DNF dependency resolution latency in multi-repository environments
0 reputation · 24 Apr 2021, 03:55 UTC
Rocky Linux 9 utilizes a tiered repository structure consisting of BaseOS and AppStream to manage software dependencies. While the distribution maintains application binary compatibility with RHEL, synchronization latency between upstream RHEL repositories and Rocky Linux mirrors can affect the performance of the dependency solver.
When performing complex transactions involving third-party repositories, the DNF package manager must resolve metadata across various sources. This process can encounter a bottleneck during the metadata synchronization phase, particularly when the local metadata cache is stale or when high-latency mirrors delay retrieval of repository metadata files.
Which specific DNF configuration parameters allow granular control of metadata refresh frequency without compromising package-level consistency? Is there a documented method to prioritize BaseOS packages over AppStream during resolution to reduce solver overhead? Are there known limits on concurrent repository metadata downloads that affect resolution time?
rockylinux