[Webkit-unassigned] [Bug 227128] Build consumes too much memory on 8gb M1

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon May 2 16:51:55 PDT 2022


https://bugs.webkit.org/show_bug.cgi?id=227128

Elliott Williams <emw at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |emw at apple.com

--- Comment #2 from Elliott Williams <emw at apple.com> ---
I'm not sure if there is much we can do about the underlying issue of how heavy our compile tasks are.

In my most recent testing, on a 20-core Mac Studio, the system peaked at 32GB memory usage during a build. For comparison, on a 24-core / 16 GB linux system I recently built WebKitGTK on, I had to limit the number of concurrent jobs to 14 to avoid running out of memory.

On Apple platforms, we can control the amount of parallelism, but only (easily) from build scripts. I'm not convinced we should do this project-wide, because:

- On systems like yours, building from Make would magically be faster than building the same scheme/targets in Xcode.
- Less parallelism would be available for non-memory-intensive parts of the build, like copying files and generating code.


That said, you can customize it yourself via defaults:

    defaults write com.apple.dt.Xcode IDEBuildOperationMaxNumberOfConcurrentCompileTasks 6

or

    make ... ARGS="-IDEBuildOperationMaxNumberOfConcurrentCompileTasks 6"

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220502/58ce8145/attachment.htm>


More information about the webkit-unassigned mailing list