Re: FYI; 14.3: A discord report of Wired Memory growing to 17 GiBytes over something like 60 days; ARC shrinks to, say, 1942 MiBytes

On Tue, Aug 12, 2025 at 06:50:49PM +0930, beldin@beldin.org wrote:
> On Tue, 12 Aug 2025 16:10:32 +0930
> Darrin Smith <beldin@beldin.org> wrote:
> 
> > On Mon, 11 Aug 2025 13:18:47 -0700
> > Mark Millard <marklmi@yahoo.com> wrote:
> > 
> > > Context reported by notafet :
> > > 
> > > 14.3-RELEASE-p2 GENERIC on amd64 with ZFS in use
> > > 
> > > RAM:  looks to be 24 GiBytes, not explicitly mentioned
> > > SWAP: 8192 MiBytes
> > > (From using the image of top's figures.)
> > > 
> > > Wired:       17 GiBytes 
> > > ARC Total: 1942 MiBytes
> > > 
> > > SWAP used: 1102 MiBytes
> > > 
> > > The link to the storage channel's message is:
> > > 
> > > https://discord.com/channels/727023752348434432/757305697527398481/1404367777904463914  
> > 
> > As of a couple of weeks ago update to latest -CURRENT at the time
> > (from previous build of a couple of months ago) I've been
> > experiencing a similar but worse case of this. 64G ram on the
> > machine, given 2 days it will run out of memory and start killing off
> > process, with Wired Memory growing the whole time (at the rate of
> > about 1G every 5s at some points). ZFS ARC never passes more then 20G
> > the whole time. 
> 
> Correction here, 1*M* every 5s...It lasts a day or two at least :D
> 
> > For example right now top reports:
> > 
> > Mem: 1031M Active, 14G Inact, 241M Laundry, 45G Wired, 404M Buf, 2157M
> > Free ARC: 17G Total, 2883M MFU, 11G MRU, 256K Anon, 167M Header, 3025M
> > 
> > (Time for another reboot or it'll have killed things off when I get
> > home from work in 8 hours)
> > 
> > I'm still trying to pin down what exactly it's related too hence. I've
> > pretty much elimiated ZFS being the issue and a large poudriere ports
> > build or a full build world doesn't seem to push it up. It seems to be
> > more closely related to how many graphical things are open at once.
> > I've tried drm-61-kmod and drm-66-kmod for my amdgpu polaris 10 video
> > card but that seems to make no difference. Next thing I was planning
> > on trying was switch to the vesa driver and see if that reduces
> > things, but these things take time to fit in around everything else.
> > 
> > Darrin
> 
> Well removing amdgpu altogether made no difference. Still climbing
> Wired (I only suspected it was that because it climbed sharpest when I
> was logged in). However I have noticed that there is no noticable growth
> when using a local login (on ZFS), it's only the NFS based users that
> seem to be causing the wired to climb sharply. 

Start looking at differences in periodic shots of vmstat -z and vmstat -m.
It would not catch direct page allocators.