From owner-freebsd-hackers@FreeBSD.ORG Wed Oct 31 21:29:52 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F83E5A3; Wed, 31 Oct 2012 21:29:52 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id BF5A78FC0C; Wed, 31 Oct 2012 21:29:50 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n9so2435893oag.13 for ; Wed, 31 Oct 2012 14:29:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gAK3CX9FIOWj6vDxQEy6gn/VExqCLy83J7kW0lU1j7Q=; b=cRg1ZlKa26k2NEe2R2q7kLD3M/Trtb8Y+A2IIu+uah0k5T1cQfIqvPRgfKJW8WL2Yb mY9Lw/vlJiNDWF64rTgIsstx2+breqtVRnMB8tMBVCp7ffNQhI7qKqVpBpNK84Y64zVE XLwrmxbd6P1ORLE7UKzjkMUUrW9fNLfWq08ViN9g5Ycgicg/6xBMX1zciHGwm5I6dmMy UuVFhbNwQ4LNTSC5KzRmt/zanT1QCsXZsyxV82BjzZl5J96NLape6+RwRS8uq61R7i+n wuIUj0h52e7+PbuEZequFM1J9S4Qy+rIzhdmUjpf8VcWMY8JGNSewu40EQARRTZECqzY 13Hg== MIME-Version: 1.0 Received: by 10.60.28.42 with SMTP id y10mr5195036oeg.24.1351718990114; Wed, 31 Oct 2012 14:29:50 -0700 (PDT) Received: by 10.76.143.33 with HTTP; Wed, 31 Oct 2012 14:29:50 -0700 (PDT) In-Reply-To: References: <509182DA.8070303@mu.org> <20121031204152.GK3309@server.rulingia.com> Date: Wed, 31 Oct 2012 14:29:50 -0700 Message-ID: Subject: Re: make -jN buildworld on < 512MB ram From: Garrett Cooper To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: Alfred Perlstein , hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2012 21:29:52 -0000 On Wed, Oct 31, 2012 at 1:44 PM, Adrian Chadd wrote: > On 31 October 2012 13:41, Peter Jeremy wrote: > >> Another, more involved, approach would be for the scheduler to manage >> groups of processes - if a group of processes is causing memory >> pressure as a whole then the scheduler just stops scheduling some of >> them until the pressure reduces (effectively swap them out). (Yes, >> that's vague and lots of hand-waving that might not be realisable). > > Well, does the compiler actually need that much memory? :) For calculating SSAs, directed graphs, and when dealing with larger optimization levels -- sadly, yes it can. -Garrett