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 [thread overview]
Message-ID: <4531844.LvFx2qVVIh@wstn> (raw)
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.
next reply other threads:[~2023-09-18 12:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 12:00 Peter Humphrey [this message]
2023-09-18 12:59 ` [gentoo-user] Controlling emerges Jack
2023-09-18 13:44 ` Peter Humphrey
2023-09-18 13:48 ` Alan McKinnon
2023-09-18 16:03 ` Peter Humphrey
2023-09-18 16:13 ` Alan McKinnon
2023-09-18 17:54 ` Laurence Perkins
2023-09-18 22:44 ` William Kenworthy
2023-09-19 9:09 ` Peter Humphrey
2023-09-19 9:14 ` William Kenworthy
2023-09-19 9:37 ` Andreas Fink
2023-09-19 9:48 ` Peter Humphrey
2023-09-19 10:06 ` Rich Freeman
2023-09-19 10:13 ` William KENWORTHY
2023-09-18 17:59 ` Michael
2023-09-18 18:10 ` John Blinka
2023-09-18 18:18 ` Dale
2023-09-18 18:49 ` Rich Freeman
2023-09-19 12:28 ` Peter Humphrey
2023-09-20 22:06 ` Wol
2023-09-21 19:26 ` Laurence Perkins
2023-09-21 20:30 ` Tsukasa Mcp_Reznor
2023-09-22 1:13 ` Dale
2023-09-22 7:13 ` Michael
2023-09-22 10:07 ` Rich Freeman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4531844.LvFx2qVVIh@wstn \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox