Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Any best practices on minimizing system performance impact during emerging?

share|improve this question
up vote 3 down vote accepted

You could always use a different system to do the hard work using distcc:

share|improve this answer

you can set the variable PORTAGE_NICENESS in the file /etc/make.conf. it sums up a nice value to the emerge process, so that it has less priority on the system. for example:


the above line, in /etc/make.conf, will make portage increment 10 to the default nice value for that process (this will not set the nice value to 10, it will increment that value).

share|improve this answer

Apart from setting PORTAGE_NICENESS Use ionice to reduce impact on hard disk and reduce impact on user.

For example, for installing evolution I would do:

ionice -c3 emerge -av evolution
share|improve this answer

Try cpulimit. It limits cpu usage per process. So, you can tell emerge to use only 10% of your cpu resources.

share|improve this answer

@Mark's answer of using distcc sound sgood. Creating binary packages on another system and installing them on the high-load system might be an alternative approach to that one.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.