Bug #24024
closedIndexContent step of initial repo sync takes 20+ minutes
Description
If you on-demand sync a large repo like RHEL7 Server x86_64, the Pulp sync will take about 15-20 minutes. However, the IndexContent step will take even longer, perhaps 20-30 minutes.
It looks like most of the time is spent in import_all:
2018-06-20T21:53:50 [W|app|] begin import_all Katello::Pulp::Rpm
2018-06-20T22:06:47 [W|app|] end import_all Katello::Pulp::Rpm
2018-06-20T22:06:49 [W|app|] begin import_all Katello::Pulp::Srpm
2018-06-20T22:06:49 [W|app|] end import_all Katello::Pulp::Srpm
2018-06-20T22:06:51 [W|app|] begin import_all Katello::Pulp::Erratum
2018-06-20T22:18:21 [W|app|] end import_all Katello::Pulp::Erratum
2018-06-20T22:18:21 [W|app|] begin import_all Katello::Pulp::PackageGroup
2018-06-20T22:18:24 [W|app|] end import_all Katello::Pulp::PackageGroup
I think most of the time is spent in the loop in https://github.com/Katello/katello/blob/master/app/models/katello/concerns/pulp_database_unit.rb#L51-L57, where each unit is loaded individually. Resyncs do not take nearly as long.
Syncing one or more large repos is extremely common when setting up a Katello installation, so any time savings here would be a big deal.
Updated by Andrew Kofink over 6 years ago
- Translation missing: en.field_release set to 338
Updated by Jonathon Turel over 6 years ago
- Target version changed from Katello 3.7.0 to Katello 3.9.0
Updated by Jonathon Turel about 6 years ago
- Target version changed from Katello 3.9.0 to Katello Backlog
Updated by The Foreman Bot about 6 years ago
- Status changed from New to Ready For Testing
- Assignee set to Christine Fouant
- Pull request https://github.com/Katello/katello/pull/7862 added
Updated by Christine Fouant about 6 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|00eb9331095a0149fc39a0fc15b87832895a6b78.