https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230454
--- Comment #8 from Mark Millard <marklmi26-f...@yahoo.com> --- I'll note that folks have been reporting problems with 1 GiByte machines for -j1 buildworld's based on the compilation of gmock-matchers_test.cc . An example is: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241848 It might be better to make such the base so the information is not as old as here: declare older submittals as duplicates of the modern information example? (llvm materials have grown as well.) Head has also added an paging/swapping I/O related OOM criteria (that was temporarily broken a littel while back). I've not used a 1 GiBYTe context but I use two settings, one of which is for avoiding I/O related kills happening as easilly: # # Delay when persistent low free RAM leads to # Out Of Memory killing of processes: vm.pageout_oom_seq=120 # # For plunty of swap/paging space (will not # run out), avoid pageout delays leading to # Out Of Memory killing of processes: vm.pfault_oom_attempts=-1 I do this on 2 GiByte+ contexts to better avoid OOM kills. vm.pfault_oom_attempts is head-only last I knew but vm.pageout_oom_seq is much older. Some folks have used much larger vm.pageout_oom_seq values. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"