|Summary:||Rework $PORTAGE_NICENESS and $PORTAGE_IONICE_COMMAND|
|Product:||Portage Development||Reporter:||xpue <r9ku1q>|
|Component:||Unclassified||Assignee:||Portage team <dev-portage>|
|Severity:||normal||CC:||aperion, gentoo, sam|
|Package list:||Runtime testing required:||---|
Description xpue 2015-11-10 21:02:31 UTC
Currently i have script as my PORTAGE_IONICE_COMMAND which sets cpu scheduling policy to idle, and scheduling class also to idle. >chrt --idle --pid 0 $1 >ionice --class 3 --pid $1 I think PORTAGE_NICENESS and PORTAGE_IONICE_COMMAND are not very well suited to what they suppoosed to do, because first only sets niceness but not scheduling class, and second does not allow to run multiple commands without use of external script. Reproducible: Always
Comment 1 aperion 2020-11-07 16:30:23 UTC
I just recently noticed that PORTAGE_NICENESS was not working anymore. Apparently because of the autogroup feature. I was not able to make it work using autogroup. Now I aliased emerge to "chrt --idle 0 emerge", which is effective. It would be nice if portage could do that via configuration, potentially replacing the old variant. I think this could improve the user experience greatly. Because without this, I could not even watch video streams while emerge was active.
Comment 2 Sam James 2022-03-01 05:13:28 UTC
(In reply to aperion from comment #1) > I just recently noticed that PORTAGE_NICENESS was not working anymore. > Apparently because of the autogroup feature. I was not able to make it work > using autogroup. Now I aliased emerge to "chrt --idle 0 emerge", which is > effective. FWIW, this was addressed in bug 777492. As for the original issue, yeah, it sometimes feels like we should at least ship with an example commented out to easily reduce Portage's impact on system responsiveness (I'm not yet sure how we should best refactor the variables though). I've created a wiki page w/ my settings too for now: https://wiki.gentoo.org/wiki/User:Sam/PORTAGE_NICENESS.