On Sat, Jan 25, 2020 at 03:31:16PM -0800, Steve Kargl wrote: > On Sat, Jan 25, 2020 at 02:09:29PM -0800, Cy Schubert wrote: > > On January 25, 2020 1:52:03 PM PST, Steve Kargl > > <[email protected]> wrote: > > >On Sat, Jan 25, 2020 at 01:41:16PM -0800, Cy Schubert wrote: > > >> > > >> It's not just poudeiere. Standard port builds of chromium, rust > > >> and thunderbird also fail on my machines with less than 8 GB. > > >> > > > > > >Interesting. I routinely build chromium, rust, firefox, > > >llvm and few other resource-hunger ports on a i386-freebsd > > >laptop with 3.4 GB available memory. This is done with > > >chrome running with a few tabs swallowing a 1-1.5 GB of > > >memory. No issues. > > > > Number of threads makes a difference too. How many core/threads does your > > laptop have? > > 2 cores. > > > Reducing number of concurrent threads allowed my builds to complete > > on the 5 GB machine. My build machines have 4 cores, 1 thread per > > core. Reducing concurrent threads circumvented the issue. > > I use portmaster, and AFIACT, it uses 'make -j 2' for the build. > Laptop isn't doing too much, but an update and browsing. It does > take a long time especially if building llvm is required. >
In thinking about this and recalling watching top(1) during my last firefox rebuild, it seems that the compiler can use 0.5-1 GB when compiling files. I see how doing a parallel build with "-j NCPU" could stress a <4 GB system. -- Steve _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[email protected]"
