Re: [gentoo-user] Controlling emerges

[Michael]

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 pileor 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 
> > 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.

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Controlling emerges

[Rich Freeman]

On Thu, Sep 21, 2023 at 9:13 PM Dale  wrote:
>
> 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?

Sure, if a relevant topic comes up and I'm aware of it.  However, I
doubt this setting is going to do much that nice doesn't already do.

The original focus seemed to be on memory use, and niceness will not
have any impact on the memory use of a build.  The only thing that
will is reducing the number of parallel jobs.  There really isn't any
way to get portage to regulate memory use short of letting it be
killed (which isn't helpful), maybe letting it being stopped when
things get out of hand (which will help as the memory could at least
be swapped, but the build might not be salvageable without jumping
through a lot of hoops), or if the package maintainer provides some
kind of hinting to the package manager so that it can anticipate how
much memory it will use.  Otherwise trying to figure out how much
memory a build system will use without just trying it is like solving
the halting problem.

-- 
Rich