Date: Fri, 13 Sep 2019 09:24:44 -0700 From: bob prohaska <fbsd@www.zefox.net> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Don Lewis <truckman@FreeBSD.org>, Mark Johnston <markj@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>, kib@freebsd.org, bob prohaska <fbsd@www.zefox.net> Subject: Re: spurious out of swap kills Message-ID: <20190913162444.GA28886@www.zefox.net> In-Reply-To: <20190913055332.GN2559@kib.kiev.ua> References: <tkrat.84b3295682c83162@FreeBSD.org> <20190913000635.GG8397@raichu> <tkrat.1a0e98a230c1a223@FreeBSD.org> <20190913055332.GN2559@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Not sure this is relevant, but in compiling chromium on a Pi3 with 6 GB of swap the job completed successfully some months ago, with peak swap use around 3.5 GB. The swap layout was sub-optimal, with a 2 GB partition combined with a 4 GB partition. A little over 4GB total seems usable. A few days ago the same attempt stopped with a series of OOMA kills, but in each case simply restarting allowed the compile to pick up where it left off and continue, eventually finishing with a runnable version of chromium. In this case swap use peaked a little over 4 GB. Might this suggest the machine isn't freeing swap in a timely manner? Thanks for reading, bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190913162444.GA28886>