On 2020-Jan-27, at 10:20, Cy Schubert <Cy.Schubert at cschubert.com> wrote: > On January 27, 2020 5:09:06 AM PST, Cy Schubert <Cy.Schubert_at_cschubert.com> wrote: >>> . . . >> >> Setting a lower arc_max at boot is unlikely to help. Rust was building >> on >> the 8 GB and 5 GB 4 core machines last night. It completed successfully >> on >> the 8 GB machine, while using 12 MB of swap. ARC was at 1307 MB. >> >> On the 5 GB 4 core machine the rust build died of OOM. 328 KB swap was >> used. ARC was reported at 941 MB. arc_min on this machine is 489.2 MB. > > MAKE_JOBS_NUMBER=3 worked building rust on the 5 GB 4 core machine. ARC is at 534 MB with 12 MB swap used. If you increase vm.pageout_oom_seq to, say, 10 times what you now use, does MAKE_JOBS_NUMBER=4 complete --or at least go notably longer before getting OOM behavior from the system? (The default is 12 last I checked. So that might be what you are now using.) Have you tried also having: vm.pfault_oom_attempts="-1" (Presuming you are not worried about actually running out of swap/page space, or can tolerate a deadlock if it does run out.) This setting presumes head, not release or stable. (Last I checked anyway.) It would be interesting to know what difference those two settings together might make for your context: it seems to be a good context for testing in this area. (But you might already have set them. If so, it would be good to report the figures in use.) Of course, my experiment ideas need not be your actions. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)Received on Mon Jan 27 2020 - 19:36:37 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:22 UTC