From nobody Fri Apr 22 23:46:20 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 982121A2575F for ; Fri, 22 Apr 2022 23:46:22 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [66.165.241.226]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KlWJY6SFNz3HYj for ; Fri, 22 Apr 2022 23:46:21 +0000 (UTC) (envelope-from pete@nomadlogic.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1650671180; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=lwFcF9CSNVI8kts/g99F9U++r1AwJNxN6fEY7puoKTg=; b=WR8W9EFNSSydpPpx5TTrx29aj3f+9YJjmzCwXjjxteO37wgGXHcuzYo8Sno8Fsxhhpbi9B mB/5wHWZKbd8/pzQNa2QHb+8By5hE1Dcm/rAm5SDZvbrfS+LGF8aDF418YPONVMWzWql0D Ncex6S8pfwCD7WESPC3ldM0tjK5l0Go= Received: from [192.168.1.160] (cpe-24-24-168-214.socal.res.rr.com [24.24.168.214]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 983dfdbd (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Fri, 22 Apr 2022 23:46:20 +0000 (UTC) Message-ID: Date: Fri, 22 Apr 2022 16:46:20 -0700 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Subject: Re: Chasing OOM Issues - good sysctl metrics to use? Content-Language: en-US To: freebsd-current@freebsd.org References: From: Pete Wright In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4KlWJY6SFNz3HYj X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=nomadlogic.org header.s=04242021 header.b=WR8W9EFN; dmarc=pass (policy=quarantine) header.from=nomadlogic.org; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 66.165.241.226 as permitted sender) smtp.mailfrom=pete@nomadlogic.org X-Spamd-Result: default: False [-1.08 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[nomadlogic.org:s=04242021]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.92)[0.919]; DKIM_TRACE(0.00)[nomadlogic.org:+]; DMARC_POLICY_ALLOW(-0.50)[nomadlogic.org,quarantine]; 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:29802, ipnet:66.165.240.0/22, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N 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.  then in the next day or 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 > workstation. Am using zfs with 32GB RAM. > > vm.pageout_oom_seq=120 > vm.pfault_oom_attempts=-1 > vm.pageout_update_period=0 > > Since setting these here, OOM is a rarity. I don't profess to exactly > 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. nice, i will give those a test next time i crash which will be by next thurs if the pattern continues. 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 handler before it triggers OOM handling vm.pageout_update_period: Maximum active LRU update period i could certainly see how those could be helpful.  in an ideal world i'd find the root cause of the system lock-ups, but it would be nice to just move on from this :) cheers, -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA