Ok thanks all for your suggestions!
On Wednesday, May 1, 2024 at 12:15:32 AM UTC+8 seth.b...@microsoft.com
wrote:
> If you're running out of memory during C++ compilation tasks, I don't have
> any useful suggestions beyond what you've already done. If you only run out
> of memory while
If you're running out of memory during C++ compilation tasks, I don't have
any useful suggestions beyond what you've already done. If you only run out
of memory while running multiple linking tasks, you could try setting the
gn argument `concurrent_links` to a smaller value than the default.
I don't think there's a built-in way to take RAM into account. ninja and
autoninja both look at the number of CPU cores/threads.
FWIW, with 2 GiB memory per thread (so e.g. 16 GiB on a 4C/8T CPU), I
haven't had OOM issues on a fairly wide range of machines from laptops to
workstations.
On Tue, Apr 30, 2024 at 3:56 AM Paul Harris wrote:
>
> Hi,
>
> I'd like to run Ninja build with as many jobs as I have CPUs.
> However, some of the build jobs require a lot of RAM (especially for Debug
> builds), so I have to reduce the number of jobs artificially, just to keep
> the number of
Hi,
I'd like to run Ninja build with as many jobs as I have CPUs.
However, some of the build jobs require a lot of RAM (especially for Debug
builds), so I have to reduce the number of jobs artificially, just to keep
the number of jobs under the ram limit.
Is there a clever set of flags or
