Date: Fri, 13 Nov 2015 10:39:27 +0100 From: Fabian Keil <freebsd-listen@fabiankeil.de> To: Doug McIntyre <merlyn@geeks.org> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: freebsd-update-server current repo location? Message-ID: <20151113103927.1c3654e8@fabiankeil.de> In-Reply-To: <20151112205736.GB15217@geeks.org> References: <20151110174248.GB73663@geeks.org> <CAHzLAVE4Fu%2B%2BSvoELuHJ5EefRx==g60zRtJntLqDTU6KLt%2B9xQ@mail.gmail.com> <20151112205736.GB15217@geeks.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/bO8r8YCZ78T2Qnm2eLEXctc Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Doug McIntyre <merlyn@geeks.org> wrote: > On Wed, Nov 11, 2015 at 10:25:05AM -0500, Rick Miller wrote: > > On Tue, Nov 10, 2015 at 12:42 PM, Doug McIntyre <merlyn@geeks.org> wrot= e: =20 > > > But I'm having problems during the big build with the machine chowing > > > memory to inactive memory and eventually running out of swap. .. > > > So I was looking for the current repo of this code? [freebsd-update-s= erver] =20 > >...=20 > > A recent build consumed approximately 12GB of swap on a VM with 8 CPUs = and > > 32GB RAM. I chocked the resource utilization up to the fact that the VM > > did not have enough RAM. Building FreeBSD source, especially multiple > > instances of it, is likely to be much more memory intensive than the VM= had > > in capacity. =20 >=20 > Thats the thing though, during the build, it doesn't really take all that= much > memory, it is mostly doing a ton of disk activity, while the multiple com= piles > are going on all around it, they use up a reasonable, expected amount of = memory.=20 > Nothing that I wouldn't expect.=20 >=20 > But then poof, all of a sudden inactive memory starts growing, and growin= g. > At only certain points in the cycle and in jumps and jerks upward.=20 >=20 > I was hoping the FreeBSD release team actually published their code somep= lace. >=20 > But at least it sounds like the same as I obvserved happens to others. I = wasn't > going to bother giving huge amounts of RAM to the build machine, but I can > at least put in a couple swap files or whatever to eat all this inactive > RAM swapped out during the process easily enough. If you are using ZFS, you may want to take a look at the various patches at: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D187594 Fabian --Sig_/bO8r8YCZ78T2Qnm2eLEXctc Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlZFr9EACgkQBYqIVf93VJ0pfACfYNnyGNvrTkzG4at/zZgqNAQr aTMAniy7n8L8JkSMkTaDdBRuWd+44BSM =VCOi -----END PGP SIGNATURE----- --Sig_/bO8r8YCZ78T2Qnm2eLEXctc--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151113103927.1c3654e8>