From nobody Sat Apr 23 16:35:49 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 639F9199AC03 for ; Sat, 23 Apr 2022 16:36:00 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from mailtransmit05.runbox.com (mailtransmit05.runbox.com [IPv6:2a0c:5a00:149::26]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4KlxjW5QWNz3N8X for ; Sat, 23 Apr 2022 16:35:59 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from mailtransmit03.runbox ([10.9.9.163] helo=aibo.runbox.com) by mailtransmit05.runbox.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1niIjd-002sYj-N3; Sat, 23 Apr 2022 18:35:49 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=iherebuywisely.com; s=selector1; h=Message-Id:In-Reply-To:Date:Subject:CC: To:From:MIME-Version:Content-Transfer-Encoding:Content-Type; bh=0o3gCun3I087c+kt9FPk/3N5v0HywcitnVjDx6tPmMM=; b=HDnIHYbVso3eGQpmEEzQNkCl+V wNWFYW9+bhUsyBoUYg9vtcH4m2ONjbhdNi+uvcLBH1lk4UJty6gKuXq7/ThaRc3Xafo/FRE0u1uNr jSBnCj8bI8sree4mKWN8PCD7N7lfUcWwOl2TzEHbPwG0ILburcogzBRmR6ebHRTahGt2EdYF0/wiL GJxht/Mx0wZNwYADmZ3YnJV4z8Av5W7a1WyoKBKZh/tDhATDlvFKmzUP6os9aBIlAseBHnT0ObrGM TQe6EErrdGHcIDcWwsllZN/OcB3HUmJpnQpAfMS8BWqdKLVM3BnFz+jE3vB14ZaNUbIQmme09JG14 f7ufBZhg==; Received: from [10.9.9.128] (helo=rmmprod06.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1niIjd-0007QK-60; Sat, 23 Apr 2022 18:35:49 +0200 Received: from mail by rmmprod06.runbox with local (Exim 4.86_2) (envelope-from ) id 1niIjd-0000mL-4y; Sat, 23 Apr 2022 18:35:49 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Received: from [Authenticated alias (650894)] by runbox.com with http (RMM6); Sat, 23 Apr 2022 16:35:49 GMT From: "Jeffrey Bouquet" To: "Pete Wright" CC: "freebsd-current" Subject: Re: Chasing OOM Issues - good sysctl metrics to use? Date: Sat, 23 Apr 2022 09:35:49 -0700 (PDT) X-RMM-Aliasid: 650894 X-Mailer: RMM6 In-Reply-To: Message-Id: X-Rspamd-Queue-Id: 4KlxjW5QWNz3N8X X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none ("invalid DKIM record") header.d=iherebuywisely.com header.s=selector1 header.b=HDnIHYbV; dmarc=none; spf=pass (mx1.freebsd.org: domain of jbtakk@iherebuywisely.com designates 2a0c:5a00:149::26 as permitted sender) smtp.mailfrom=jbtakk@iherebuywisely.com X-Spamd-Result: default: False [0.77 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.41)[-0.410]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a0c:5a00:149::26]; NEURAL_SPAM_SHORT(0.57)[0.569]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[iherebuywisely.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[iherebuywisely.com:~]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.01)[0.008]; R_DKIM_PERMFAIL(0.00)[iherebuywisely.com:s=selector1]; MLMMJ_DEST(0.00)[freebsd-current]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:50304, ipnet:2a0c:5a00::/29, country:NO]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[2a0c:5a00:149::26:from] X-ThisMailContainsUnwantedMimeParts: N On Fri, 22 Apr 2022 16:46:20 -0700, Pete Wright wrote: >=20 >=20 > On 4/22/22 13:39, tech-lists wrote: > > Hi, > > > > On Thu, Apr 21, 2022 at 07:16:42PM -0700, Pete Wright wrote: > >> hello - > >> > >> on my workstation running CURRENT (amd64/32g of ram) i've been running > >> into a scenario where after 4 or 5 days of daily use I get an OOM event > >> and both chromium and firefox are killed.=C2=A0 then in the next day o= r so > >> the system will become very unresponsive in the morning when i unlock = my > >> screensaver in the morning forcing a manual power cycle. > > > > I have the following set in /etc/sysctl.conf on a stable/13=20 > > workstation. Am using zfs with 32GB RAM. > > > > vm.pageout_oom_seq=3D120 > > vm.pfault_oom_attempts=3D-1 > > vm.pageout_update_period=3D0 > > > > Since setting these here, OOM is a rarity. I don't profess to exactly=20 > > know > > what they do in detail though. But my experience since these were set > > is hardly any OOM and big users of memory like firefox don't crash. >=20 > nice, i will give those a test next time i crash which will be by next=20 > thurs if the pattern continues. >=20 > looking at the sysctl descriptions: > vm.pageout_oom_seq: back-to-back calls to oom detector to start OOM > vm.pfault_oom_attempts: Number of page allocation attempts in page fault= =20 > handler before it triggers OOM handling > vm.pageout_update_period: Maximum active LRU update period >=20 > i could certainly see how those could be helpful.=C2=A0 in an ideal world= i'd=20 > find the root cause of the system lock-ups, but it would be nice to just= =20 > move on from this :) >=20 > cheers, > -p >=20 > --=20 > Pete Wright > pete@nomadlogic.org > @nomadlogicLA I don't know if it would help this discussion, but I installed security/pic= ocrypt and memory usage started going thru the roof*. Maybe that port could be use= d to test any fix found in this thread, iow if that port runs better without /wi= th some sysctl... if could be used for the issues discussed here so far.=20=20 * and I had to desintall. FWIW I had set the three vm listed above a sh= ort while prior.=20=