From: Uwaysi Bin Kareem <uwaysi.bin.kareem@paradoxuncreated.com>
To: linux-kernel@vger.kernel.org
Subject: re: Optimizing scheduling policies for Ubuntu (desktop), for low-jitter.
Date: Sat, 20 Oct 2012 01:27:57 +0200 [thread overview]
Message-ID: <op.wmf8svxp6426ze@localhost.localdomain> (raw)
In-Reply-To: <op.wmbjpvqe6426ze@localhost.localdomain>
Not many are discussing this.
So odd since an overloaded computer, looks like a computer with jitter. So
removing jitter = higher performance.
I changed X to nice -20 though instead. It is hard to predict jitter, and
maybe some measure of fairness is good.
Still daemons wouldn`t mind running sequentially as simple round robin,
or? I would like to see a lowpriority round-robin, and not just the
realtime one. Maybe a modification on "idle" pri. I just want to know
daemons can be made transparent to jitter. Or atleast some measure of
fairness to sequentialness that keeps the lowest jitter.
Anyone following ? :)
Peace Be With You.
prev parent reply other threads:[~2012-10-19 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 10:35 Realtime threads for less jitter (w/ X)? Uwaysi Bin Kareem
2012-10-18 9:36 ` Optimizing scheduling policies for Ubuntu (desktop), for low-jitter Uwaysi Bin Kareem
2012-10-19 23:27 ` Uwaysi Bin Kareem [this message]
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=op.wmf8svxp6426ze@localhost.localdomain \
--to=uwaysi.bin.kareem@paradoxuncreated.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).