From: "Arttu V." <arttuv69@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: May be OT: recommended niceness settings for Portage while using Gnome?
Date: Fri, 21 Aug 2009 21:01:52 +0300 [thread overview]
Message-ID: <fecdbac60908211101v15c47d91g85a33206e292a4d6@mail.gmail.com> (raw)
In-Reply-To: <h6mmnn$f1b$1@ger.gmane.org>
On 8/21/09, Nikos Chantziaras <realnc@arcor.de> wrote:
> However, also very important is "I/O nice". Setting an ionice
> value of "idle" will result in portage not blocking your other
> applications whey they need to do disk I/O:
>
> PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}"
Yes, as it is a laptop, it's likely to have a slow 5400 RPM disk. I
have a nearly same-spec old laptop (~5.5 yo, P4m 2.2GHz, 256+256MB
RAM), but I haven't had much trouble with portage emerges on it. Only
when something big is due to in the I/O (lots of swapping due to the
small RAM, kernel sources being unpacked, 100+ MB file transfer over
from LAN etc) has there been slowness which has been annoying.
Given the open nature of OP's question I'm also offering
MAKEOPTS="-j1". It's not really that much a "speed optimization" (on
the contrary?), but another way to try to keep the disk I/O and CPU to
yourself -- even if the compiles will take a bit longer on the
background. (And this ionice thing I got to try as well on that old
clunker, thanks for the tip!)
--
Arttu V.
next prev parent reply other threads:[~2009-08-21 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 16:54 [gentoo-user] May be OT: recommended niceness settings for Portage while using Gnome? James Homuth
2009-08-21 17:02 ` Paul Hartman
2009-08-21 17:49 ` [gentoo-user] " Nikos Chantziaras
2009-08-21 18:01 ` Arttu V. [this message]
2009-08-21 23:58 ` meino.cramer
2009-08-22 0:12 ` Dale
2009-08-22 0:13 ` Paul Hartman
2009-08-22 17:06 ` James Homuth
2009-08-23 5:19 ` Paul Hartman
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=fecdbac60908211101v15c47d91g85a33206e292a4d6@mail.gmail.com \
--to=arttuv69@gmail.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