Date: Mon, 11 Jun 2012 23:41:57 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: alc@freebsd.org Cc: Garrett Cooper <yanegomi@gmail.com>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: 10-CURRENT and swap usage Message-ID: <20120611204157.GG2337@deviant.kiev.zoral.com.ua> In-Reply-To: <CAJUyCcP0ry_Mt-KKUGiaDmuUm8o1emc2RXgjuibBwOpTWuaQ5g@mail.gmail.com> References: <6809F782-1D1F-4773-BAC5-BC3037C58B87@gmail.com> <CAJUyCcP0ry_Mt-KKUGiaDmuUm8o1emc2RXgjuibBwOpTWuaQ5g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--OFj+1YLvsEfSXdCH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 11, 2012 at 01:23:03PM -0500, Alan Cox wrote: > On Sat, Jun 9, 2012 at 9:26 PM, Garrett Cooper <yanegomi@gmail.com> wrote: >=20 > > I build out of my UFS-only VM in VMware Fusion from time to time, > > and it looks like there's a large chunk of processes that are swapped o= ut > > when doing two parallel builds: > > > > last pid: 27644; load averages: 2.43, 0.94, 0.98 > > > > up 1+15:06:06 19:20:48 > > 79 processes: 4 running, 75 sleeping > > CPU: 77.3% user, 0.0% nice, 22.7% system, 0.0% interrupt, 0.0% idle > > Mem: 407M Active, 186M Inact, 208M Wired, 24M Cache, 110M Buf, 145M Free > > Swap: 1024M Total, 267M Used, 757M Free, 26% Inuse > > > > I know that some minor changes have gone in in the past couple > > months to change when swapping and page ins/outs would occur, but I was > > wondering if this behavior was intended; I'm finding it a bit bizarre t= hat > > there's ~150MB free, ~180MB inactive, and 267MB swapped out as previous > > experience has dictated that swap is basically untouched except in extr= eme > > circumstances. > > >=20 > I can't think of any change in the past couple months that would have this > effect. Specifically, I don't recall there having been any change that > would make the page daemon more (or less aggressive) in laundering dirty > pages. >=20 > Keep in mind that gcc at higher optimization levels can and will use a lot > of memory, i.e., hundreds of megabytes. The new jemalloc in debugging mode uses much more anonymous memory now. And since typical compiler process is relatively short-lived, the picture posted probably related to some memory hog recently finished a run. --OFj+1YLvsEfSXdCH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk/WWBUACgkQC3+MBN1Mb4jBkwCfXLda4TAX7xQZGnilQMxOyQRz e/IAoKSWvYN+m3azj8GNGyBZxh1AcYcd =wErp -----END PGP SIGNATURE----- --OFj+1YLvsEfSXdCH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120611204157.GG2337>