Actions
Bug #32142
closedexcess memory consumption when importing errata during pulp3 migration
Status:
Closed
Priority:
Normal
Assignee:
Category:
Repositories
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1940678
Description of problem:
On a system with a LOT of repositories, during migration the sidekiq worker for dynflow will consume ~16GB, which is way too much.
We need to look at breaking up the errata import process to not consume as much memory.
In this case, there were ~25,000 errata, and 21,153,436 errata <-> repo associations (the biggest issue)
Actions