public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Controlling emerges
Date: Fri, 22 Sep 2023 08:13:41 +0100	[thread overview]
Message-ID: <4835574.GXAFRqVoOG@rogueboard> (raw)
In-Reply-To: <62114b10-8329-b11a-17b1-e4b49b6d581a@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]

On Friday, 22 September 2023 02:13:08 BST Dale wrote:
> Tsukasa Mcp_Reznor wrote:
> > So I feel I should add my own 2 cents to the pile....or possibly 25 cents
> > due to inflation.
> > 
> > 
> > PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}"
> > PORTAGE_SCHEDULING_POLICY="idle"
> > 
> > Those 2 together in make.conf have had a noticeable effect on multitasking
> > for me.  I still wouldn't recommend allocating all of your cores to
> > emerge, but emerging with idle priority keeps your tasks a little higher
> > up in the mix.
> > 
> > ________________________________________
> > From: Laurence Perkins <lperkins@openeye.net>
> > Sent: Thursday, September 21, 2023 3:26 PM
> > To: gentoo-user@lists.gentoo.org
> > Subject: RE: [gentoo-user] Controlling emerges
> 
> I had the first one, little different for my rig, but I added the second
> one just now.  I'll be testing this tomorrow or Sunday, depending on
> packages, maybe both.  lol 
> 
> Sometimes I wish they would announce when they add features.  Rich, you
> frequent this list.  If you hear of something new, could you post it? 
> This may not be NEW but it is new to me.  No idea when it got added. 
> 
> Dale
> 
> :-)  :-) 

Loads of tweaks are described here, which I wasn't aware of:

https://wiki.gentoo.org/wiki/Portage_niceness

As well as the man pages for make.conf and sched.  I'm not sure what default 
values are, if these variables are not set in make.conf.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-09-22  7:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 12:00 [gentoo-user] Controlling emerges Peter Humphrey
2023-09-18 12:59 ` 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 [this message]
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=4835574.GXAFRqVoOG@rogueboard \
    --to=confabulate@kintzios.com \
    --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