1 |
Mark Haney wrote: |
2 |
> I've been extremely busy lately and have let my updates get way behind. |
3 |
> Part of that is my need to keep kde-libs-3.5 on my system for K3b, etc, |
4 |
> part of that is just too much else to do. |
5 |
> |
6 |
> The problem I've encountered is when I try to do an update while I'm |
7 |
> working, my system can slow to a crawl, on a big compile usually. I've |
8 |
> tried using nice to manage how much CPU the compile gets so I can |
9 |
> function while it's building, but it's killing the output so I can't see |
10 |
> what's going on. |
11 |
> |
12 |
> Is there another way to use nice, or to fix that problem? Or another |
13 |
> way to manage CPU usage during an emerge? |
14 |
|
15 |
You can also "ionice" portage in addition to just "nice". I'm using |
16 |
"nice 19" and "ionice idle". To achieve this, in make.conf: |
17 |
|
18 |
PORTAGE_NICENESS=19 |
19 |
PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}" |
20 |
|
21 |
On my system, "ionice" makes a bigger difference than "nice" (I'd rather |
22 |
say that "nice" doesn't result in any noticeable effect at all.) |
23 |
|
24 |
"man ionice" will give you some info about it does. In short, it does |
25 |
for I/O operations what "nice" does for CPU time. |