Issue #2732
closed
Syncing from one pulp instance to another is slow
Description
Syncing puppet forge from one pulp instance then to another is slow. Pulp is not utilizing neither CPU or NET bandwidth and all the 5k puppet modules is syncing on 10gb network at rate of one module per second which gives around two hours run time.
This happens for the initial sync as well as for every other re-sync when puppet modules are already present locally.
Updated by ttereshc almost 7 years ago
One optimization was introduced in #2606 so puppet modules won't be re-downloaded (using forge importer) if they are known to Pulp and present on a disk.
Updated by ttereshc almost 7 years ago
- Priority changed from Normal to High
- Triaged changed from No to Yes
Updated by bmbouter almost 7 years ago
When fixing this we need to make sure not to introduce any conditional code paths that are specific to syncing from Pulp versus syncing from puppet forge. If we introduce conditional codepaths then we split the testing benefit and then we have to support two implementations that do the same thing. These are the same concerns that caused us to deprecate nodes and remove it from Pulp3.
Updated by daviddavis over 6 years ago
Per downstream, they're retesting BZ 1445691 and will re-link this issue if it's still slow.
Updated by bmbouter about 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
Updated by bmbouter almost 4 years ago
- Tags Performance added
- Tags deleted (
Sync Performance)
.