https://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-12-13T16:29:11ZPulpPulp - Story #9635: As a user, I can specify the desired maximum amount of memory usagehttps://pulp.plan.io/issues/9635?journal_id=777142021-12-13T16:29:11Zbmbouterbmbouter@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/77714/diff?detail_id=78176">diff</a>)</li></ul> Pulp - Story #9635: As a user, I can specify the desired maximum amount of memory usagehttps://pulp.plan.io/issues/9635?journal_id=777162021-12-13T16:54:22Zdalleydalley@redhat.com
<ul></ul><blockquote>
<p>Repos in pulp_rpm have had a single unit use more than 1.2G if I remember right, so if someone was syncing with 800 MB and we weren't careful to allow that unit to still flow through the pipeline we'd deadlock.....</p>
</blockquote>
<p>This is true but:</p>
<ol>
<li>the metadata is very messed up - 13 million duplicate "files" are listed for that package.</li>
<li>the postgresql maximum insert size is 1gb - so a single content unit exceeding that is a hard limitation regardless of anything else we do. Luckily I think that would be much much less frequent than an entire batch exceeding that limit, which I don't think we've ever seen happen either (but still a theoretical issue).</li>
</ol> Pulp - Story #9635: As a user, I can specify the desired maximum amount of memory usagehttps://pulp.plan.io/issues/9635?journal_id=786012022-01-17T16:45:05Zfao89
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/78601/diff?detail_id=79574">diff</a>)</li><li><strong>Status</strong> changed from <i>NEW</i> to <i>CLOSED - DUPLICATE</i></li></ul>