Date: Fri, 05 May 2023 19:32:37 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 271246] Kernel wired memory leak with repeated netstat Message-ID: <bug-271246-227-XZaTKuML9l@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-271246-227@https.bugs.freebsd.org/bugzilla/> References: <bug-271246-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=3D271246 --- Comment #2 from Dave Hayes <dave@jetcafe.org> --- So I am not a modern kernel dev. That being said, I currently data over time of: - anything in sysctl=20 - vmstat -z ... malloc buckets and UMA=20 I can fairly easily monitor almost any other value I can get with a command= , I just need to know what to monitor exactly (*all* of vmstat -m or vmstat -z = is probably not indicated and a waste of prometheus space). Now having said that, I did this: # vmstat -m | sort -k 3 ... bus-sc 139 5134K 12172=20 16,32,64,128,256,384,512,1024,2048,4096,8192,16384,32768,65536 iflib 813 6241K 833=20 16,64,128,512,1024,2048,8192,16384,32768,65536 solaris 113 18692K 233=20 16,32,64,128,256,512,1024,2048,4096,8192,65536 md_sectors 7260 29040K 7260 4096 devbuf 28312 46705K 35453=20 16,32,64,128,256,384,1024,2048,4096,8192,65536 pf_hash 5 51204K 5 2048 Type InUse MemUse Requests Size(s) Does this help any? --=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-271246-227-XZaTKuML9l>