Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

Fix high memory consumption issues #179

Merged
merged 1 commit into from Jul 24, 2020
Merged

Conversation

dralley
Copy link
Contributor

@dralley dralley commented Jul 21, 2020

@dralley
Copy link
Contributor Author

dralley commented Jul 21, 2020

Before and after with a single repository: https://imgur.com/a/mrqAJ2k

With 8 repositories and ~230k units, it maxes out around 600mb of RAM. That definitely would have run out of memory before in my experience, even with ~12gb allocated to the box.

I'm going to keep looking into this tomorrow because I want to make sure the tool I'm using isn't lying to me, since a lot of what we're doing is using C-based libraries that Python profiling tools can't always necessarily track. Also, it's a lot more difficult to track the memory usage of many different processes than one process, so I made a few hacks to execute the task without forking and disable parallel repo migration, so this isn't a very real-world setup. I'll see what I can do to verify this properly.
I'll also probably look into https://pulp.plan.io/issues/7183

@goosemania
Copy link
Member

🎉 🐈 🥇

@goosemania goosemania merged commit 0132839 into pulp:master Jul 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants