From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-201827-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id 4FF73158089
	for <garchives@archives.gentoo.org>; Mon, 18 Sep 2023 12:00:09 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id BB8512BC04C;
	Mon, 18 Sep 2023 12:00:03 +0000 (UTC)
Received: from smarthost01c.ixn.mail.zen.net.uk (smarthost01c.ixn.mail.zen.net.uk [212.23.1.22])
	(using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 2DD282BC01D
	for <gentoo-user@lists.gentoo.org>; Mon, 18 Sep 2023 12:00:02 +0000 (UTC)
Received: from [82.69.80.10] (helo=wstn.localnet)
	by smarthost01c.ixn.mail.zen.net.uk with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.90_1)
	(envelope-from <peter@prh.myzen.co.uk>)
	id 1qiCv3-0007Hj-6d
	for gentoo-user@lists.gentoo.org; Mon, 18 Sep 2023 12:00:01 +0000
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Controlling emerges
Date: Mon, 18 Sep 2023 13:00:00 +0100
Message-ID: <4531844.LvFx2qVVIh@wstn>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Originating-smarthost01c-IP: [82.69.80.10]
Feedback-ID: 82.69.80.10
X-Archives-Salt: ac236ead-cb22-486a-8f03-bc22dbc78652
X-Archives-Hash: c8d8bfc52498ae11ca67d9102c418f36

Hello list,

We've had a few discussions here on how to balance the parameters to emerge 
to make the most of the resources available. Here's another idea:

One the one hand, big jobs should be able to use the maximum CPU 
performance and RAM capacity, but on the other we don't want to flood the 
system.

Therefore, I think it would be useful to be able to specify in env and 
package.env that a job should be run on its own - if any other emerge jobs are 
scheduled, wait until they're finished. Combine that with a specific MAKEOPTS, 
and we'd have a more flexible deployment of resouces.

Is this feasible? What have I not thought of?

-- 
Regards,
Peter.