<div dir="ltr">Since this is a relatively common issue, I decided to respond via blog post:<div><br></div><div><a href="http://pulpproject.org/2017/02/17/why-does-copy-use-lots-of-memory/">http://pulpproject.org/2017/02/17/why-does-copy-use-lots-of-memory/</a><br></div><div><br></div><div>Michael</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 16, 2017 at 4:22 PM, Richard Gray <span dir="ltr"><<a href="mailto:richard.gray@smxemail.com" target="_blank">richard.gray@smxemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 2017-02-17 10:07, Richard Gray wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
given size? This VM has 8GB, and I could add more, but it seems faintly<br>
ridiculous that it should be required.<br>
</blockquote>
<br></span>
I increased the size of the VM to 16GB, which allowed the job to complete. The celery worker processes peak at around 7.2GB.<br>
<br>
I would still like to know if there's a fix or workaround that doesn't involve throwing memory at the problem.<br>
<br>
Thanks,<span class="HOEnZb"><font color="#888888"><br>
-- <br>
Richard<br>
______________________________<wbr>______________________________<wbr>_________________<br>
<br>
This email has been filtered by SMX. For more info visit <a href="http://smxemail.com" rel="noreferrer" target="_blank">http://smxemail.com</a><br>
______________________________<wbr>______________________________<wbr>_________________<br>
<br>
______________________________<wbr>_________________<br>
Pulp-list mailing list<br>
<a href="mailto:Pulp-list@redhat.com" target="_blank">Pulp-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-list</a><br>
</font></span></blockquote></div><br></div>