[Pulp-dev] Memory consumption on RPM sync

Lubos Mjachky lmjachky at redhat.com
Tue Nov 26 18:03:39 UTC 2019

Great results!

I have tried to apply the same procedure like you, as I am currently
working on a similar issue (https://pulp.plan.io/issues/5689), but there is
one problem. I could not run performance tests with additional profilers
because my workstation run out of memory after a couple of minutes. I have
got only 16GB of RAM. Also, as you noticed, the synchronization takes a
huge amount of time. I think that we should not run those tests and
profilers on our personal machines.

For my tests, I used pulp3-source-fedora30 vagrant box, initially set with
> 4GB, then I increased to 16GB, and it was not enough. I only was able to
> sync RHEL 7 when I increased the memory up to 23GB.

What about using some allocated openstack instances? Do we have access to
some powerful machines as a team? I have managed to spin up some instances
but when I tried to run pulp services I always stumbled upon some issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20191126/56e8348e/attachment.htm>

More information about the Pulp-dev mailing list