From owner-freebsd-questions@freebsd.org Thu Nov 12 20:57:44 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9331FA2DF6E for ; Thu, 12 Nov 2015 20:57:44 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (jacobs.geeks.org [204.153.247.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6A7EB18A3 for ; Thu, 12 Nov 2015 20:57:44 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (localhost [127.0.0.1]) by after-clamsmtpd.geeks.org (Postfix) with ESMTP id B628C110237 for ; Thu, 12 Nov 2015 14:57:36 -0600 (CST) Received: by mail.geeks.org (Postfix, from userid 1003) id 95F48110234; Thu, 12 Nov 2015 14:57:36 -0600 (CST) Date: Thu, 12 Nov 2015 14:57:36 -0600 From: Doug McIntyre To: FreeBSD Questions Subject: Re: freebsd-update-server current repo location? Message-ID: <20151112205736.GB15217@geeks.org> References: <20151110174248.GB73663@geeks.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Nov 2015 20:57:44 -0000 On Wed, Nov 11, 2015 at 10:25:05AM -0500, Rick Miller wrote: > On Tue, Nov 10, 2015 at 12:42 PM, Doug McIntyre wrote: > > 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-server] >... > 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. 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 compiles are going on all around it, they use up a reasonable, expected amount of memory. Nothing that I wouldn't expect. But then poof, all of a sudden inactive memory starts growing, and growing. At only certain points in the cycle and in jumps and jerks upward. I was hoping the FreeBSD release team actually published their code someplace. 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.