We must take care not to bring the Shepherd VM down by OOMs or excessive swapping.
If a project creation/update would create a situation where max memory usage (calculated as a sum of all project runtime memory usage + top x build memory usage, where x depends on the number of builders) would overlap memory available to shepherd, then such a change will be rejected with an informative exception.
We must take care not to bring the Shepherd VM down by OOMs or excessive swapping.
If a project creation/update would create a situation where max memory usage (calculated as a sum of all project runtime memory usage + top x build memory usage, where x depends on the number of builders) would overlap memory available to shepherd, then such a change will be rejected with an informative exception.