From: Richard Freeman <rich@thefreemanclan.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] PORTAGE_NICENESS
Date: Thu, 14 Jun 2007 15:14:57 -0400 [thread overview]
Message-ID: <467193B1.2090308@thefreemanclan.net> (raw)
In-Reply-To: <4671877C.4080003@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
Mike Doty wrote:
> Mark Knecht wrote:
>> so do I actually use "+19"?
> the latter
Yes, a -19 would certainly make for a VERY unusable system!
I'm running a myth backend and I've found a few useful tricks:
1. Myth itself is run at nice -10. This was accomplished by editing
the init.d script.
2. Within myth tasks like commercial flagging are set to run niced.
You don't want myth spawning random tasks running at -10. Unfortunately
I can't find a way to do this with mythfilldb (short of writing a
wrapper script I suppose).
3. emerge schedutils and setup your block devices to use a scheduler
which respects IONICEness.
4. Run mythbackend using ionice -c 1 for realtime scheduling.
5. I usually run builds with ionice -c 3 nice -n 19. That results in
essentially no impact at all on system performance.
Oh, if you run cron jobs I'd avoid setting them to ionice -c 3. I had
problems with backups taking multiple days (instead of an hour) to run
that way. I guess it depends what your priorities are...
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3875 bytes --]
next prev parent reply other threads:[~2007-06-14 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 17:44 [gentoo-amd64] PORTAGE_NICENESS Mark Knecht
2007-06-14 17:57 ` Hemmann, Volker Armin
2007-06-14 18:06 ` Mark Knecht
2007-06-14 18:22 ` Mike Doty
2007-06-14 19:14 ` Richard Freeman [this message]
2007-06-17 9:41 ` Peter Humphrey
2007-06-17 10:36 ` Richard Freeman
2007-06-17 13:14 ` Peter Humphrey
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=467193B1.2090308@thefreemanclan.net \
--to=rich@thefreemanclan.net \
--cc=gentoo-amd64@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