On Tue, Apr 30, 2024 at 3:56 AM Paul Harris <harris...@gmail.com> 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 jobs under the ram limit. > > Is there a clever set of flags or options in the v8 build system that would > automatically manage the number of jobs launched based on max RAM? > > Or do people simply learn from the past and set a max job limit for that > particular machine? > > Thanks, > Paul
It's been my experience that it's really only the link commands that consume lots of memory, not compilation, so I changed the $ld ninja variable from `c++` to `flock c++`, to stop them from running in parallel. -- -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/CAHQurc_dQQXeWc4oTjxs6neHjwH6O6tEt%3DajYON10rT-Z09J7Q%40mail.gmail.com.
