Date: Sat, 08 Feb 2020 09:31:17 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 241848] lib/googletest/gtest/tests: gmock-matchers_test.cc requires a pathological amount of memory to compile Message-ID: <bug-241848-227-0cIVJ3vLZf@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241848-227@https.bugs.freebsd.org/bugzilla/> References: <bug-241848-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241848 --- Comment #7 from Dave Evans <dave.evans55@googlemail.com> --- Thanks for all the useful comments. I've now set kern.maxswzone=3D42949664 which as far as I can tell from loader(8) is the value to be used for a theoretical 8GB of swap. I've configured 4GB of swap and rebooted. I then ran a stress test of running 3 compilations of the offending file simultaneously and monitored the system with top. Each job peaked at size: 1500M, resident: 600M swap usage peaked at 75% or 3054M The 3 jobs took 30 minutes to complete, as I would expect. There were no out of swap messages, which I good. The initial problem was that default kern.maxswzone was set way too low. It is not something I've ever tweaked before. It was probably not allowing more than 1GB or less of swap. This experience has taught me to read the output of dmesg more frequently and studiously. It also helps to read the man pages. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241848-227-0cIVJ3vLZf>