Date: Mon, 10 Jul 2023 16:26:58 -0700 From: Pete Wright <pete@nomadlogic.org> To: freebsd-current@freebsd.org Subject: Re: huge amount laundry memory not being cleaned up Message-ID: <ae24e557-404e-808f-99b8-1f853f01e33b@nomadlogic.org> In-Reply-To: <E6F42F72-7812-41C6-AE83-6EB7BEEA79B9@yahoo.com> References: <E6F42F72-7812-41C6-AE83-6EB7BEEA79B9.ref@yahoo.com> <E6F42F72-7812-41C6-AE83-6EB7BEEA79B9@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/10/23 4:01 PM, Mark Millard wrote: > Pete Wright <pete_at_nomadlogic.org> wrote on > Date: Mon, 10 Jul 2023 19:35:26 UTC : > >> hi there, >> i've got a workstation running CURRENT that recently ran out of swap >> space. i killed the usual suspects (chrome, firefox and thunderbird) >> and noticed some odd behavior. while some memory did get freed up - >> after leaving the system idle for 4 hours i still have 14G or memory in >> the Laundry according to top. I also have noticed that very little data >> has paged out of swap (100MB out of 2G). >> >> >> i was wondering if there was a good way to determine what is in the >> laundry, > > I do not know how to get a breakdown of the laundry's usage. > But I'd expect, say, for example, top's resident memory > figures would count what is in the laundry as resident. > If correct, given the large laundry usage, may be some > resident figures would be suggestive? thanks Mark, so yea i poked around and didn't see any large consumers of resident memory. > >> or get diagnostic info on why it's not cleaning itself up? > > As I understand, it would take take one of the following > to change the status of the pages in the laundry in normal > operation: > > A) access to a page by a program, turning the page into > being in the active category. (It might go through > inactive to get there?) > > B) memory pressure leading to sending the page to the swap > in order to provide a page for a different use. > > Time alone does not contribute much as I understand. More > on-demand driven. Laundry is sort of "inactive but known > to be dirty" as I understand, in some respects just a > subset of inactive optimized for being closer to ready to > page out to swap space if needed. i'm doing a build world now since i'll need to reboot this box anyway, just to get everything up to date. interestingly enough i'm still pegged at 14G of laundry memory, and my 2G swap is %100 utilized. once the build world completes i'll do a double check and see if i can find any large consumers of resident memory which may lead me in the right direction. cheers! -pete -- Pete Wright pete@nomadlogic.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ae24e557-404e-808f-99b8-1f853f01e33b>