From: Uwaysi Bin Kareem <uwaysi.bin.kareem@paradoxuncreated.com>
To: linux-kernel@vger.kernel.org
Subject: Optimizing scheduling policies for Ubuntu (desktop), for low-jitter.
Date: Thu, 18 Oct 2012 11:36:04 +0200 [thread overview]
Message-ID: <op.wmdbmeh66426ze@localhost.localdomain> (raw)
In-Reply-To: <op.wmbjpvqe6426ze@localhost.localdomain>
Hi.
I have made a little script, optimizing Ubuntu abit. If you have any good
and relevant information, reasonable arguments, please post them.
Do note this script is something I have quickly made, and can probably be
improved. Feedback from experienced desktop-optimizers is appreciated. The
point is to get waiting due to suboptimal policies out. Making the desktop
as responsive as it can be.
What it does for the time being, is set X to realtime, so that it`s
singlethreadedness does not become a performance bottleneck. And all
daemons to idle pri. Also idle pri, would ofcourse work best, if they are
queued in a way separately, from normal apps, so they don`t all kick in at
once. (and cause jitter)
Peace Be With You.
Please CC me.
--
#initctl list | grep running #for running daemons
echo "Setting intelligent scheduling policies."
# realtime priority for that which need it
# RCU boost to 99
sudo schedtool -p 97 -n -20 -F `pgrep X` # X is singlethreaded, this makes
it perform the best.
#does any other thread benefit(desktop) from realtime?
#for pid in `pgrep "softirqs"`; do
# sudo schedtool -F -p 98 -n -20 $pid
#done
# idle priority for daemons
for pid in `pgrep "upstart"`; do
sudo schedtool -D -p 0 -n 19 $pid
done
for pid in `pgrep "udev"`; do
sudo schedtool -D -p 0 -n 19 $pid
done
sudo schedtool -p 0 -n 19 -D `pgrep rsyslogd`
for pid in `pgrep "dbus"`; do
sudo schedtool -D -p 0 -n 19 $pid
done
sudo schedtool -p 0 -n 19 -D `pgrep modem-manager`
sudo schedtool -p 0 -n 19 -D `pgrep cupsd`
sudo schedtool -p 0 -n 19 -D `pgrep acpid`
sudo schedtool -p 0 -n 19 -D `pgrep cron`
sudo schedtool -p 0 -n 19 -D `pgrep atd`
for pid in `pgrep "avahi"`; do
sudo schedtool -D -p 0 -n 19 $pid
done
sudo schedtool -p 0 -n 19 -D `pgrep whoopsie`
for pid in `pgrep "winbindd"`; do
sudo schedtool -D -p 0 -n 19 $pid
done
sudo schedtool -p 0 -n 19 -D `pgrep polkit`
sudo schedtool -p 0 -n 19 -D `pgrep timidity`
sudo schedtool -p 0 -n 19 -D `pgrep accounts`
sudo schedtool -p 0 -n 19 -D `pgrep console`
sudo schedtool -p 0 -n 19 -D `pgrep upowerd`
sudo schedtool -p 0 -n 19 -D `pgrep colord`
sudo schedtool -p 0 -n 19 -D `pgrep rtkit` #ubuntu has set this to nice 1?
sudo schedtool -p 0 -n 19 -D `pgrep keyring`
for pid in `pgrep "gvfs"`; do
sudo schedtool -D -p 0 -n 19 $pid
done
sudo schedtool -p 0 -n 19 -D `pgrep gconf`
# remomve unneeded
#sudo stop tty6
#sudo stop tty5
#sudo stop tty4
#sudo stop tty3
#sudo stop tty2
#sudo stop tty1
#sudo modprobe -r usb-storage
sudo modprobe -r snd_seq_dummy # is anyone using this?
sudo modprobe -r snd_seq_oss
sudo modprobe -r snd_seq_midi
sudo modprobe -r snd_rawmidi
sudo modprobe -r snd_seq_midi_event
#sudo modprobe -r snd_seq
sudo modprobe -r snd_pcm_oss
sudo modprobe -r snd_mixer_oss
sudo modprobe -r serio_raw
next prev parent reply other threads:[~2012-10-18 9:36 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 ` Uwaysi Bin Kareem [this message]
2012-10-19 23:27 ` Optimizing scheduling policies for Ubuntu (desktop), for low-jitter Uwaysi Bin Kareem
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.wmdbmeh66426ze@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).